Can't ssh into my gateway using ssgconfig after an upgrade.

Document ID : KB000044670
Last Modified Date : 14/02/2018
Show Technical Document Details


After upgrading my Gateway, I could not SSH to it using the ssgconfig user and the connection is being closed.

I’ve done the application update to 8.3 (or above) and after reboot I could no longer SSH/connect to the Gateway using the ssgconfig user and I’m getting:

“Connection closed” message.

Only user root can connect from the console directly.


In use a Virtual Appliance of the Gateway of any version below 8.3


This can happen if we apply the application update and not the platform update first.

Once this is done, the /home/ssgconfig/.bash_profile file is replaced with a new one which is looking for the below:

-bash: /opt/SecureSpan/Platform/bin/ No such file or directory


Revert to a backup snapshot and follow the upgrade procedure which is always platform update(s) and the last is the Application update (and DB upgrade if needed).

Please have a read at the below link if more detailed information is needed:

You can also find the updated list of the Product/Platform/Application updates under:


Additional Information:

A sample of a more verbose SSH attempt (using the –v option) to verify that you are facing the exact problem:'s password:

debug1: Authentication succeeded (password).

debug1: channel 0: new [client-session]

debug1: Requesting

debug1: Entering interactive session.

debug1: Sending environment.

debug1: Sending env LANG = en_US.UTF-8

Last login: Fri Jul  8 12:16:11 2016 from XX.X.X.XX

-bash: /opt/SecureSpan/Platform/bin/ No such file or directory

debug1: client_input_channel_req: channel 0 rtype exit-status reply 0

debug1: client_input_channel_req: channel 0 rtype reply 0

debug1: channel 0: forcing write

Unable to execute the ssg config menu

debug1: channel 0: free: client-session, nchannels 1

Connection to closed.

Transferred: sent 1928, received 2152 bytes, in 0.1 seconds

Bytes per second: sent 29738.9, received 33194.0

debug1: Exit status 0