@PatrikG:
The way
Let's Encrypt works is their SSL Certificates are good for
3 months, thus reducing abuse and hacking risks, BUT it also means that transition periods (time between one key expiring and a replacement going online and then that replacement's Start time/date to get here) has quadrupled. This SSL renewal process is a
lot more streamlined than in was only ten years ago (before services like Let's Encrypt even existed openly) and yes, there's a server-side software that's running all of those thousands of
Let's Encrypt renewals DreamHost tends to, but there are also
pre-written scripts and apps available allowing admins and end-users to do the same for themselves "on the spot" if the hosting company doesn't support Let's Encrypt directly.
HTTP to HTTPs redirection, or forced HTTPs,
IS TURNED OFF intentionally at the moment during the
backup,
relocation and upgrade periods.
ETA: Probably tomorrow night or earlier, depending on a few tests.
Years of suffering... Honestly, I don't even know why it took this long for someone to do any of this. I just spoke with one of the Tiny Core Admins earlier today who claims to be a SMF expert (and why we won't be making any changes/enhancements to the forum.) What I don't get is if people are so experienced, why they didn't fix these problems years ago? However, I am very happy that you're happy and by tomorrow evening, hopefully everyone is happy! That's a lot of Happy!!!