Skip to content
View in the app

A better way to browse. Learn more.

Unraid

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

unRAID refuses connection from new version of SFTP client, old versions works

Featured Replies

Hi everyone:

 

This is probably a common issue that might be caused by security certificates or something else but before I delete the keys in config/ssh, which solved my previous "can't SSH but can telnet" problem, I thought I better ask in here.

 

I use Transmit (for the Mac) to SFTP to my unRAID. Old version still works, but a new version of Transmit is reporting the credentials error.

 

Would deleting the SSH keys in the unRAID flash drive's config/ssh folder and rebooting unRAID solve this or should I do something else?

 

Thank you.

  • Author

Bump.

  • Community Expert

Have you attempted to solve the problem from the Mac/Transmit end of the equation.  Any developer who updates a ftp type package should be making sure that it will work properly with the any older protocol and/or ftp client.  After all, there is no reason to suppose that the user (you, in this case) will be able to do anything at all about the client on the other end of the connection.  If there is a reason it won't, then they should be providing warnings about the problem and its solution/workaround. 

  • Author

Fair point, but SFTP to another site works, and I've had difficulty using SSH to connect in the past so I thought it's a similar problem.

 

Could this be related?
 

Quote


I have an SFTP favorite that connected in Transmit 4, but it doesn’t connect in Transmit 5. What’s going on?

In order to support the same authentication experience across all our Mac and iOS apps, Transmit 5 uses a different SSH library than Transmit 4.

Unfortunately, this means we have to temporarily drop support for a few features, specifically OpenSSH formatted (ssh-keygen -o) keys.

If you were using keys of this format in Transmit 4 they will not work currently work in Transmit 5.

We hope to add support for these in the near future!

 

 

I think you need to create new private keys for transmit 5 then export the public keys to openssh format.

 

Client is Transmit 5 so private keys must be in Transmit 5 format.

Server is OpenSSH, so public keys must be in openssh format.

 

This is how I work sometimes with PuTTY and WinSCP from Windows to unRAID (and other servers)

 

unless Transmit 5 refuses to talk to an openssh server for the time being... :(

 

  • Author

@ken-ji Thanks for clarifying. From their site, it sounds like it won't work with OpenSSH for the time being.

Archived

This topic is now archived and is closed to further replies.

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.