I was using this information too: https://www.collaboraoffice.com/code/nginx-reverse-proxy/

But in my case it did not really help.

Diethmar

Thanks, Diethmar.

I gave up at the moment, sacrified one external IP and arranged port redirection at firewall. Finally, it works.

I will return to this issue later on.

Regards, Dariusz

So, I am using nginx as a reverse proxy and both filr and ce works as designed. Perhaps post your server block code for clues?

Okay,  ,

my trials failed again. So what do you want to see? My proxy part for nginx?

In my environment I use this configuration for my nginx now.

https://icewind.nl/entry/collabora-online/
The only statements I have changed that I access my content server via port 443 than 9980 (which is not really necessary).

I hope you are successful too.

I have attached a conf file for nginx which worked in my environment for a content editor vmware.

Hi Diethmar,

we tried to implement this configuration, but so far failed. The problem seems to be not the ngnix configuration but Filr: Filr does not use the "external" URL for ce over nginx but the internal one. The only access we see in ngnix's log is when configuring Content Editor in Filr, when pressing "Test connection" (Success) and "OK".

How did you make sure that Filr uses the reverse proxy? Are there any additional steps to do?

Thanks,

Mirko

Filr 23.2.1

Hi Diethmar,

we tried to implement this configuration, but so far failed. The problem seems to be not the ngnix configuration but Filr: Filr does not use the "external" URL for ce over nginx but the internal one. The only access we see in ngnix's log is when configuring Content Editor in Filr, when pressing "Test connection" (Success) and "OK".

How did you make sure that Filr uses the reverse proxy? Are there any additional steps to do?

Thanks,

Mirko

Filr 23.2.1

Filr wants to use an external ce dns name to offer ce functionality. So Filr should be able to access CE using a dns information without passing a proxy. ;-) (maybe use your internal DNS server to handle this or your local Filr hosts file).

Users will get the whole path to access but will pass proxy every time.

I still use the mentioned configuration file above.

Finally we got it working...

<IP address of ce appliance> <reverse proxy DNS name for ce>

in /etc/hosts to persuade Filr to use the reverse proxy. But this still seems strange to me - how does this work? And - how can one figure that out? Many thanks for the tip!

We had to change the location / section: we added

           proxy_set_header Upgrade $http_upgrade;
           proxy_set_header Connection "Upgrade";
           proxy_set_header Host $http_host;

here too, otherwise it did not work.

Thanks for helping!

I used tips for Collabora to get it running  

New CE needs new settings in nginx proxy settings. This example file will solve issues: https://help.univention.com/t/collabora-nextcloud-hinter-nginx-reverse-proxy/19871