1. Log into your Vesta Control Panel.
   
2. Click on Firewall on Your Vesta menu
   
3. Click on the Green Plus button to add the New Port
   
4. I will be changing my port to 2019.  For the new port, add the details as follows:
   
   
   Code:

   Action:  ACCEPT

Protocol: TCP

Port: 2019

IP Address: 0.0.0.0/0
   
   Then click Add, to add the new port to your Firewall.
   
5. Next edit the NGINX config file to listen to the new port, in my case 2019.
   
6. To do this, login into your SSH client. Make sure you are the root user or a user with root (sudo) privileges.
   
7. Issue the following command:
   
   Code:

   sudo vi /usr/local/vesta/nginx/conf/nginx.conf
   
   
   
8. Press the INSERT key.
   
9. Scroll down to the area which says:
   
   Code:

   listen 8083;
   
   
   
10. And change it to:
    
    Code:

    listen 2019;
    
    
    
11. Then exit out of the editor by pressing Esc key and then type :wq and press Enter.
    
12. Then restart Vesta using the Command below.
    
    Code:

    sudo service vesta restart
    
    
    
13. Now log into your VestaCP using the new port as follows.
    
    Code:

    Your-IP-Address:2019
    
    
    
14. Finally, you may delete the old port, 8083.
    
    To delete the port 8083 from your Firewall, just click on Firewall on your Top Menu within Vesta.
    
    Then hover over port 8083 and delete it.
    

(11-01-2019, 09:54 AM)sohamb03 Wrote: Nay this wouldn't break anything in Vesta. It's indeed good you change the default stuff, as it'll prevent everyone from getting to the login interface. Personally I've Vesta running on a completely separate port than 8083.

It might as well afford protection against bruteforce attacks. Although fail2ban is very efficient, still this is extra protection.

And yes, this also helps if you've something else running on Vesta's default port, which can be more cumbersome to change than this one. This is a really simple tutorial as well as a process which anyone can follow from newbies to intermediates to advanced users.

Regards,

(11-01-2019, 11:17 AM)Hidden Refuge Wrote: It simply protects from automated brute force attacks which today are mostly 99% of all attacks thanks to huge automated botnets. 1% are the people you mentioned that would simply run a port scan or similar to find the new port.

That's usually how changing a default port to a non default port helps with brute force attacks. Generally this is helpful because it really stops all automated brute force attacks and thus can even drop down the load on the system (depending on the volume of the brute force attack).