-
Steps to reproduce
Expected behavior Ability to create Nextcloud Office documentsActual behavior Nextcloud office is not connected to Collabora document server.Host OS Ubuntu server 22.04 - UFW disabledNextcloud AIO version Nextcloud AIO v2.0.4Current channel You are running the latest channelOther valuable info |
Beta Was this translation helpful? Give feedback.
Replies: 18 comments 17 replies
This comment has been hidden.
This comment has been hidden.
-
Hi, i fear I cannot reproduce this. Can you please post the nextcloud-aio-nextcloud container logs here? Also are you running AIO behind a reverse proxy and/or are you using docker rootless or podman? |
Beta Was this translation helpful? Give feedback.
-
Hi, I am not behind reverse Proxy now. .... but I will use NGINX Proxy later (I found your tutorial for that). I started the docker command as sudo user, not root. I do not use podman. |
Beta Was this translation helpful? Give feedback.
-
Thanks for the response! However I need the logs of the |
Beta Was this translation helpful? Give feedback.
-
Sorry, my bad. Thank you. |
Beta Was this translation helpful? Give feedback.
-
Thanks! Can you click on that button and check if that makes it work? |
Beta Was this translation helpful? Give feedback.
-
I hope I am sending the right one. |
Beta Was this translation helpful? Give feedback.
-
Hm... so it looks like websockets connections do not work in general. Which reminds me of this thread: #1196. I honestly do not think that we can improve AIO to fix this... It is rather something with your domain or maybe web firewall and/or something in between AIO and the client... Where are you hosting your domain and are you using some kind of web firewall or therelike? Did you also already try different browsers? EDIT: I googled the problem again and the issue may be an adblocker? https://www.reddit.com/r/audiobookshelf/comments/ub021p/caddy_v2_as_reverse_proxy_websockets_not/ Sorry, I am honestly still tapping in the dark since the issue is not reproducible in my test instance. Everything works as expected here. EDIT2: for google domains I found this: https://support.glitch.com/t/websockets-do-not-work-on-custom-domain/31171/5 |
Beta Was this translation helpful? Give feedback.
-
Hi,
hostname No other settings were applied in the Ubuntu server filesystem.
I tried 2 browsers - Chromium a FIrefox (Ad Blockers - disabled) with the same results. I am not an IT pro... just an amateur so I do not understand all. I do not use any Proxy service. Thank you for your answer. |
Beta Was this translation helpful? Give feedback.
-
I tried to remove the line above and It did not help. As you sent me the hints. |
Beta Was this translation helpful? Give feedback.
-
I just had an idea what you could try: What is the output of |
Beta Was this translation helpful? Give feedback.
-
Also, what does |
Beta Was this translation helpful? Give feedback.
-
I tried to remove the line above and It did not help. As you sent me the hints. I am sending output logs from both commands above. |
Beta Was this translation helpful? Give feedback.
-
So it seems like you indeed have cloudflare in between the client and AIO based om the logs that you provided. Can you try to disable the clouflare caching and check if that makes it work? See e.g.https://community.cloudflare.com/t/disable-cloudflare-caching-completly/86417 |
Beta Was this translation helpful? Give feedback.
-
Can you please also try to get completely rid of cloudflare in the chain to eliminate that as a possible problem? |
Beta Was this translation helpful? Give feedback.
-
I also found this: https://support.cloudflare.com/hc/en-us/articles/360050691831-Understanding-Network-Error-Logging |
Beta Was this translation helpful? Give feedback.
-
To sum this up: seems like switching to NPM solved the problem |
Beta Was this translation helpful? Give feedback.
-
Hi, |
Beta Was this translation helpful? Give feedback.
To sum this up: seems like switching to NPM solved the problem