A few days ago, I started with letsencrypt. We already had a SSL certificate for certain pages, but not sitewide (eg for payment pages, we never had any problems with those).
It’s a Windows Server with Apache, so I generated everything with letsencrypt-simple-win client. Updated my https-ssl.conf file to use the new certificates, restarted Apache and voila, everything worked fine for our test domain.
After making sure everything worked on test, I repeated the steps for our production domain. Everything went smooth and after some more testing I sent out an email to others involved letting them know that we now had sidewide SSL.
No 20 minutes later I get a panicked mail that our site was down. Somehow the website timed out. So I disabled the forced use of SSL and could reach the site via http just fine. The apache service is also still running and I can’t find anything of interest in the log files. Still https keeps timing out.
So after some googling, some minor config changes and some more testing on our test site (which is by the way hosted on the same server, just another subdomain), I tried again yesterday. Again, it took about 20 minutes before SSL went down.
I’m no server admin, just a webdev, so my knowledge about this stuff is limited. What can I do to troubleshoot?