Issue Redundant error after changing ssh port with plesk extension - SSH Terminal - 1.3.8-111

[serreri]

Server operating system version

Plesk Obsidian v18.0.65_build1800241122.08 os_Ubuntu 22.04

Plesk version and microupdate number

Plesk Obsidian Web Host Edition 18.0.65

Hello everyone,
I have always noticed that if you change the ssh port in /etc/ssh/sshd_config
eg: from port 22 to port 22xx
if you then log in to SSH Terminal of plesk after having changed the port from 22xx to port 22 again
then an infinitely repeated error occurs:
ssh: connect to host 127 .0.0.1 port 22xx: connection refuses
ssh: connect to host 127 .0.0.1 port 22xx: connection refuses
ssh: connect to host 127 .0.0.1 port 22xx: connection refuses
... etc
with a popup in plesk with the warning
CONNECTION INTERRUPTED.

If you do not exit the page immediately, the message repeating infinitely creates a problem for the server, blocking it with no way to intervene except locally.

Hoping to have been clear in my problem, it is this:

1. is there a cache that is maintained by SSh Terminal of Plesk?
2. if it exists, how to restore the functionality of the Ssh Terminal extension of plesk so that it reads the port correctly once changed??

I also tried to use:
systemctl restart plesk-ssh-terminal.service

after the server is back up and running, but Ssh terminal I don't know why it always sees the old port and not the new one, i.e. port 22.

I would like to uninstall SSh terminal but I'm afraid that doing so could create a problem for plesk

Hi everyone Thanks

 

[Vladimir C.]

Hello! This behavior caused by known SSH Terminal extension bug EXTPLESK-5050:
https://support.plesk.com/hc/en-us/...when-SSH-port-is-customized-Connection-Broken

As a workaround, after changing SSH port update SSH terminal configuration:

/usr/local/psa/admin/sbin/modules/ssh-terminal/installer --update-configuration

And only after that restart service:

systemctl restart plesk-ssh-terminal.service

Please let me know if the issue still persist after that.