I’m struggling with setting up nginx as a reverse proxy on ipfire.
nginx is setup to listen on port 443, but all external access to RED/port 443 is blocked by the firewall and not forwarded to the nginx running on ipfire.
Is it necessary to create a firewall rule for this type of access ?
Nick, thanks a lot, this was the link I missed. I wasn’t aware that it’s necessary to create a firewall rule for any service running on ipfire with accessibility from the internet.
Also in all documentation about nginx on ipfire I couldn’t find any hint about this issue.
Thanks again for solving my issue.
Running nginx or HAProxy as a reverse proxy is a great task for IPFire because you can have to many different services running behind it, have the IPS scan all the traffic and what not.
I would not recommend to host your blog on IPFire.
Well, it seems we unfortunately have different views on that.
I use Nginx myself as a Proxy (about 10 Services) and as a Webserver as a Jail - therefore I know pretty much exactly that even a missing or incorrect “/” placed in the ‘location’ block can have devastating Consequences.
Unlike an Nginx Jail (FreeBSD) or a VM, this may potentially allow access to the underlying IPCop ‘root’ filesystem.
I may be a little paranoid about this, but in my opinion, such a Service has no place on my Firewall.
Thanks again for all the aspects and arguments about this.
After evaluation all the aspects I think running nginx just as a proxy on IPFire is ok from my point of view, keeping in mind that misconfiguration of any firewall component is always something which hurts firewall security.