Web access behind reverse proxy

[kangfat]

I may have missed it but are there setup instructions to set this up behind a reverse proxy?

[SubleXBle]

no, my chain of thought was, that the people using the reverse proxy, will know how to set that up.
You can adjust ports within docker-compose and dockerfile to fit the needs for a reverse proxy.

as far as I know you can set up ips that will (simmilar to portmapping) bound to your outside ip/dns with certain ports. something like

location /some/path/ {
    proxy_set_header Host $host;
    proxy_set_header X-Real-IP $remote_addr;
    proxy_pass http://localhost:8000;
}

you can set the port of the apache-container to anything you like and set the outside port to something easy like 8000 - but then you will have to map this in your proxy since this is the thing that would pass requests through to the service ...

what reverse proxy do you use? Nginx? Cloudflare?

[kangfat]

I use nginx and have it up and running for other services. I'm using the native install and just wasn't sure if there was a config to adjust the port internally so that I can proxy to that port.

[SubleXBle]

oh - sorry - you would have to do this in dockerfile and docker-compose.yml prior installation. I did mention this in the install readme/instructions once or twice - but probably not clear enough or to easy to overread ..
but you dont have to use the installer again - the installer just sets up the places that are shared with the container - so you can easy go for docker-compose stop && docker container prune && docker-compose build && docker-compose up -d to rebuild quick and easy without loosing settings or .json files if you took a wrong port-config for your setup

[kangfat]

Ah, I did miss that. Thank you for clarifying and the instructions. I will try again.

[SubleXBle]

tryed to make it more visible in readme/installation instructions:

⚠️ When you are behind a reverse proxy ⚠️

Default Ports are set to 80:80 443:443 you would have to change this prior installation in docker-compose.yml and Dockerfile to propper connect to your reverse proxy

[SubleXBle]

if you want to set this up on a non docker webserver behind a reverse proxy, you would have to change used ports for apache ... but I dont think that was the question?

[kangfat]

Looks like there might be an error in the instructions. Should that say cd Fail2Ban-Report-Docker?

[SubleXBle]

oh - i see - on the first step
and you are correct - changing it - thy :)

[kangfat]

Here is another I believe with the same issue, it should say Fail2Ban-Report-Docker

[SubleXBle]

i am a heavy tab user :)

[SubleXBle]

cannot see the image sadly but it is only the first folder that has the name -Docker. Everything else should use the usual "Fail2Ban-Report" Name without "-Docker"

[SubleXBle]

my last test installation was from step 2 by just copying the steps in the readme and pasted it to the shell - worked fine - I hope it does for you too

[kangfat]

I've ran into a few hiccups so far.

When I run Install.sh it wants to install fail2ban even though it's already installed and on the latest version.
It attempts to install fail2ban but doesn't attempt to install docker or docker-compose

This is a me issue but I can't seem to get it to work behind a nginx reverse proxy. This is still a WIP but I'll eventually get there.

[SubleXBle]

ah - ok - had not installed fail2ban on my testsystem so i was not wondering that installation was triggered ..
this should only trigger when fail2ban is not running/configured or installed - I will have a look at it.
that it does not install docker or docker-compose was intentionally - my thought was, that people want to use a docker-version of something have docker installed and I did not want to cause disturbance in setups where version numbers are important by just overwriting it. Same with Fail2Ban - is needed - so there is a check for it - but I will review this - there is probably a smarter method to do the installation stuff ..

Did you update the docker files (both) to ensure you are opening the needed ports?
If yes, try to "disable" htaccess by renaming it - if it works you will have to fiddle a litte until you have your settings running and secure enough.
I am not so much into the docker world, just did it because it seem to be possible when I got asked

[kangfat]

I found one more error. Once I figured this out I got everything up and running behind my reverse proxy.

In the .htaccess file it lists the AuthUserFile as being in the /var/www/html/ directory, however, it is actually in the /var/www/html/Fail2Ban-Report/ directory. After I adjusted that everything started working perfectly.

Thank you again for your help!

[SubleXBle]

the .htaccess is in /var/www/Fail2ban-Report/.htaccess

the .htpassword does not exist at the point of installation therefore I set the path to ../html/ because it is outside of the webroot .. but it is not enabled by default : or should not be enabled by default .. thats why i made the Helper-Script.sh as Part of the Installation process to "make sure, your htaccess fit your needs" ..

to be fair, I could be more specific on those points .. I will rework the Installation-Guide to be more helpful.
thank you for your feedback! Appreciate it! 🙏

[SubleXBle]

would you be ok with it, when I moove this conversation to the docker repository as it could be helpful for others?

[kangfat]

Sure. And again, thank you for the help with getting this running.