We are happy to announce that Vesta is back under active development as of 25 February 2024. We are working on v1 candidate and expect to engage more with the community over the coming months. We are committed to open source, and we encourage contributors to help us build the future of Vesta.
Can't access my site after installing and configuring Vesta
Can't access my site after installing and configuring Vesta
Hello all!
I'm a total newbie regarding server issues :(
I've bought VPS, on which apache was preinstalled (httpd) - I've run installation, it told me that httpd is already installed, so I did -f --apache no, and on the things to install there were no apache server (just nginx)
Before, I could access my webserver at mysite.myprovider.pl.
The files were stored in var/www/html
After installing vesta I have created ftp etc.
So my path now is home/admin/web/mysite.myprovider.pl
But when I type to the address bar mysite.myprovider.pl chrome tells "server rejected connection" :(
So i guess something is wrong with DNS?
Vesta gave my nameservers like ns1.something.ltd (there were something I don't remember for "something" :))
So I edited them in user admin to the ns1.myprovider.pl, ns2, ns3.
Then, at DNS, changed the SOA, ns1 and ns2 records to corresponding myprovider.
Probably I'm doing something wrong. Could you please tell me what? :)
Thanks!
edit:
I will just add that I can access my vesta at two addresses:
mysite.myprovider.pl:8083
IPX.x.x.x:8083
All I have parallels panel, that I can access with different ports from vesta.
I'm a total newbie regarding server issues :(
I've bought VPS, on which apache was preinstalled (httpd) - I've run installation, it told me that httpd is already installed, so I did -f --apache no, and on the things to install there were no apache server (just nginx)
Before, I could access my webserver at mysite.myprovider.pl.
The files were stored in var/www/html
After installing vesta I have created ftp etc.
So my path now is home/admin/web/mysite.myprovider.pl
But when I type to the address bar mysite.myprovider.pl chrome tells "server rejected connection" :(
So i guess something is wrong with DNS?
Vesta gave my nameservers like ns1.something.ltd (there were something I don't remember for "something" :))
So I edited them in user admin to the ns1.myprovider.pl, ns2, ns3.
Then, at DNS, changed the SOA, ns1 and ns2 records to corresponding myprovider.
Probably I'm doing something wrong. Could you please tell me what? :)
Thanks!
edit:
I will just add that I can access my vesta at two addresses:
mysite.myprovider.pl:8083
IPX.x.x.x:8083
All I have parallels panel, that I can access with different ports from vesta.
-
- Collaborator
- Posts: 783
- Joined: Mon May 11, 2015 8:43 am
- Contact:
- Os: CentOS 6x
- Web: apache + nginx
Re: Can't access my site after installing and configuring Vesta
Vesta has a wrong config because you have changed the install to apache=no, vesta thinks that apache is not used. Also, your files are in the wrong location. Vesta doesn't use the /var/www directory.
Backup your database, website files in /var/www reinstall a clean OS (No Apache or other software preinstalled) and install vesta cp. Upload your files to /home/username/web/domainname.com/public_html
Backup your database, website files in /var/www reinstall a clean OS (No Apache or other software preinstalled) and install vesta cp. Upload your files to /home/username/web/domainname.com/public_html
Re: Can't access my site after installing and configuring Vesta
Hello Tjebbeke, thank you for your reply.
The domain is pingable, I've also made another domain on freenom and it also points to my server ip. So I'm gonna start from fresh install.
I have an option to reinstall OS, but it comes with preinstalled httpd (apache) from very begining. Uninstalled packages on fresh install, installed vesta and... yay, it works! Thank you, I thought that if apache is preinstalled so vesta doesn't need to install it again :)
Yes, that was default location for original apache I think, because I could see the site from there. I've placed the files for vesta in home/admin/web/domain... path, and still connection refused.Vesta has a wrong config because you have changed the install to apache=no, vesta thinks that apache is not used. Also, your files are in the wrong location. Vesta doesn't use the /var/www directory.
The domain is pingable, I've also made another domain on freenom and it also points to my server ip. So I'm gonna start from fresh install.
I have an option to reinstall OS, but it comes with preinstalled httpd (apache) from very begining. Uninstalled packages on fresh install, installed vesta and... yay, it works! Thank you, I thought that if apache is preinstalled so vesta doesn't need to install it again :)