Onlyoffice 7.3.0 websocket path invalid, help

installed docker onlyoffice 7.3.0 software.

in our current nginx system,config onlyoffice :
location /crm/onlyoffice/ {
proxy_pass http://onlyoffice:80/;
proxy_set_header Host $host:$server_port;
proxy_set_header X-Real-IP $remote_addr;
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
proxy_set_header X-Forwarded-Proto $scheme;
proxy_set_header Upgrade $http_upgrade;
proxy_set_header Connection “upgrade”;
proxy_http_version 1.1;

but page network requests have ***/cache/files path invalid ,no add nginx config “/crm/onlyoffice”.

response message contain :42[“message”,{“type”:“documentOpen”,“data”:{“type”:“open”,“status”:“ok”,“data”:{“Editor.bin”:“",“origin.docx”:“”},"openedAt”:1677169053306}}]

how to repair this problem ?

Hello @mojianpo
We changed the websocket library from sockjs to in v.7.3
We described workaround solution here:

Please check it out.

If I misunderstood your request, please provide us with details.

Hi Alexandre,

We are having the same problem, our reverse proxy is oracle HTTP server (essentially apache). We are using a virtual path from https - our document server is running as a docker container:

Define VPATH /onlyOffice

<Location ${VPATH}>
Require all granted
SetEnvIf Host "^(.)$" THE_HOST=$1
RequestHeader setifempty X-Forwarded-Proto https
RequestHeader setifempty X-Forwarded-Host %{THE_HOST}e
RequestHeader edit X-Forwarded-Host (.
) $1${VPATH}
ProxyAddHeaders Off

RewriteEngine on
RewriteCond %{HTTP:Upgrade} websocket [NC]
RewriteCond %{HTTP:Connection} upgrade [NC]
RewriteRule ^${VPATH}/?(.*) “ws://${DS_ADDRESS}/$1” [P,L]
ProxyPass ${VPATH} “http://${DS_ADDRESS}”
ProxyPassReverse ${VPATH} “http://${DS_ADDRESS}”

Any ideas what could be the problem here (we have had the issue for quite some time so have not upgraded our environment due to this issue so are running 7.2.1 in production).



Hello @kritta
The described by topicstarter situation was related to Docs v.7.3. In the version 7.3.2 we released a fix for it:

  • Revert to classic upgrade to fix connection issue with proxy

I believe you can update your installation to the latest version (v.8.0.1) without mentioned issue. However, we strongly recommend preparing whole server backup before update process just in case.
The another way, please try to deploy the latest version of Docs on a separate server with your proxy server to check it out.
Here’re our actual proxy samples, I believe they will be useful: Using ONLYOFFICE Docs behind the proxy - ONLYOFFICE