Scale up as you grow — whether you're running one virtual machine or ten thousand.

From GPU-powered inference and Kubernetes to managed databases and storage, get everything you need to build, scale, and deploy intelligent applications.

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!
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.
Hello,
In case that anyone comes across this in the future, here are a few suggestions that might help:
1. Checking SSL Certificates
Ensure that the paths to the SSL certificates and keys are correct in both the nginx and apache configs:
SSLCertificateFile should point to your full chain certificate (e.g. /home/admin/conf/web/ssl.xxxxxxx.com.pem).SSLCertificateKeyFile should point to your private key (e.g. /home/admin/conf/web/ssl.xxxxxxx.com.key).The error message you’re seeing in Firefox (“the authenticity of the received data could not be verified”) could be due to a problem with the SSL certificate, so it’s worth double-checking this.
2. Check Nginx to Apache Proxy Settings
In your nginx configuration, you are proxying requests to https://192.168.1.2:8443. Ensure that Apache is correctly configured to accept these proxied requests over SSL. If it’s not set up correctly, nginx could be attempting to proxy requests to Apache over SSL, while Apache is not configured to accept these requests, leading to the error.
To diagnose this, you might want to temporarily change the proxy pass in nginx to use http (e.g., proxy_pass http://192.168.1.2:8443;), and see if you can access your website over HTTP. If this works, then the issue is likely related to how Apache is configured to handle SSL.
3. Check VestaCP settings
VestaCP should handle the generation of the Apache and Nginx configurations automatically when you install an SSL certificate using the VestaCP interface. You might want to try reinstalling the SSL certificate using the VestaCP interface, and see if this resolves the issue.
4. Check Logs
When you’re seeing the issue, check the logs at /var/log/apache2/domains/xxxxxxx.com.error.log and /var/log/nginx/error.log for any error messages. These might provide a clue as to what is going wrong.
Best,
Bobby