• If you are still using CentOS 7.9, it's time to convert to Alma 8 with the free centos2alma tool by Plesk or Plesk Migrator. Please let us know your experiences or concerns in this thread:
    CentOS2Alma discussion

Resolved SSH terminal extension does not work

abanico

New Pleskian
Server operating system version
Centos 7
Plesk version and microupdate number
18.0.55 update 2
Hi all,

Since this afternoon, the SSH terminal extension of my plesk obsidian has stopped working. The extension loads, but nothing appears in the SSH window. Also the extension does not work with any client that has it enabled. SSH access does work if I use the terminal on my mac. I have tried uninstalling the extension and reinstalling it, but to no avail. I have restarted the server, but no luck either.

If I run systemctl status plesk-ssh-terminal -l I get this (domain and IPs removed by me):

● plesk-ssh-terminal.service - Plesk SSH Terminal Backend Service
Loaded: loaded (/usr/lib/systemd/system/plesk-ssh-terminal.service; enabled; vendor preset: disabled)
Drop-In: /etc/systemd/system/plesk-ssh-terminal.service.d
└─options.conf
/usr/lib/systemd/system/plesk-ssh-terminal.service.d
└─respawn.conf
Active: active (running) since jue 2023-10-19 23:47:21 WEST; 7min ago
Main PID: 11859 (plesk-ssh-termi)
CGroup: /system.slice/plesk-ssh-terminal.service
└─11859 /usr/local/psa/admin/plib/modules/ssh-terminal/libexec/plesk-ssh-terminal.x86-64 --listen /run/plesk-ssh-terminal/backend.sock --connect-to *:22

oct 19 23:47:21 domain.com systemd[1]: Started Plesk SSH Terminal Backend Service.
oct 19 23:47:21 domain.com plesk-ssh-terminal.x86-64[11859]: 2023/10/19 23:47:21 Listening on unix:/run/plesk-ssh-terminal/backend.sock
oct 19 23:52:02 domain.com plesk-ssh-terminal.x86-64[11859]: 2023/10/19 23:52:02 remote=xxx.xxx.xxx.xxx Session error: session with token fd995923e7b912a3d91efb2fb3e1a3ba0d0005ae9a7583381190792d1b12a0ab was not found
oct 19 23:54:03 domain.com plesk-ssh-terminal.x86-64[11859]: 2023/10/19 23:54:03 remote=xxx.xxx.xxx.xxx Session error: session with token 42736cc3473931c940441c62467c28407cb50b15188c89c97599a80a4798dfa5 was not found


Any help is appreciated!

Thanks!!
 

Attachments

  • Captura de pantalla 2023-10-19 a las 23.51.06.png
    Captura de pantalla 2023-10-19 a las 23.51.06.png
    131.3 KB · Views: 4
I cannot verify it here on CentOS 7, neither is the issue known from other users. It'll need to be investigated on your server why this happens. Could you please open a support ticket?

To sign-in to support please go to https://support.plesk.com

If you experience login issues, please see this KB article:
https://support.plesk.com/hc/en-us/...rt-plesk-com-and-password-reset-does-not-work

If you bought your license from a reseller, your reseller should provide support for you. If the reseller does not provide support, here is an alternative:
https://support.plesk.com/hc/en-us/articles/12388090147095-How-to-get-support-directly-from-Plesk-
 
I cannot verify it here on CentOS 7, neither is the issue known from other users. It'll need to be investigated on your server why this happens. Could you please open a support ticket?

To sign-in to support please go to https://support.plesk.com

If you experience login issues, please see this KB article:
https://support.plesk.com/hc/en-us/...rt-plesk-com-and-password-reset-does-not-work

If you bought your license from a reseller, your reseller should provide support for you. If the reseller does not provide support, here is an alternative:
https://support.plesk.com/hc/en-us/articles/12388090147095-How-to-get-support-directly-from-Plesk-
Hi Peter,

First of all, thank you so much for your fast response. I'm a fairly new Plesk user, we are using it in our company since june this year and so far we are very very happy with it. I have already read a lot of messages for issues and doubts we had implementing Plesk these months and your messages are always very helpful.

I'm so ashamed with this. The problem, it seems, was with the browser. As soon as I restart the computer, the SSH window worked as always. It is very a strange "solution" and I did not thought of that when I was trying everything before writing here. So, the issue is resolved and I retreat in shame for not having tried everything before writing :D. I will continue to listen and read your messages which, as I said, are very, very useful.
 
Back
Top