25 Mar
2018
25 Mar
'18
7:47 p.m.
Others have had this issue. The underlying problem: the certificate chain is incomplete on the web server.
It's actually not that. It's that certbot-auto was configuring my older apache in a way that caused it not to load the intermediate certs from the full chain. I've fixed it now.
I submitted ticket 5663 for the problem.
And I've deleted it. The issue tracker is for CHIRP bugs, not transient infrastructure issues.
Thanks to both of you for letting me know. I'm not sure how I haven't noticed since I converted the site to letsencrypt a few months ago.
--Dan