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
Nextcloud Unable to Connect to DocumentServer following Upgrade: socketOnTimeout
#2146
Comments
Hi, any news here? |
if i do healthcheck after upgrade to 7.3.3-49 on CentOS 8 Stream it returns: https://[onlyoffice.domain.tld]/healthcheck
this is the nginx on the onlyoffice server, nextcloud is not used here at all, neither wss the onlyoffice nginx error log shows: 192.168.1.14 is the reverse proxy
EDIT: https://192.168.1.29/healthcheck and it also does NOT work the onlyoffice rabbitMQ log throws very many errors after a clean reboot after upgrade
and it continues to generate tons of errors These are the listening ports locally:
|
Okay I wrote a lot of things and many might not be true but i limited the test to a minimum the Example Project does not work when I connect locally to the nginx server
|
solved by something like 5 hours which can be reduced to:
add the JWT secret to nextcloud only office integration and VOILA |
Hello @MikeDacre, sorry for the late reply. Something went wrong while updating. Can you attach update log? |
@igwyd This happened a while ago now and I ended up switching to collabora because I just couldn't fix the problem with the above solutions or any similar solutions posted on similar issues. So unfortunately, the log is gone now. I do prefer OnlyOffice though and so I'll try to recreate the issue in the coming days when I have time and try to get an update log to you. |
I also tried an update last weeks and restored a snapshot because the installation broke again. this time the rabbitmq did not run after upgrade on centos8 stream |
This issue is unique.
Operating System of DocumentServer
Linux (DEB package)
Version information
7.3.2
Expected Behavior
Have
onlyoffice-documentserver-ee 7.3.2-8~stretch
installed viaapt
. I use it only with nextcloud. It has been working fine, following upgrade today, it is not connecting.Actual Behavior
On opening document in nextcloud:
out.log
attached. Get the warningnodeJS - Transport unknown
and report that it is timing out onsocketOnTimeout
.out.log
Otherwise the rest of the log looks fine. I'm confused why it is trying to use a socket... maybe that is the issue? I looked in default.json for anything related to sockets, but the only thing I found was related to
sockjs
. Mylocal.json
is minimal and just defines the db and secret string for connection.Reproduction Steps
No response
Additional information
https://oo.mdd.li/healthcheck returns true. No firewall. I use internal ports on
127.0.0.1
for connection with nextcloud, error maintained if I remove these.The text was updated successfully, but these errors were encountered: