Docspace behind Pangolin tunnel

onlyoff · 27 March 2026 13:03

DocSpace version: latest
Type of installation of the DocSpace (docker, deb/rpm, exe, please point us to the installation guide that you used as well): docker
OS:Debian
Browser version:Onlyoffice Desktop flatpak version 9.3.1

I’m trying to tunnel my ip running Onlyoffice docspace to pangolin.

The web version works fine with that, while the desktop apps do not.

Web: Document opens up fine
Desktop: Download failed errors, when opening a file

When inspecting it seems to be the cause of mixed http/https errors.

I tried using switching to https as following user suggested:
https://www.reddit.com/r/OnlyOffice/comments/1r7m15d/comment/o6fnk1p/?utm_source=share&utm_medium=web3x&utm_name=web3xcss&utm_term=1&utm_content=share_button

Providing my website address

bash docspace-install.sh docker --letsencryptmail user@example.com --letsencryptdomain yourdomain .com

But pangolin would still only target my http page.

For now I use deprecated onlyoffice workspace, but any help for docspace would be appreciated.

Constantine · 2 April 2026 08:45

Hello @onlyoff

Just to clarify my understanding of the issue: you have DocSpace in Docker (by the way, what is the version of DocSpace specifically?) and you access it either via regular web browser or via Desktop Editors. While DocSpace works as expected in the web browser, it does not in Desktop Editors, is that correct understanding?

onlyoff · 28 April 2026 15:43

hey @Constantine thanks for replying.

While DocSpace works as expected in the web browser, it does not in Desktop Editors, is that correct understanding?
Yes exactly.

Yes I am using docker and used following command for setup:
bash docspace-install.sh docker
But I have also tried the package for debian with:
bash docspace-install.sh package
and had similar issues with the App.

I don’t have the specific version of docspace because i’ve since deleted the config, but I’m sure it was the latest.

But I know that the Workspace version had similar issues with tunnels like pangolin and cloudfare:

github.com/ONLYOFFICE/CommunityServer

Mixed Content Issue in OnlyOffice when accessed through a Tunnel

opened 04:59AM - 24 Feb 25 UTC

kerbymart

I'm running a local OnlyOffice Workspace installation and making it publicly acc…essible through a tunnel (via [pangolin](https://github.com/fosrl/pangolin)). While the main site is reachable over HTTPS, the editor fails to load because the OnlyOffice SDK seems to be requesting a non-HTTPS (HTTP) endpoint, leading to a Mixed Content error. I’m trying to figure out what might be causing these HTTP requests. Is there a configuration option—either in OnlyOffice or on the server side—that can force HTTPS usage for all requests? If anyone has encountered a similar issue or knows how to configure OnlyOffice to strictly use HTTPS. ``` sdk-all-min.js:543 Mixed Content: The page at 'https://onlyoffice-workspace.<TUNNEL_DOMAIN>/Products/Files/DocEditor.aspx?fileid=4' was loaded over HTTPS, but requested an insecure XMLHttpRequest endpoint 'http://<SUBDOMAIN>.<TUNNEL_DOMAIN>/ds-vpath/cache/files/data/Vhk5wuA…&shardkey=VhkSwuAgFPO8Emav1hDKsEsPOdykuUA123Rzvc1xGU8_&filename=Editor.bin'. This request has been blocked; the content must be served over HTTPS. Ya @ sdk-all-min.js:543 ``` Additional issues encountered: | ``` Access to manifest at 'https://proxy.<TUNNEL_DOMAIN>/auth/resource/1?redirect=https%3A%2F%2Fonlyoffice-workspace.portpunch.lol%2Fmanifest.json' (redirected from 'https://onlyoffice-workspace.<TUNNEL_DOMAIN>/manifest.json') from origin 'https://onlyoffice-workspace.<TUNNEL_DOMAIN>' has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource. ```

Which I was able to solve here by changing the headers:

github.com/ONLYOFFICE/DocSpace

DocSpace login page renders only background (no login form) when accessed behind Nginx Proxy Manager over HTTPS

opened 08:05AM - 23 Feb 26 UTC

Strux-DK

Environment: - ONLYOFFICE DocSpace: 3.6.1.1 (Docker) - Reverse proxy: Nginx Prox…y Manager (jc21/nginx-proxy-manager) Deployment: - DocSpace stack running on 192.168.10.101 - NPM running on 192.168.10.103 - URL (Only locally available): office.customdomain.com - TLS terminated at NPM (HTTPS → HTTP upstream) When accessing DocSpace directly via IP: `http://192.168.10.101/login` The login page renders correctly (full UI with login fields and buttons). All expected /api/2.0/* initialization requests are made. When accessing via reverse proxy: `https://office.customdomain.com/login` The page renders only the background. No login fields or buttons are shown. All static assets load successfully (CSS, JS chunks, fonts). No network errors are visible. No JavaScript exceptions are thrown. Console shows: ``` initCSR ClientConfig: undefined ``` Only a minimal API call is made: `/api/2.0/settings/colortheme` Expected initialization calls (e.g. `/api/2.0/portal`, `/api/2.0/people/@self`, etc.) are not triggered. NPM is configured as: - Forward Host: 192.168.10.101 - Forward Port: 80 - Websocket support: enabled Custom headers set: ``` proxy_set_header Host $host; proxy_set_header X-Real-IP $remote_addr; proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; proxy_set_header X-Forwarded-Host $host; proxy_set_header X-Forwarded-Proto $scheme; proxy_set_header X-Forwarded-Port $server_port; ``` Tested with and without: - HTTP/2 - Additional forwarded SSL headers - Clean browser storage - Restarted DocSpace containers Screenshot: <img width="1913" height="913" alt="Image" src="https://github.com/user-attachments/assets/f44e8355-f3ac-410b-a77d-eb8f85f5a5d7" />

I tried the same with docspace but that only worked for the web-browser. I’m now using Onlyoffice Community Workspace instead.

But it would be nice to be able to run onlyoffice Docspace/Workspace behind a reverse proxy without having to configure files.

onlyoff · 28 April 2026 15:43

Here’s another one having the same issues with the login page with cloudfare (not pangolin):

onlyoff · 28 April 2026 15:50

Just to clarify setting these settings in the comment left on github:
DocSpace login page renders only background (no login form) when accessed behind Nginx Proxy Manager over HTTPS · Issue #1854 · ONLYOFFICE/DocSpace · GitHub
worked for both web and the app with onlyoffice workspaces proxied with pangolin.

Constantine · 4 May 2026 15:45

Good to know that it works in Workspace, however, in order to troubleshoot the problem with DocSpace, a running instance of DocSpace is requried. If you feel like it worth analyzing, please let me know.