-
Notifications
You must be signed in to change notification settings - Fork 489
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
OnlyOffice won't load after newest docker update - TRANSPORT_HANDSHAKE_ERROR? #576
Comments
Hi, same problem here, seems linked to changes in 7.3. |
reverted to 7.2 which works ok |
Same here. I've spent several hours looking for the solution, but it was nowhere to be found. Reverted to 7.2 and everything works fine again. |
Same here. Reverted to latest 7.2 which works OK. |
Same here. |
Guess it the same problem as ONLYOFFICE/DocumentServer#2084 because we switched to socket.io. Make changes to your apache proxy config ONLYOFFICE/document-server-proxy#27. |
It does not happen only on apache. I use nginx as my proxy (nginx proxy manager to be precise). |
@pawel-szopinski i haven't experience with nginx proxy manager, but i cheked our examples nginx configs with 7.3 and are works. https://helpcenter.onlyoffice.com/installation/docs-community-proxy.aspx |
Thank you @igwyd. I am using document-server behind a nginx reverse proxy (https to http), and was experiencing the issue (as stated above). I copied the settings from https://github.com/ONLYOFFICE/document-server-proxy/blob/master/nginx/proxy-https-to-http.conf into my .conf file, and it works now. |
Ok, to everyone who uses Nginx Proxy Manager, just enable "Websockets Support" in your ONLYOFFICE proxy host. It's in the very first tab (Details). |
THIS! |
Seems to be fixed with the newest update for me. Can you confirm? |
Yes, confirmed, at least in case one uses Nginx Proxy Manager, enabling Websockets Support is no longer required, so everything's working as it used to in ver. 7.2. |
Same here - as soon as I upgrade to version 7.3 at my Kubernetes cluster it won't open any office file. |
I have made some oberservations but no clue yet. background:
everything works on 7.1 but not on 7.2 and not on 7.3 i tried already 4 upgrades all failed i guess i really need to roll back to 7.1 which was super stable and will watch all theses threads :) |
Hello @ant0nwax, you are missing /etc/onlyoffice/documentserver/local.json, our updates need it. Can you run |
@igwyd thank you for the contribution, I am restored the snapshot of 7.1 and did following steps:
i suppose the script destroyed my HTTPS configuration of OnlyOffice tcp 80 0 0.0.0.0:5672 0.0.0.0:* LISTEN Thank you |
@ant0nwax You need to switch to https, for example follow this instruction https://helpcenter.onlyoffice.com/installation/docs-community-https-linux.aspx |
Thank you for pointing again in the right direction, it seems it is a documentation issue that many creators and users do not develop or integrrate https environments, i learned for security reasons to use https even in local networks. i think the attitude worldwide could maybe one day change in order to have this as a default... for chrome and edge these are mandatory things nowadays that get moqued out... not a good test scenario :) Because i am not using IPV6 on the onlyoffice host, I could share the following change was needed additionally:
and then finally when i used point 5 of the docs [root@onlyoffice ~]# bash /usr/bin/documentserver-update-securelink.sh now what is that connected to? I will not yet try to update as this step again produced an error.
OnlyOffice is back on Port 443 but Nextcloud has the 502 Bad Gateway like in initial issue post |
step 2 is missing a point:
please fix the docs :) and still the error is i do not know how i fixed that once already, but most likely there must be a centos maybe selinux issue?
it exists :)
selinux seems good from here, so no clue anymore
|
I just see that port 8000 is not LISTENING, so how to get port 8000 listening? |
hmm
cleaned
looks better :)
|
please see the following as a bug report and hand it over to QA team, it will not work for anyone on centos or redhat if selinux is enabled
it destroyed the selinux context and the owner of the file /etc/onlyoffice/documentserver/default.json
|
the error in err.log disappeared, still there is errors in out.log for docservice and converter
i think the fact that i should run the script sudo bash /usr/bin/documentserver-update-securelink.sh broke a working onlyoffice in not 1 but already 3 places, and i am debugging for the last 3 hours... I think i deserve at least some break :) |
I WOULD LIKE TO POINT OUT I AM STILL ON 7.1 BEFORE ANY UPGRADE I JUST WAS RUNNING TWO SCRIPTS
these two destroyed the whole installation :) I rolled back and I shall rest until monday |
Please, upgrade it in accordance with the upgrades to the upstream version of OnlyOffice, see ONLYOFFICE/DocumentServer#2083 |
so i shall ignore the errors and port 8000 does not listen, but i shall upgrade according the other bug report? which is OPEN ;) whats the reason for the two mentioned scripts breaking a working 7.1 installation? missing QA in release pipeline i will not trial and error upgrade anymore before some more users are encouraged to break their installations ;) |
i am trying a new upgrade, this is not docker
|
i found this thread, maybe this is connected: |
I started a new thread for my issue: |
Hey everyone,
since the last update my watchtower did, my OnlyOffice won't load the interface/gui anymore, it just keeps showing the loading-logo until it fails after like 1-2 minutes. Below is the log.
Do you want to request a feature or report a bug?
Bug
What is the current behavior?
Onlyoffice in Nextcloud starts opening a new tab with the logo loading, but the interface/gui never opens.
If the current behavior is a bug, please provide the steps to reproduce and if possible a minimal demo of the problem.
My watchtower updated to the last recent version, since then this happened.
What is the expected behavior?
The gui/interface to properly load so I'm able to edit documents
Did this work in previous versions of DocumentServer?
Yes. It's still working with e.g. 7.2.2.56
DocumentServer Docker tag:
-latest
Host Operating System:
Synology DS918+
The text was updated successfully, but these errors were encountered: