Make reverse proxy container firewall rules work without the need for NAT?

[Skyrider]

What I currently have in my network interfaces is NAT forwarding 80/443 to my reverse proxy container. My entire server is only having a single IP address. Now while that is working great, the main problem is due to the NAT forwarding the firewall rules (on the host & container) are useless when it comes to users coming to http/https. If a abusive user is being rejected on the server from accessing my websites, they can still do so due to the NAT forwarding.

Is there any alternative way to forward 80/443 ports to the reverse proxy container, without the NAT so I can at least still use iptable rules?

Regards,
Skyrider

 

[em.tie]

I am not sure if this helps but there is a way to use iptables / fail2ban with x-forwarded-for . A way is described here but if you google iptables and x-forwarrded-for (here the source ip is stored) and iptables https://nerdblog.steinkopf.net/2016/12/fail2ban-schuetzt-owncloud-hinter-reverse-proxy/

cu em.tie