VesctaCP 1.0.0 Stuck on "IT WORKS PAGE" Topic is solved

[rj2010ism]

Hello...

How to fix VestaCP latest Version: 1.0.0 (x86_64) Release: 6 errors? after new server install it works.
but after few min or seconds when you upload your site data it just stuck at the page (IT WORKS powered by VestaCP).

How can this be solved?

Also notice the LE not working? tried manual but still no luck.

Is this build of VestaCP corrupted?

The site say: LATEST VERSION (Jan 22): 0.9.8-26 but when installing you get V1.0.0 ?

[sandro]

You need to verify that the DNS entry is correctly created with the public IP.

You need to verify that the web domain is also created with the public IP.

These are the first steps for you to find out what is going on.

[rj2010ism]

You need to verify that the DNS entry is correctly created with the public IP.

You need to verify that the web domain is also created with the public IP.

These are the first steps for you to find out what is going on.

Iv Checked all. it all seems correct...

-----------Public IP---------------------
162.22.xx.xx points to rev.tld.com
rev.tld.com point to 162.22.xx.xx
-------------------------------------------

-----------------Domain-----------------
tld.com (A) record pointing to IP

NS1.tld.com pointing to IP
NS2.tld.com pointing to IP


Previous version of Vesta didn't have this issue

[sandro]

I agree with you that version 0.9.8 didn't have this kind of bug and that's why I didn't update Vesta on my production servers.

I'm starting the tests now with version 1.0.

I think your problem is in the <webdomain>.httpd.conf file located at /home/<user>/conf/web.

Maybe some error related to the apache virtualhost configuration.

[rj2010ism]

I agree with you that version 0.9.8 didn't have this kind of bug and that's why I didn't update Vesta on my production servers.

I'm starting the tests now with version 1.0.

I think your problem is in the <webdomain>.httpd.conf file located at /home/<user>/conf/web.

Maybe some error related to the apache virtualhost configuration.

Managed to get it working..

Solution iv found somewhere on the forum :

Change Web Template httpd: from (Default) to (hosting)
Proxy Template nginx: from (Default) to (hosting) Then save..

After save restart httpd....

Then Change back to (Hosting) to (Default) worked for my issue...

Now page load correctly..

[sandro]

Nice.

I will check these files and compare them with the ones from version 0.9.8.

Thanks for sharing the solution.

[imperio]

Can you provide access to your server ? We will check what wrong

[rj2010ism]

Can you provide access to your server ? We will check what wrong

At moment is working..
Iv also notice something strange. Iv used ( Inter Server VPS ) As test and found that Lets Encrypt (LE) doesn't work.. Then tried another VPS Provider.. But came to my 3rd VPS provider and all sudden everything works..

So my question is: Is Lets Encrypt (LE) Blocked on some providers,(ISP) or is the latest script not functioning correctly on some ISP DNS/IPs? Strange..

[sandro]

In fact, LetsEncrypt can block IPs that have an error when creating the certificate.

If this request is recurring, then LetsEncrypt blocks the IP for a certain time.

I've had this problem in the past, but I've never had any issues with VestaCP in version 0.9.8.