# New SFTP always requires password for ed25519 key, even when none is set **URL:** \ **Category:** Help & Support\ **Tags:** bug-report\ **Created:** [October 1, 2026, 4:22pm UTC](https://resource.dopus.com/t/new-sftp-always-requires-password-for-ed25519-key-even-when-none-is-set/60619 "2026-10-01T16:22:42Z")\ **Posts on this page:** 6\ **Page:** 1
**Author:** ![amuser7683](https://resource.dopus.com/letter_avatar_proxy/v4/letter/a/f07891/32.png) [@amuser7683](https://resource.dopus.com/u/amuser7683)\ **Post date:** [October 1, 2026, 4:22pm UTC](https://resource.dopus.com/t/new-sftp-always-requires-password-for-ed25519-key-even-when-none-is-set/60619/1 "2026-10-01T16:22:43Z")
Hello. I am trying to use the new SFTP but I keep running into an issue. When trying to connect to a server it prompts me for a password for a keyfile which is not password protected. There is no option to enter nothing, the "Ok" button is disabled. The only option is to cancel. There is nothing detailed printed in the logs, just the generic connection line ```auto Connecting to host ***.***. ***.*** , port 22, user ****** , private key Cancelled ``` I am on the latest beta. ---
**Author:** ![Leo](https://resource.dopus.com/user_avatar/resource.dopus.com/leo/32/69732_2.png) [@Leo](https://resource.dopus.com/u/Leo)\ **Post date:** [October 2, 2026, 11:44am UTC](https://resource.dopus.com/t/new-sftp-always-requires-password-for-ed25519-key-even-when-none-is-set/60619/2 "2026-10-02T11:44:08Z")
I've not been able to reproduce this so far, using a PPK V2 file generated via PuTTYGen. Do you know which kind of key it is? If you open it in a text editor, the first few lines usually identify the key type. ---
**Author:** ![diegocr](https://resource.dopus.com/user_avatar/resource.dopus.com/diegocr/32/26234_2.png) [@diegocr](https://resource.dopus.com/u/diegocr)\ **Post date:** [October 2, 2026, 12:12pm UTC](https://resource.dopus.com/t/new-sftp-always-requires-password-for-ed25519-key-even-when-none-is-set/60619/3 "2026-10-02T12:12:35Z")
for me, while trying things out, i only got a pwd prompt if i use a public key instead of private key. With the last beta, using the new sftp, i get error -41 and this on the logs: ```auto 2026-10-02 13:54 Legacy SSH_Init, but ftp_legacy_sftp is False 2026-10-02 13:54 SSH Connection Failed! 2026-10-02 13:54 FD_CONNECT - WSAENOTSOCK: Socket operation on non-socket 2026-10-02 13:54 **WSA returns ERROR** ``` my ppk is: ```auto PuTTY-User-Key-File-2: ssh-ed25519 Encryption: none Comment: dc@ws Public-Lines: 2 HNDFKHLKDJHFLDKSJDLHKLSDJasd/JKASDKJASHDKJASHDKASDSNKASJDKKJSAHX 4mq2 Private-Lines: 1 AAAAIOUzS/AKLHJDSKJSAHLSKDHASLJKDHLAKJSHDLKASDFS Private-MAC: 7234872634879263897426384762983746298346 ``` ---
**Author:** ![Leo](https://resource.dopus.com/user_avatar/resource.dopus.com/leo/32/69732_2.png) [@Leo](https://resource.dopus.com/u/Leo)\ **Post date:** [October 2, 2026, 12:21pm UTC](https://resource.dopus.com/t/new-sftp-always-requires-password-for-ed25519-key-even-when-none-is-set/60619/4 "2026-10-02T12:21:42Z")
> [@diegocr](#): > > `2026-10-02 13:54 Legacy SSH_Init, but ftp_legacy_sftp is False` That means it's trying to use the old SFTP code for some reason, while set to use the new code. If you can work out the sequence of actions to make that happen, please start a new thread with the details. ---
**Author:** ![amuser7683](https://resource.dopus.com/letter_avatar_proxy/v4/letter/a/f07891/32.png) [@amuser7683](https://resource.dopus.com/u/amuser7683)\ **Post date:** [October 3, 2026, 3:06pm UTC](https://resource.dopus.com/t/new-sftp-always-requires-password-for-ed25519-key-even-when-none-is-set/60619/5 "2026-10-03T15:06:16Z")
I tried several key types, and they all failed. For the new SFTP I first tried with an openssh private key id\_ed25519, got the log in the first post. Then I tried one I was using previously with old SFTP is `PuTTY-User-Key-File-2: ssh-ed25519 Encryption: none`, also fails. It has no password but when typing a password still there's a slightly different message. ```auto Connecting to host *******, port 22, user******** , private key Failed to convert private key format. (Error code 1630: Data of this type is not supported.) Failed to load private key (typed password; ****** \id_ed25519_private.ppk) (Error code 30042: Failed to import private key.) Cancelled ``` I also just tried just creating a new ed25519 openssh key WITH a password, it also still somehow fails. The log message is still generic. ```auto Connecting to host ******, port 22, user******** , private key Failed to load private key (typed password; C:\Users\ ********** \test_ed25519) (Error code 30042: Failed to import private key.) Cancelled ``` At one point during attempts I even got the same log message as diegocr, but I have been unable to replicate the circumstances that have made it appear. The only way that I managed to get the new SFTP working at all is to create a brand new key `PuTTY-User-Key-File-2: ssh-rsa`. Then dopus loads the remote and opens it just fine, even without a password, and works pretty well overall. ---
**Author:** ![Leo](https://resource.dopus.com/user_avatar/resource.dopus.com/leo/32/69732_2.png) [@Leo](https://resource.dopus.com/u/Leo)\ **Post date:** [October 5, 2026, 6:57pm UTC](https://resource.dopus.com/t/new-sftp-always-requires-password-for-ed25519-key-even-when-none-is-set/60619/6 "2026-10-05T18:57:58Z")
Thanks for the extra details! I think there are two issues. One is that any error loading key files without a password will result in a password prompt, as we don't always know the reason for the error, and assume it's likely it just needs a password. I'll see if we can make that better. Sounds like ed25519 keys also aren't working, although they are supposed to. I'd put that on my list to investigate as well.