Question

Issue With Hosting Multiple Sites. VestaCP

Hi everyone, I am facing issue on hosting multiple sites on VestaCP panel. I dont know what the issues. The first site is working fine, but the second isnt. I havet setup any virtual hosts in Apache2 i dont know if they are required with VestaCP or not.

Here is the error in browser. http://prntscr.com/f9lyl0

In my domain, which is at Godaddy, only has nameservers in it of Cloudflare.

Here are my cloudflare settings. http://prntscr.com/f9lz1w

And here are my VestaCP settings http://prntscr.com/f9lz72 http://prntscr.com/f9lz99

I dont know whats wrong, Can you guys please help me out?


Submit an answer

This textbox defaults to using Markdown to format your answer.

You can type !ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!

Sign In or Sign Up to Answer

These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.

Want to learn more? Join the DigitalOcean Community!

Join our DigitalOcean community of over a million developers for free! Get help and share knowledge in Q&A, subscribe to topics of interest, and get courses and tools that will help you grow as a developer and scale your project or business.

@Zulqarnainkhan

With CloudFlare + SSL, in most cases, you need to head to the Crypto tab and make sure the first drop down box is set to Full (Strict).

If that doesn’t fix the issue, you’d need to check the your error logs to see if there’s an indication of what may be causing the issue(s) you’re having.

Generally, for Apache, the error logs are in:

/var/log/apache2

… and for NGINX, they are in:

/var/log/nginx

I’m not 100% sure if that’s where Vesta stores the logs as it’s been a while since I’ve used it, but that’s the default locations.

You’d want to run tail on the error logs to pull the last X lines from the logs. For example, if we wanted the last 20 lines of the NGINX error log (and NGINX is installed, of course), we’d run:

tail -20 /var/log/nginx/error.log

From there, you’d take a look at what the error log is showing to be problematic, and work to resolve that issue. Sometimes it’s a simple fix, sometimes it’s permissions related, sometimes it’s more complex. Generally, however, the error log will allow you to diagnose the issue in greater detail.

It’s important to keep in mind, a control panel is simply an overlay to what you’d normally need to do from the CLI. It’s not a complete replacement for the CLI and you still need to know how to manage, secure, and troubleshoot a web server / server environment, and potentially even OS-level issues.

A control panel can’t and won’t do these things for you. I say this as a general statement – it’s what I tell pretty much everyone who runs a control panel, whether they’re a DigitalOcean customer or not. That doesn’t matter to me :-). I like DigitalOcean and I think you would too, but I simply try to help where I can.

May be i have ssl on my domain thats why this issues coming or what? please someone help me out @jtittle

Thank you @jtittle for replying, yes everything is done and now the domain seems to be working fine and its pointed. But now there is a new problem i uploaded backup of my site and now i am getting this error, i have no clue what this is. Before the backup the VestaCP default index.html was working fine on the domain Can you please have a look at this http://prntscr.com/f9qeqg