Access to FileRun through Apache proxy

Petr B 2 years ago updated by gary.parr 1 week ago 2

Hello everyone 

I try to configure FileRun behind apache proxy, but I have a problem with it.
Filerun is located on http://filerun.xxx.yyy but I don’t want to expose it to outside.
I desire that the access would be the following: The outside user goes to https://my.domain/filerun and there he may use FileRun through the proxy.
If someone has similar experience please share your apache httpd.conf as an example


I hope to find some help here.

I'm really struggling on the same problem. There's not much information to make it working behind a reverse proxy.
I'm running Filerun in a docker container, trying to acces it trough the build in reverse proxy (Asustor).

I can get to the https login page, when I login I get an alert saying that i'm redirected to http without encryption and the login fails without any message.

Please Help :(

So, not a lot of information to go on here.

Is it just a change to http on the same proxy domain name? Or is it being redirected to http on the actual host (not proxy) domain name?  I'm assuming that your proxy is terminating the SSL and connecting to FileRun over HTTP and that your proxy addy is something like https://frproxy.external.domain and the redirect giving problems is like http://frserver.internal.domain. If this is the case, try forcing FileRun to use the proxy base by following Vlad's instructions in this answer.  If that works, then you have the same basic issue I do which is... where does FR pick up the domain name from any why isn't it detecting/using the proxy base value when generating links in content.

If the domain name on that troublesome link is actually the proxy address then you have a different issue. There are a few posts on here about forcing SSL, and I believe even a "force HTTPS" option in FileRun itself. Poke around at those a bit and see if it fixes your issue.