"I hate web interface at port 8083" No problem, I have solution for this
Posted: Thu Oct 13, 2016 5:16 pm
Hi guys,
By default VestaCP web interface runs with SSL on port 8083, but isn't easy to access, because you need to remember correct address and always ignore SSL not validated to login.
Then, I have a workaround (or solution if you like) for this. Then Let's go.
On my example, I have my VestaCP panel on https://amazing.subdomain.vestacp.net:8083/
1 - On existing user (or create, you decide) create domain, that remember, this domain will be used only for this.
Ex: I created cool-panel.vestacp.net on panel user.
2 - With root or admin user, go to user owner of domain created and go to "conf" and "web"
Ex:
root@srv:# pwd
/home/panel/conf/web
3 - VestaCP apache and nginx config was created to be extended (thanks VestaCP team, you're amazing), then You will create a apache specific file for domain with your favorite editor.
Ex:
root@srv:# vim apache2.cool-panel.vestacp.net.conf // Debian like
root@srv:# vim http.cool-panel.vestacp.net.conf // Centos like
4 - We will make domain created as reverse proxy to VestaCP panel, then, edit file as below, save and quit
5 - Enable reverse proxy for apache
Ex:
root@srv:# a2enmod proxy
root@srv:# a2enmod proxy_http
4 - Test if all is okay with apache2ctl -t (or apachectl -t on CentOS)
5 - If is all okay, then restart your apache server and done, you can access VestaCP panel on specific domain.
Note: VestaCP will work on reverse proxy only if is on /, will not work on /panel /vesta /vestacp /cpanel /zpanel /bla-bla-bla and others.
By default VestaCP web interface runs with SSL on port 8083, but isn't easy to access, because you need to remember correct address and always ignore SSL not validated to login.
Then, I have a workaround (or solution if you like) for this. Then Let's go.
On my example, I have my VestaCP panel on https://amazing.subdomain.vestacp.net:8083/
1 - On existing user (or create, you decide) create domain, that remember, this domain will be used only for this.
Ex: I created cool-panel.vestacp.net on panel user.
2 - With root or admin user, go to user owner of domain created and go to "conf" and "web"
Ex:
root@srv:# pwd
/home/panel/conf/web
3 - VestaCP apache and nginx config was created to be extended (thanks VestaCP team, you're amazing), then You will create a apache specific file for domain with your favorite editor.
Ex:
root@srv:# vim apache2.cool-panel.vestacp.net.conf // Debian like
root@srv:# vim http.cool-panel.vestacp.net.conf // Centos like
4 - We will make domain created as reverse proxy to VestaCP panel, then, edit file as below, save and quit
Code: Select all
ProxyRequests Off
SSLProxyEngine on
SSLProxyVerify none
SSLProxyCheckPeerCN off
SSLProxyCheckPeerName off
SSLProxyCheckPeerExpire off
ProxyPass / https://127.0.0.1:8083/
ProxyPassReverse / https://127.0.0.1:8083/
Ex:
root@srv:# a2enmod proxy
root@srv:# a2enmod proxy_http
4 - Test if all is okay with apache2ctl -t (or apachectl -t on CentOS)
5 - If is all okay, then restart your apache server and done, you can access VestaCP panel on specific domain.
Note: VestaCP will work on reverse proxy only if is on /, will not work on /panel /vesta /vestacp /cpanel /zpanel /bla-bla-bla and others.