Intermittent errors when serving VestaCP through nginx reverse proxy
Posted: Wed Sep 19, 2018 12:50 pm
I am trying to configure a "website" in VestaCP, which serves as a way to access the panel on port 443 instead of 8083.
I created a new template, vestaproxy.stpl (and .tpl of course), which looks like this: https://pastebin.com/e6vYerDC
This seems to work pretty well, but for some reason, we get intermittent "Connection refused" errors, mostly when updating or deleting users/websites. The item in question is still deleted as it should, but it is very annoying to have to go back and then reload to see if it actually worked.
Has anyone else had a similar problem?
Steps to reproduce:
1. Install VestaCP on a fresh Debian 9 (nginx + apache version)
2. Download my templates
3. Create a new vhost through VestaCP to access it from in the future
4. Add SSL of whatever kind makes you happy
5. Visit the panel through the new domain, e.g. https://vesta.example.com:443
6. Create a new website with whatever bogus settings you want and try to delete it again. Result should be an error from the browser because the server returned an empty response. Sometimes it also shows as connection refused or even a VestaCP error saying that it doesn't exist.
If you cannot reproduce, I have a blank server that shows this exact behaviour.
I created a new template, vestaproxy.stpl (and .tpl of course), which looks like this: https://pastebin.com/e6vYerDC
This seems to work pretty well, but for some reason, we get intermittent "Connection refused" errors, mostly when updating or deleting users/websites. The item in question is still deleted as it should, but it is very annoying to have to go back and then reload to see if it actually worked.
Has anyone else had a similar problem?
Steps to reproduce:
1. Install VestaCP on a fresh Debian 9 (nginx + apache version)
Code: Select all
curl -sO http://vestacp.com/pub/vst-install.sh
bash vst-install.sh \
--force --nginx yes --apache yes --phpfpm no --vsftpd no --proftpd no \
--named no --mysql yes --postgresql no --exim no --dovecot no --clamav no \
--spamassassin no --iptables yes --fail2ban yes --quota no --lang en \
--interactive no --hostname $(hostname --fqdn) --email [email protected]Code: Select all
wget -O $VESTA/data/templates/web/nginx/vestaproxy.stpl https://pastebin.com/raw/e6vYerDC
wget -O $VESTA/data/templates/web/nginx/vestaproxy.tpl https://pastebin.com/raw/RAmuUrCeCode: Select all
v-add-web-domain admin vesta.example.com
v-change-web-domain-proxy-tpl admin vesta.exaple.com vestaproxy5. Visit the panel through the new domain, e.g. https://vesta.example.com:443
6. Create a new website with whatever bogus settings you want and try to delete it again. Result should be an error from the browser because the server returned an empty response. Sometimes it also shows as connection refused or even a VestaCP error saying that it doesn't exist.
If you cannot reproduce, I have a blank server that shows this exact behaviour.