• The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

Issue SSH from Plesk server showing wrong IP on remote server

brainforge

Basic Pleskian
At command line on Plesk server - using putty.
who am i shows the correct IP address from where the ssh session comes from.

On the Plesk server I have a number of additional IP addresses.

On Plesk server command line
PleskServer$ ssh myotherserver

Logs into the other server OK.
Then check origination IP ...
myotherserver$ who am i

Shows one of the additional IPs (always same one) as the session originator not the main server IP.
Does not matter which account (including root being used on the Plesk server).
Was working fine prior to Obsidian 18.0.38 Update #2

Reverse DNS for each IP correct - have not been changed.
 
If you just want to tell ssh to use a specific IP, try '-o BindAddress=<IP>' or put that option in /etc/ssh/ssh_config.
To determine why the default IP changed, let's start with the output of `ifconfig` and `ip addr`.
 
Back
Top