Now, I am not fluent in the iptables language but shouldn’t you first specify what IPs that are accepted and then drop everything else? To me it looks like you are dropping everything and then the accept rules are never reached. But, what do I know…?!
By the way, 0.0.0.0 is just a placeholder.
Ip tabels are executed one after the other.
First, all incoming packets are blocked to ports 80 and 443 and then released in this case only for IP 0.0.0.0.
Because Bitwarden is running in a Docker container does Bitwarder ignore these rules.
Is there possibly a solution for from Bitwarden?
Hello @sb2014,
i guess you mean a self hosted bitwarden. In that case note that Docker itself modifies your IP Tables [1]. Having yourself and docker modifying IP tables can cause unexpected behavior. You can achieve your goal by just modifying either docker-compose.yml or writing into docker-compose.override.yml the following [2]: