So after an absence of three months including a major jump over continents to the US, I was able to knuckle down and work with my Websites. Everything so far has been working fine. I started a brand-new Website: Namecheap was still relatively cheap. Namecheap still works as it should. HostUs.us, my favourite VPS provider, is still providing its great service. I managed to renew the service for yet another year.
Highlight for me when updating my Websites and creating a new one was MyVestaCP. Dpeca (Forum Name), the site owner, has taken on a huge responsibility with creating a fork from the original VestaCP panel. VestaCP went down the tubes towards end of 2019 as admin were leaving the Forum and there were not enough resources to maintain the script. Hacking of Websites were rampant because of an out of date script. So Dpeca was responsible for creating a Debian Fork for maintaining his own number of VPSs he was responsible for. Looks like Dpeca has yet again done some changes to the fork and it is taking on a unique personality of its own. All for the good.
One great consequence of my change from VestaCP to MyVestaCP is that I had to change from CentOS to Debian distribution that in the end was a great change in overall. Debian to me is much leaner and focused whereas CentOS is big, bulky and chaotic. Rest in peace CentOS.
Not sure how HestiaCP is doing, but at the time when I changed to MyVestaCP in 2020 I had great difficulties with using HestiaCP. A host of a free Website service of which I had a Website with tried to change from VestaCP to HestiaCP and to run all of the Websites off HestiaCP. It had been a painful experience which eventually led to the host discontinuing the service. Probably need to revisit HestiaCP to see how it is doing and whether it has managed to overcome all of its challenges. I still feel much more comfortable with MyVestaCP entirely due to the effort of the owner of the fork, Dpeca, who has a vested interest in maintaining and updating the script for use with Debian only.