I know. A friend of mine runs a small private server where I host my stuff, and the SSL cert expires every now and then, it'll be down for a while until he wakes up and pokes it.
I guess for this one I can edit it and just upload the image directly (I don't normally do that so I don't use too much of the server's bandwidth.)
I see he is using a simple Self-signed one; they're often quite easy to automate. While just tangential to my proficiency I could have a quick chat with him and then throw the appropriate tutorials for the specific hosting solution (and a helping hand, if needed) at him to never have to renew it manually again.
Nah, he knows what he's doing. As I understand it, one of the other hosted domains on his server pointed their domain off-server, and this triggers a review. I understand that invalidating the certificate until it's checked is the desirable outcome.
I know. A friend of mine runs a small private server where I host my stuff, and the SSL cert expires every now and then, it'll be down for a while until he wakes up and pokes it.
I guess for this one I can edit it and just upload the image directly (I don't normally do that so I don't use too much of the server's bandwidth.)
Boo technical issues.
You can usually have a job autorenew the certificate, which would help with the downtime.
I think he likes his setup - because he's running a bunch of different spaces for people, it gives him the impetus to check in on them.
FWIW CertBot does send an email when your cert is about to expire, and then renews it for you.
I am informed that the server does, in fact, run certbot - and certbot invalidated the certificate :)
It's fixed now.
Yeah, a simple cron job fixed the issue.
Every now and then is every 90 days.
I see he is using a simple Self-signed one; they're often quite easy to automate. While just tangential to my proficiency I could have a quick chat with him and then throw the appropriate tutorials for the specific hosting solution (and a helping hand, if needed) at him to never have to renew it manually again.
Nah, he knows what he's doing. As I understand it, one of the other hosted domains on his server pointed their domain off-server, and this triggers a review. I understand that invalidating the certificate until it's checked is the desirable outcome.