My next struggle with VestaCP happened after I had uploaded my WordPress script files and was ready to install WordPress.  When I typed my sub-domain in the address line hoping to get the WordPress Installation Window, nothing happened.  Page couldn’t be found. Darn!

Then followed almost an hour or more of swotting up how the DNS records work. I Googled it and found some documentation at Servermom.org. That provided a learning curve but didn’t solve my problem. I was reminded of the reason I had ditched VestaPanel in 2014 when I had installed it on my first VPS and was wondering whether that was going to happen again.  I just couldn’t get the DNS to work. And then it worked!  Turned out that it had been a simple matter of needing the sub-domain to propagate first.

Usually with cPanel the subdomain propagates immediately, but with VestaCP one has to give the newly created subdomain some time to propagate first.  Whilst still working on the DNS and wondering what I could do to fix it, I discovered that the Domain had finally resolved to the WordPress Installation page.  I was in the process of installing my first WordPress site with VestaCP.  What a great relief that was!