Open BerndGit opened 1 year ago
Hi!
I had also issues using Collabora behind the reverse proxy.
As far as I understood this tread seems to address the root cause of issues with Collabora and OnlyOffice behind reverse proxy: https://github.com/nextcloud/richdocuments/issues/1904
Unfortunatly I lack the skills to make OnlyOffice running behind the proxy.
Config of internet facing proxy:
server {
listen 80;
server_name your_server_name;
location / {
proxy_pass http://your_server_internal_ip:80;
}
}
server {
listen 443 ssl;
server_name your_server_name;
location / {
proxy_pass http://your_server_internal_ip:80;
include /etc/nginx/snippets/rp.conf;
}
ssl_certificate /etc/letsencrypt/live/your_server_name/fullchain.pem; # managed by Certbot
ssl_certificate_key /etc/letsencrypt/live/your_server_name/privkey.pem; # managed by Certbot
}
Passing those packets as is, without changing / setting any header seems to work for me. Also notice im terminating my ssl here as I trust the connection between internet facing proxy and the machine the container is running on. Hope this helps.
Try removing those rewrite rules or request header lines in your apache config, im using nginx though.
But this gives a red warning message in admin settings,
The reverse proxy header configuration is incorrect. This is a security issue and can allow an attacker to spoof their IP address as visible to the Nextcloud. For more details see the [documentation ↗](https://docs.nextcloud.com/server/28/go.php?to=admin-reverse-proxy).
I try to run the container behind an Apache2 reverse proxy.
Result:
Major changes, which I did on Apache
myenabledsite.conf
:and in
docker-compose.yml
:any Idea?