We are happy to announce that Vesta is back under active development as of 25 February 2024. We are working on v1 candidate and expect to engage more with the community over the coming months. We are committed to open source, and we encourage contributors to help us build the future of Vesta.
Different ways to access the VestaCP Panel
-
- Posts: 27
- Joined: Wed Jan 03, 2018 5:57 pm
- Os: Debian 8x
- Web: apache + nginx
Different ways to access the VestaCP Panel
Hello,
Actually, I can access the VestaCP panel with a lot of ways: MY-IP:8083, MY-SERVER-HOSTNAME:8083, SITE1:8083, SITE2:8083...
Basically every domains.
Is there a way to limit only to one solution? Let's say only login with my server hostname?
Thank you.
Actually, I can access the VestaCP panel with a lot of ways: MY-IP:8083, MY-SERVER-HOSTNAME:8083, SITE1:8083, SITE2:8083...
Basically every domains.
Is there a way to limit only to one solution? Let's say only login with my server hostname?
Thank you.
Re: Different ways to access the VestaCP Panel
I use MY-IP:8083 and is working properly
-
- Support team
- Posts: 1096
- Joined: Sat Sep 06, 2014 9:58 pm
- Contact:
- Os: Debian 8x
- Web: apache + nginx
Re: Different ways to access the VestaCP Panel
You can make a rule in Firewall to deny all access to 8083 but allow only, something like this
Be very very cautious, make sure you have console access to your server before playing with firewall, you can lose access to whole server
Code: Select all
iptables -I INPUT -p tcp ! -s yourIPaddress --dport 8083 -j DROP
Re: Different ways to access the VestaCP Panel
The easiest way, is using Vesta's templates.
Main Vesta site has locations for your distro. (Assuming nginx reverse proxy).
In nginx templates for proxy:
Copy default.tpl and default.stpl to vesta_proxy.tpl and vesta_proxy.stpl repectively.
Change the %proxy_port% (not looking at the files, I'm on mobile) to 8083. Save them.
Then create a subdomain of your site. Say 'cp.mydomain.tld' and choose proxy template we created.
Visit in browser. Make sure it works.
Firewall -> add a rule, drop/block 8083 port.
Now, outside can not access it, but cp.mydomain.tld can.
Easy :-)
Main Vesta site has locations for your distro. (Assuming nginx reverse proxy).
In nginx templates for proxy:
Copy default.tpl and default.stpl to vesta_proxy.tpl and vesta_proxy.stpl repectively.
Change the %proxy_port% (not looking at the files, I'm on mobile) to 8083. Save them.
Then create a subdomain of your site. Say 'cp.mydomain.tld' and choose proxy template we created.
Visit in browser. Make sure it works.
Firewall -> add a rule, drop/block 8083 port.
Now, outside can not access it, but cp.mydomain.tld can.
Easy :-)
Re: Different ways to access the VestaCP Panel
nice tip
thanks !
thanks !