[deanhills]

The only consequences I can think when you change your SSH port are you wouldnt be able to login into your VPS if you forget it, so better to take note of it, another thing is if you are using firewall to close all port and forgot to open your new SSH port.

I also learned the hard way that my VestaCP wouldn't work any longer - it came up with a 502 and no matter what I did including restarting VestaCP - it just wouldn't work even with all of the suggestions of how to tweak the firewall and VestaCP.  I've now learned that with certain aspects of VPSs it is much easier to reload the OS and also reinstall VestaCP than to try and tweak VestaCP.  What was nice for me though is that after I had reloaded the OS and reinstalled VestaCP, VestaCP was able to pick up on the new port number automatically.  That I found interesting.  Everything after that worked perfect as well.  No issues with any of my usual installations and working with WordPress.  Right now I'm a very happy camper.  I spent a good portion of yesterday reloading all of my Websites and am now back where I was before the issue with the bad logins grabbed my attention.  It was worth it for me.  From now on I'll change my port number of a VPS as standard procedure.  Depending on how secure my VPS is, I'll also remove password authentication and use PuTTy Gen keys.