Thanks for the help everyone! Turns out that it was an iptable conflict. Two rules listing the port open (which resulted in a closed port). However, one of the comments by aka and another by manu2013 were problems that I would have run into, if not for the conflict. So! Always remember to edit the … Read more
This question should be on Server Fault. Nevertheless, the following should do the trick, assuming you’re talking about TCP and the IP you want to allow is 1.2.3.4: iptables -A INPUT -p tcp –dport 8000 -s 1.2.3.4 -j ACCEPT iptables -A INPUT -p tcp –dport 8000 -j DROP
As others said your Firewall needs to be configured to accept incoming calls on TCP Port 80. in win 7+ (easy wizardry way) go to windows firewall with advance security Inbound Rules -> Action -> New Rule select Predefined radio button and then select the last item – World Wide Web Services(HTTP) click next and … Read more
Problem This problem has been around for a long time. Disable iptables in Docker will take other problems. Rollback changes first If you have modified your server according to the current solution that we find on the internet, please rollback these changes first, including: Enable Docker’s iptables feature. Remove all changes like –iptables=false , including … Read more
Use this command to find your active zone(s): firewall-cmd –get-active-zones It will say either public, dmz, or something else. You should only apply to the zones required. In the case of public try: firewall-cmd –zone=public –add-port=2888/tcp –permanent Then remember to reload the firewall for changes to take effect. firewall-cmd –reload Otherwise, substitute public for your … Read more
Execute the same commands but replace the “-A” with “-D”. For example: iptables -A … becomes iptables -D …