I’m noticing a theme as I read through comments and questions, but not finding success. It seems like I have followed all of the steps to set up Collabora but I can’t access documents.
Basic structure:
nginx proxy manager using self-signed certificates
nextcloud docker
separate collabora container started from the same docker compose
Collabora .env includes:
extra_params=–o:ssl.enable=false --o:ssl.termination=true
I also tried this without ssl termination.
I can access nextcloud and collabora via browser using https without issue including the testing URLs listed in the integration guide.
I can use cur -k and access collabora using the domain in my NPM via the nextcloud container and vice versa so no communication issues.
In /settings/admin/richdocuments I get a green checkmark pointing to my collabora server. I do not have anything set up in the WOPI allowed-list at this time.
I have the checkbox checked to disable certificate verification.
When I try opening a file I receive the “Failed to establish socket connection or socket connection closed unexpectedly.” error which points me towards an NPM configuration issue but there’s no more options for me to change. I have toggled every possible option without success.
NPM configuration for each is very basic.
Domain Names: collabora.internal.home.arpa
scheme: https
Forward Hostname/IP: 192.168.1.xxx
Forward Port: 9980
Websockets support and block common exploits activated.
SSL Certificate: Self-signed
Force SSL, HTTP/2 Support, and HSTS Enabled all checked and I have cycled through all possibilities on these options.
Domain Names: nextcloud.internal.home.arpa
scheme: http
Forward Hostname/IP: 192.168.1.xxx
Forward Port: 4080
Websockets support and block common exploits activated.
SSL Certificate: Self-signed
Force SSL, HTTP/2 Support, and HSTS Enabled all checked and I have cycled through all possibilities on these options.
I tried using the proxy settings found here: Proxy settings — SDK https://sdk.collaboraonline.com/ documentation
and made a custom setting in NPM but I receive the same error.
I haven’t found anything in logs that points me towards an issue but I’m not sure where to look to be honest. I looked at the docker logs for my collabora container and the nextcloud container and it’s not clear what I should be looking for but nothing jumps out as an error.From what I have seen in other people’s setups the basic NPM config should work without requiring a custom nginx setup.
Oh, and for what it’s worth I tried using the integrated Collabora but that failed as well so decided to use one where I could at least control the setup.
Where do I look for an error of what’s stopping this from working? What else am I missing?