MSL/MiCollab SFTP Access Issues

[BradHand]

Hello all! I've been working through doing certificate updates ahead of the Aug 21st deadline and I keep running into an issue that I could use some insight on.

All our physical devices have been upgrading mostly without issues but our VMs that are running MSL/MiCollab sometimes have an issue allowing SFTP connections. We have to reboot the devices and then we can access SFTP to transfer the certificate files. However, we have to wait until after hours for each client to perform the reboot and it's really slowing us down. I have been looking but have been unable to find an answer to this question, is there a command to reset the SFTP service inside MSL or something similar that could allow us to regain access via SFTP without a reboot? I am able to use Putty to SSH into the devices.

Using known good UN/PW this is what we receive when attempting to SFTP using FileZilla, WinSCP has similar results/errors: FATAL ERROR: Received unexpected end-of-file from SFTP server

Thanks all!

[johnp]

Sftp amd putty use the same port, I have never had a sftp issue. If you can use putty there should be no reason a sftp connection should not work. You could try to disable and re-enable ssh access in the remote access section

[sarond]

What I will sometimes do is rather than 'push' the file to MSL using WinSCP I will log in to the server and 'pull' the file from somewhere (usually a webserver) using 'wget http://example.com/path/file.ext'. You could also use FTP.

You just need somewhere to host the files that is accessible from the server.

[dilkie]

never had a problem with winscp but it almost sounds like an MTU issue... Slow transfer speeds tend to result from that.

[NEPhoneGuy]

Only the MiVoice Business is impacted by the certificate expiration?