Just get my domain name served up - not the web pages!

[briangriffin]

Hi,

Installed Vesta fine on CentOS 6.4 - everything seems to be up & running OK on my VPS. I've created a mydomain.conf config file for my website in the nginx conf.d and restarted nginx. But no matter what I do when I browse to my site all I get is the domain name shown in large text, not my pages served up.

I have ticked "nginx support" for the domain, I can see entries in the access log and even one or two of the usual favicon errors in the error log, but I never get to see my site pages - just a white page with the domain name and underneath it "Powered by VESTA" in small text. I've tried suspending & unsuspending the web service in Vesta without success.

Can anyone suggest a fix please?

Thanks,

Steve

[briangriffin]

Hmm.. that's odd. I just stopped httpd and now I get an error 500 when browsing to my site. I assumed that ticking "enabled nginx support" for my site meant it would be using nginx & not httpd? Now I'm confused! :-)

Steve

[briangriffin]

OK so to answer my own question (bad form, I know!). Seems there's a /home/admin/web/ directory in which the mydomain.com has its own file structure. I needed to transfer what I'd originally had in /var/www/html/mydomain.com into /home/admin/web/public_html is that right?

Can someone point me at the documentation for Vesta please - looks like things are done a little different to what I was expecting.

Despite Vesta using httpd & nginx I didn't need to create a virtualhost in httpd.conf, I didn't need a separate mydomain.conf in nginx I needed to put my site in /home/admin/web/public_html

Is there a way to tell Vesta to use the standard document root structure of httpd & nginx instead of /home/USER/web/ ?

Steve

[skid]

Hi Steve,

that's right Vesta automatically create nginx and apache configuration. You don't have to do it manually. As for the document_root location only /home/admin/web/%domain%/public_html is supported at the moment.

Unfortunately control panel documentation is not ready yet. Please fee free to ask any question here.

[briangriffin]

Thanks for the reply! Looking forward to documentation and trying Vesta with WHMCS.

Keep up the good work, it's looking very promising.

Steve

[skid]

The WHMCS setup is quite easy

Code: Select all

cd /home/wex/web/billing-whcms-site.ltdr/public_html/modules/servers
mkdir vesta
wget http://c.vestacp.com/0.9.8/rhel/whmcs-module.php -O vesta.php

[SANDPOND]

Hello:

A way to change the default document root is needed!. Very often it is better to install an application in a specially named subdirectory, like "wordpress", "drupal", "myapp", etc, rather than dumping all of the web files and directories into the "/public_html/" webroot.

I suggest to include an option for each Vesta Package type for setting a custom document root (subdirectory).

I think a lot of people are hung up on this problem. Yes, it is possible to do workarounds in the apache2 and NGINX config files, do rewrites, or use ugly .htaccess directives, but this adds unnecessary complexity to the Vesta/Webserver installation.

Vesta is becoming popular with application developers because they can use the Vesta CLI to develop deployment and management systems.

Keep up the good work Vesta, but please considering adding a way to change the document root to a custom subdirectory as soon as possible.

THANKS !

As for the document_root location only /home/admin/web/%domain%/public_html is supported at the moment.

P.S.: Need CLI documentation too !