• Halloween is coming! To celebrate the occasion, we dusted off a couple of old skins, and even created a brand new one (Pixel).
    To get into the festive spirit, install the Skins extension.
  • The new Python extension is now available. It allows customers to deploy and manage WSGI-based Python applications on their websites directly from Plesk.
  • The Plesk Mobile apps for iOS and Android and the Plesk Mobile Center extension have been deprecated, and are no longer available for new installations. In Plesk Obsidian 18.0.84, the Plesk Mobile Center extension will be removed from servers during the upgrade, and the Plesk Mobile apps will lose their server management features.
  • The Social Login extension has been deprecated and will be removed in Plesk Obsidian 18.0.84. After that, it will no longer be possible to log in to Plesk with a Google, Facebook, GitHub account, or with a passkey. Plesk usernames and passwords, as well as logging in with a WebPros Account, are not affected.

Change SSH port

D

dahamsta

Guest
Is it safe to change the SSH port to something non-standard on Plesk 7.5? None of my users are allowed ssh access, so I'm really just checking to make sure it won't affect the CP in any way.

adam
 
I changed it without problems. I don't want ssh on 22 either.
 
Depends on your OS, but on Red Hat/CentOS/Fedora machines you have to edit /etc/ssh/sshd_config (insert Port 2222 for instance) and restart the SSH service.
 
After you change the file (mentioned by breun), don't forget to allow in firewall the port.
 
Originally posted by breun
Depends on your OS, but on Red Hat/CentOS/Fedora machines you have to edit /etc/ssh/sshd_config (insert Port 2222 for instance) and restart the SSH service.

When I log-in to SSH, I see {root@serv root]# I do not also see the etc on my dir list. How can I reach that file.

Thanks
Timu
 
When you login the current working directory is your home directory. If you're logging in as root this is /root. This doesn't really matter as /etc/ssh/sshd_config is an absolute path and you can just open that file with any text editor you like. (You could 'cd /etc/ssh' to change the working dir to the dir where the sshd_config file is located if you'd want to.)

If this is all not clear to you then you might want to first learn a thing or two about basic command-line operations. The Introduction to Linux guide might be a good starting point.
 
Back
Top