-
Notifications
You must be signed in to change notification settings - Fork 353
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
Comments
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 |
I confirm that "ufw allow" rules are ignored. |
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 |
can confirm not working on ubuntu 24.04 LTS |
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?
The text was updated successfully, but these errors were encountered: