dm17
dm17
I'm not sure about the IPs in docker changing... I thought it would be more reproducible than that - maybe we should ask your question on Docker forums? And then...
Also looking for this functionality. I don't care about per-container support - just predictably deny all to 443/80 + allow 1 IP to 443/80.
> Also looking for this functionality. I don't care about per-container support - just predictably deny all to 443/80 + allow 1 IP to 443/80. OK, I think this functionality...
Yes, and nmap shows ports not explicitly allowed as open. So does "ufw default deny" need to be altered to defaultly deny based on your changes? I know the after.rules...
So how do I do the equivalents of 'ufw default deny' and 'ufw deny 443' for all of docker? Thanks. EDIT: I just deleted all of my rules, and added:...
OK, I'm confused... It seems to be working now. I did restart the server after setting this up the first time, but this time after rebooting it all works as...
> I'm confused too. So, you still applied these rules in `/etc/ufw/after.rules`? Yes, they were there from the time I started... I will continue testing to see if the docker...
I can start a new thread if you'd like, but I'm having a strange problem where one particular docker service in a docker-compose of 6 services is having issues talking...
@bures Thanks - using the built-in ZoneMTA (not sure what it is) as opposed to what? I'm mostly using it for the Mosaico editor's mailing list compatibility and ease connecting...
I envision a 'D' with an tiny arrow to another 'D' that looks slightly different...