Let's Encrypt can't work on Cox
I just want to restate that Cox blocking port 80 started out as an "okay" idea for security but has become the exact opposite. All Cox-provided routers have a firewall, and the majority of people not using Cox hardware have their own firewall because that is their preference. In my case I want to use Let's Encrypt to provide certificates for my firewall, and Cox makes this impossible by blocking port 80. Please read up on the ACME spec and see if you can do something for it. Regards, Mike
Cox is blocking port 80 incoming, causing security certificates from installing!
This is a real issue.Cox needs to at least unblock port 80 incoming for let's encrypt acme servers. Many of us want to remote into our routers and have a certificate displayed on the web page. Many newer high end routers like my ASUS 88U will allow a certificate to be added to your DDNS address, ( COX dynamic IP.) On the 88U everything is in front of the firewall and I opened a ticket with ASUS and they verified that port 80 was being blocked by my IP. You can see bad communication in the logs of the router when it is trying to get an answer back for the key that is randomly generated. I also put a Debian linux box in the DMZ and got the same results. Now I always use a list of select IP addresses when I log in to my router from WAN but I hate the security exception issues. Cox needs to fix this as let's encrypt makes the internet a safer place and they are setting back our ability to guard and protect ourselves. https://www.cox.com/residential/support/internet-ports-blocked-or-restricted-by-cox.html