Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Stopped working recently? #120

Open
toitzi opened this issue May 7, 2024 · 7 comments
Open

Stopped working recently? #120

toitzi opened this issue May 7, 2024 · 7 comments

Comments

@toitzi
Copy link

toitzi commented May 7, 2024

Recently the script stopped working, i tried it with 3 different servers. Usually everything was blocked correctly. But now it does not seem to block anything anymore. I verified the ufw rules and i verified that the firewall configuration was there, still no success (ubuntu). Did anything change in a recent docker release? Is anybody else having that problem?

@tebbbb
Copy link

tebbbb commented May 8, 2024

i also have a hard time getting it to work. It completely ignores my ufw allow rules and i have to manually enter stuff into the after.rules to get it working or use a proxy

@mysteryx93
Copy link

I confirm that "ufw allow" rules are ignored.

@justJackjon
Copy link

justJackjon commented May 10, 2024

Ah, thank goodness for this issue thread - I thought I was going bonkers 🙃!

Sadly I couldn't get it to work either 😞

Edit: Apologies, I should have been explicit - after following the instructions in the README, like the OP I found that containers were not blocked by default, which was the behaviour I was expecting. I made sure to verify that after running the ufw-docker utility script that the rules were added correctly added to /etc/ufw/after.rules.

@s55ma
Copy link

s55ma commented Jun 14, 2024

can confirm not working on ubuntu 24.04 LTS

@byayex
Copy link

byayex commented Jul 10, 2024

It is still working for me.

What is the IP address you use to access it? Maybe you are using an IP address from the IPs declared in the after.rules:

•	192.168.0.0/16
•	10.0.0.0/8
•	172.16.0.0/12

If you access it with one of the internal Docker IPs (which can also be private network IPs), you are bypassing the firewall. If you try accessing it from another network/IP, it should still be blocked.

@akselerando
Copy link

akselerando commented Jul 18, 2024

I am also unable to get this to work. I've installed using the script, but connections are not blocked at all. Have anyone been able to find a fix for this, or know of an alternate solution?

Edit: I forgot to re-remove the trusted IP-addresses from the config after re-installing. Works as intended now.

@c80609a
Copy link

c80609a commented Jul 25, 2024

Block all outgoing connections from inside a docker container except https using firewalld. https://gist.github.com/deploy595/205ea7985fbf41fe66ab9a082021ed6a

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

8 participants