I am having a problem with my HestiaCP. I hired our regular sysadmin and asked him to update our CP.
I also asked for him to do some redirects on a subdomain we have setup years ago.
Here’s what happens, after he updated Hestia and said the redirects from http to https were done. Not only HestiaCP got broken but also the subdomain SSL was gone.
I am not a Sysadmin or a DevOps I can only do a few things but maybe you can help me out finding a way to a solution he has said he used this post: Update Hestia v1.6.8
Yes, me neither. Most of all because he was managing it for 3 years.
When someone needs to make up an excuse it is how it goes.
I am 99,9999% sure he broke everything because he rushed everything.
If there was an uprade using apt, he may have told the installer to overwrite your server configs instead of keeping the exsting ones. It’s a rookie mistake that I wouldn’t expect from someone who has been working on your HestiaCP server for three years, but it is a plausible explanation.
Eris is a genius.
I was already thinking I take everything down and rebuild the server again!
sahsanu, you know when it comes a time when you figure out that you thought you were in great hands and weren’t… this was the case I am sure that under the hood there will be a ton of errors and leftovers.
I am so very thankful to you all, and Eris I got no words to thank you enough