How to Change SSH Port on Ubuntu
- Thread starter ChrisM
- Start date
Same here. I just connect twice via terminator and make sure I don't fudge stuff up.
What if it is a dedi and you have no kvm?If you do royally fudge up, there's always the console.
Then it gets to be a hassle...
365Networks
New Member
To do this for dropbear is quite simple, on Debian/Ubuntu based systems:
Head to /etc/default/dropbear:
You may have a quite a few lines or you may have little, this just depends on how it was installed.
# disabled because OpenSSH is installed
# change to NO_START=0 to enable Dropbear
NO_START=0
# the TCP port that Dropbear listens on
DROPBEAR_PORT=51096
# any additional arguments for Dropbear
DROPBEAR_EXTRA_ARGS=-g
As seen above, you will want to have DROPBEAR_PORT=51096 on a line to change the default dropbear port.
To disable root password login, root logins, etc. you will need to have DROPBEAR_EXTRA_ARGS=xxxxx on another line.
-g = Disable password logins for root
-s = Disable password logins
-w = Disable root logins
An example would be DROPBEAR_EXTRA_ARGS=-s to disable password logins on all accounts including root.
Finally you will want to service dropbear restart or /etc/init.d/dropbear restart to finalize the changes.
This is taken from my other post. Just thought it would help some others.
Head to /etc/default/dropbear:
You may have a quite a few lines or you may have little, this just depends on how it was installed.
# disabled because OpenSSH is installed
# change to NO_START=0 to enable Dropbear
NO_START=0
# the TCP port that Dropbear listens on
DROPBEAR_PORT=51096
# any additional arguments for Dropbear
DROPBEAR_EXTRA_ARGS=-g
As seen above, you will want to have DROPBEAR_PORT=51096 on a line to change the default dropbear port.
To disable root password login, root logins, etc. you will need to have DROPBEAR_EXTRA_ARGS=xxxxx on another line.
-g = Disable password logins for root
-s = Disable password logins
-w = Disable root logins
An example would be DROPBEAR_EXTRA_ARGS=-s to disable password logins on all accounts including root.
Finally you will want to service dropbear restart or /etc/init.d/dropbear restart to finalize the changes.
This is taken from my other post. Just thought it would help some others.
Last edited by a moderator:
Uhh @KnownHost-ChrisM there's nothing here
Last edited:
Uhh @KnownHost-ChrisM there's nothing here
@MannDude vpsBoard broke my thread sometime in the last few years... lol
Most likely was outdated anyway. I will add fixing this to my to-do list along with make some new tutorials might get some up tomorrow.
Last edited by a moderator:
The extremely simple way would be to run this in cmd:
Replace 48652 with whatever port you want SSH to run on.
And make sure the new port is opened in your firewall so you don't get locked out.
Also, don't close previous SSH session before you open a new one on the new port to make sure everything's working fine.
Code:
sed -i 's/22/48652/' /etc/ssh/sshd_config
service ssh restartReplace 48652 with whatever port you want SSH to run on.
And make sure the new port is opened in your firewall so you don't get locked out.
Also, don't close previous SSH session before you open a new one on the new port to make sure everything's working fine.
Yeah. Lovely IPB and the transition between 3.X and 4.X resulted in some threads having data loss. We thought we got it all by some workaround and fixes we did, however in the end I guess this one slipped through the cracks.
tldr: edit /etc/ssh/sshd_config file. The line that ssays "Port 22" change to "Port 48652" or something. Then restart the service.
tldr: edit /etc/ssh/sshd_config file. The line that ssays "Port 22" change to "Port 48652" or something. Then restart the service.
Last edited by a moderator:
mpkossen
New Member
Switch to WBB ;-)
Man I haven't heard and used Woltlab Burning Board in a long time. Man that used to be a pretty spiffy forum software. Although iirc it used to be fairly clunky.
Right now I"m a fan of Xenforo, but we'll see.