The error usually appears as "ERR_SSL_PROTOCOL_ERROR" or "SSL_ERROR_RX_RECORD_TOO_LONG". This is occurring regardless of what browser is used and appears to be exclusive to Comcast Xfinity users.
It's on a shared hosting package with Namecheap, the computer in question running Cloud Linux, and they do not support root access or Let's Encrypt as an official cert provider so I had to manually install it with certbot running on Windows 10.
I contacted Namecheap customer support about the issue and they said that as far as they can tell the cert is installed correctly and the server is functioning properly.
Hi and welcome to the LE community forum.
I have to agree with NameCheap, I can't anything wrong.
If you have a picture of the error, that might be helpful.
It might be something like them adding "www" to your site: https://www.samus.is-best-girl.fyi
Notably, I've had a user who has tried the website both on their home internet and on mobile hotspot. Their home internet is Comcast. In the same browser, on the same computer, they can connect fine on hotspot but not on landline.
I will recommend clearing browser caches if anyone gets the issue again, but I'm not sure how to tell Comcast itself to fix their cache or whatever issue they're having with resolving my site.
I would suggest looking in to Comcast internet engineering team... possibly at your local level. (I have had some success at this approach) the Corporate site is full of BS.
The caches can be flushed and recreated on the fly, if they are willing to do it.
"Squeaky wheel gets the grease"