amnezia-vpn/amnezia-client

Fork 0

mirror of https://github.com/amnezia-vpn/amnezia-client.git synced 2026-10-15 05:42:07 +00:00

[GH-ISSUE #874] SSH private key is not accepted during server setup #235

New issue

Closed

opened 2026-10-13 20:16:20 +00:00 by bsakaguchi · 5 comments

bsakaguchi commented

2026-10-13 20:16:20 +00:00

Owner

Originally created by @trackadelsilent on GitHub (Jul 1, 2024).
Original GitHub issue: https://github.com/amnezia-vpn/amnezia-client/issues/874

Describe the bug
Configure your server returns 101 error code while using SSH private key.

To Reproduce
Steps to reproduce the behavior:

Go to 'Configure your server'
Fill server IP
Fill SSH username
Fill Password or SSH private key with contents like:
-----BEGIN OPENSSH PRIVATE KEY-----
....
-----END OPENSSH PRIVATE KEY-----
See error

Expected behavior
Server setup continues to the next step.

Screenshots
Screenshot 2024-07-01 at 14 55 50

Desktop (please complete the following information):

OS: MacOS
Version Sonoma 14.4.1

Server (please complete the following information):

OS: Debian GNU/Linux 12

Originally created by @trackadelsilent on GitHub (Jul 1, 2024). Original GitHub issue: https://github.com/amnezia-vpn/amnezia-client/issues/874 **Describe the bug** Configure your server returns 101 error code while using SSH private key. **To Reproduce** Steps to reproduce the behavior: 1. Go to 'Configure your server' 2. Fill server IP 3. Fill SSH username 4. Fill Password or SSH private key with contents like: -----BEGIN OPENSSH PRIVATE KEY----- .... -----END OPENSSH PRIVATE KEY----- 5. See error **Expected behavior** Server setup continues to the next step. **Screenshots** <img width="374" alt="Screenshot 2024-07-01 at 14 55 50" src="https://github.com/amnezia-vpn/amnezia-client/assets/72935259/f4ccc9dc-c90e-448a-b63f-4c56a58bec7f"> **Desktop (please complete the following information):** - OS: MacOS - Version Sonoma 14.4.1 **Server (please complete the following information):** - OS: Debian GNU/Linux 12

bsakaguchi closed this issue

2026-10-13 20:16:20 +00:00

bsakaguchi commented

2026-10-13 20:16:21 +00:00

Author

Owner

@rustem-galeev commented on GitHub (Jul 5, 2024):

so do you have some workaround for this problem?

upd: I don't know why but for me using ecdsa key instead of rsa works fine

@rustem-galeev commented on GitHub (Jul 5, 2024): so do you have some workaround for this problem? upd: I don't know why but for me using ecdsa key instead of rsa works fine

bsakaguchi commented

2026-10-13 20:16:21 +00:00

Author

Owner

@trackadelsilent commented on GitHub (Jul 5, 2024):

Hello,

Yes, the solution was provided to us by support.

пт, 5 июл. 2024 г., 20:58 rustem-galeev @.***>:

so do you have some workaround for this problem?

—
Reply to this email directly, view it on GitHub
https://github.com/amnezia-vpn/amnezia-client/issues/874#issuecomment-2211294428,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ARMOOW47AOCI56DXLG53FK3ZK3UGHAVCNFSM6AAAAABKFRAWKOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDEMJRGI4TINBSHA
.
You are receiving this because you modified the open/close state.Message
ID: @.***>

@trackadelsilent commented on GitHub (Jul 5, 2024): Hello, Yes, the solution was provided to us by support. пт, 5 июл. 2024 г., 20:58 rustem-galeev ***@***.***>: > so do you have some workaround for this problem? > > — > Reply to this email directly, view it on GitHub > <https://github.com/amnezia-vpn/amnezia-client/issues/874#issuecomment-2211294428>, > or unsubscribe > <https://github.com/notifications/unsubscribe-auth/ARMOOW47AOCI56DXLG53FK3ZK3UGHAVCNFSM6AAAAABKFRAWKOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDEMJRGI4TINBSHA> > . > You are receiving this because you modified the open/close state.Message > ID: ***@***.***> >

bsakaguchi commented

2026-10-13 20:16:22 +00:00

Author

Owner

@wKich commented on GitHub (Aug 22, 2024):

@trackadelsilent, could you please share what exactly solution was provided?

@wKich commented on GitHub (Aug 22, 2024): @trackadelsilent, could you please share what exactly solution was provided?

bsakaguchi commented

2026-10-13 20:16:22 +00:00

Author

Owner

@trackadelsilent commented on GitHub (Aug 22, 2024):

@wKich
Hello,

The following answer helped us:

Amnezia does not support all kinds of SSH keys, try using a key that was generated by one of these commands:
ssh-keygen -t rsa -m PEM -b 2048
ssh-keygen -t rsa -m PEM -b 3072
ssh-keygen -t rsa -m PEM -b 4096
ssh-keygen -t ed25519

We had to regenerate the key.

@trackadelsilent commented on GitHub (Aug 22, 2024): @wKich Hello, The following answer helped us: > Amnezia does not support all kinds of SSH keys, try using a key that was generated by one of these commands: > ssh-keygen -t rsa -m PEM -b 2048 > ssh-keygen -t rsa -m PEM -b 3072 > ssh-keygen -t rsa -m PEM -b 4096 > ssh-keygen -t ed25519 We had to regenerate the key.

bsakaguchi commented

2026-10-13 20:16:23 +00:00

Author

Owner

@nnseva commented on GitHub (Jan 25, 2026):

Hi everybody,

It's not necessary to regenerate the OpenSSH private key, actually. The existing OpenSSH private key can be used to access Amnezia from the client if properly converted to the old-style SSH key.

Use PuTTY to convert keys. The OpenSSH ssh-keygen tool can't do it properly.

The following is a Linux (Ubuntu) way to convert the existing OpenSSH private key ~/.ssh/id_rsa:

sudo apt-get install putty-tools
puttygen ~/.ssh/id_rsa -O private-openssh -o ~/.ssh/id_rsa.ssh2

Use the contents of the existing file ~/.ssh/id_rsa.pub to fill in the root SSH access key on your virtual host.

Then use the contents of the output file ~/.ssh/id_rsa.ssh2 (although, you could name it as you wish) to put into the password field (copy&past for simplicity)

@nnseva commented on GitHub (Jan 25, 2026): Hi everybody, It's not necessary to regenerate the OpenSSH private key, actually. The existing OpenSSH private key can be used to access Amnezia from the client if properly converted to the old-style SSH key. Use PuTTY to convert keys. The OpenSSH ssh-keygen tool can't do it properly. The following is a Linux (Ubuntu) way to convert the existing OpenSSH private key `~/.ssh/id_rsa`: ```sh sudo apt-get install putty-tools puttygen ~/.ssh/id_rsa -O private-openssh -o ~/.ssh/id_rsa.ssh2 ``` Use the contents of the existing file `~/.ssh/id_rsa.pub` to fill in the root SSH access key on your virtual host. Then use the contents of the output file `~/.ssh/id_rsa.ssh2` (although, you could name it as you wish) to put into the `password` field (copy&past for simplicity)

bsakaguchi referenced this issue

2026-10-13 20:46:56 +00:00

[PR #235] [CLOSED] Feature/ios gh setup #1693