I have a setup that has a TrueNAS host, running Docker images for Nextcloud and Collabora, and a Linux VM running Virtualmin which manages Apache and other web apps for me as a proxy.
Originally, I had Nextcloud configured to use Collabora using the URL of 10.0.0.253:9980, ignoring the self-signed certificate. This worked from my home network, but failed when I was outside and accessing Nextcloud via Proxy.
I then tried to set up a Proxy for Collabora, but after configuring it, I am getting an 403 Forbidden when trying to browse to the new URL for the proxy. The intended URL of the Collabora server is office(dot)aiskon(dot)net
I tried to follow the directions from the Proxy Settings page, but seem to be stuck. Below are my files:
https://www.aiskon.net/public/collabora/apache2.txt
https://www.aiskon.net/public/collabora/coolwsd.xml.txt
May I get pointers on what I am missing?
Thank you!
If it helps at all, here are my settings from within Nextcloud:
hello @GJSchaller Welcome to collabora online forum. I did some investigation, here are some points that you can check one by one and see if that works ?
1. Check coolwsd.xml
Configuration
- Ensure that the
coolwsd.xml
file allows traffic from the reverse proxy (office.aiskon.net
):
To allow multiple hosts or aliases (e.g., your internal network IP and proxy domain), switch the mode to "groups"
and explicitly define your allowed hosts. Here’s how you can configure it:
Checkout coolwsd.xml
=> alias_groups
2. Apache Proxy Configuration
- Your Apache proxy settings for Collabora seem well-structured, but here are a few refinements:
- Add
nocanon
to all ProxyPass
directives where URLs are being passed to coolwsd
(especially WebSocket URLs).
ProxyPass /cool http://10.0.0.253:9980/cool nocanon
ProxyPassReverse /cool http://10.0.0.253:9980/cool
- Ensure that the WebSocket upgrade conditions match. For example:
RewriteCond %{HTTP:UPGRADE} ^WebSocket$ [NC]
RewriteCond %{HTTP:CONNECTION} ^Upgrade$ [NC]
RewriteRule ^/?(.*) "ws://10.0.0.253:9980/$1" [P,L]
3. Enable AllowEncodedSlashes
Globally
4. Verify SSL Configuration
- Confirm that the SSL certificate for
office.aiskon.net
is valid and trusted by Collabora. You can test this by accessing https://office.aiskon.net/hosting/discovery
directly.
- Ensure the SSL handshake works between Apache and the Collabora server. If using self-signed certificates:
5. Inspect Collabora Logs
6. Confirm Proxy Functionality
7. Firewall/Network Configuration
- Ensure that port
9980
is open between your TrueNAS Docker host and the proxy server.
- Confirm there are no additional security rules on the TrueNAS or Linux VM blocking traffic.
If still haveing the same issue then please can you share the error logs ? Will help to find the cause
Thanks
Darshan
Thank you for this - I’ll do some digging on my end. Most of this is already in place, I just need to check the logs.
My day job has also been my night / weekend job this week, I may be a few days before I can respond here.
1 Like