They did something. I can't see the pic now in firefox!

What I notice is the cert is for domain.com, not www.domain.com. So if you post pic as https://domain.com/pic.jpg, there won't be any issues. If you post as https://www.domain.com/pic.jpg, it will not work.

Btw, Lets Encrypt certs are good for 3 months. Yours expires on 1/26/2021. You are permitted to renew as early as 30 days before expiration. Most systems have scripts in place that handle renewal automatically. Else we'll be revisiting this topic next year

I see two ways of fixing this.

1) Issue another cert for www.domain.com
2) redirect www.domain.com traffic to domain.com (seems counterintuitive)
3) generate a wildcard *.domain.com cert with letsencrypt - automated renewal becomes more challenging and also lets secure as it involves generating TXT dns records via api (assuming your registrar supports api access).

If it were me, i'd do #1 and call it a day.

You get what you pay for . I have my own domain too, and run a small static website for a music club on top. I don't charge 'em anything for the hosting, but they do pay for any updates.

edit: Seems firefox is caching some stuff. Disregard.. Cert appears correct. Quite FF,deleted cache folder, then restarted. Carry on

 

I bought that domain back in 1998. I think it was 1998. Once or twice a year, I still get flack from some irate or confused English Lit student, for obvious reasons.

 

I got mine around 2004. It was mainly for email. I was bouncing between dialup providers back in the day and email changes were annoying. While I have several gmail/hotmail/yahoo accounts, those are mostly for disposable purposes (junk mail). Having my own domain alleviated such issues. I pay ~$50/2 years with a company called hawkhost.com for the webhosting. They use cpanel for the admin stuff.

I'm no expert on the stuff but do like having full control. There is the occasional glitch/outage (handful of times a year at best). Good enough for my use.

 

Now that all is right with the world again (for a while, at least), here's a pic hosted on my personal site that goes BAM! with simple, front-end G37 beauty.



Love this shot.

 

I don't see it....


https://....without the www

 

Well now you're too deep in the weeds for me.

I can see everything normally again in Chrome, all platforms. And my site is no longer being flagged as insecure.

 

I did some experimenting. When I connect via wired, your pic is blocked. When I connected wirelessly, your pic shows.

Difference - wired connection does https content inspection (for most sites). Wireless is more forgiving, ignoring the above - mainly use it for testing purposes. Some sites don't like to be MITM (man in the middle) inspected.

 

Chrome on iPhone uses the same engine as iPhone’s safari so there shouldn’t be a difference... just FYI