April 22, 2020

From Gerald R. Lucas
Revision as of 16:56, 22 April 2020 by Grlucas (talk | contribs) (Created page with "{{Large|Cox-blocked}} {{C19|40}} For the life of me, I could not figure out why my server could not successfully retrieve an SSL certificate from Let’s Encrypt. I had done...")
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)

Cox-blocked covid-19: day 40 | US: GA | info | act

For the life of me, I could not figure out why my server could not successfully retrieve an SSL certificate from Let’s Encrypt. I had done it before. My proxy server seemed to be working. I even posted to the LE help forum, and some dude told me that my port 80 was down. What? It had been working fine...then I remembered something...

A quick search, and I confirmed it: Cox blocks port 80 on residential service. Of course they do. Of course their reasons are bull💩; they just want to charge you more for a “business” account when it would take some sysadmin three seconds at a terminal to open the firewall. I know: I should call them before I complain too much, but I can already predict that call would not go well. This is so frustrating and negates the only reason I bought my third Raspberry Pi for a proxy server.

. . .