VNC over SSH Error: “Could not create SSH tunnel”

Follow

Mike Smith

August 06, 2022 17:37

Hi,

I’m trying to use the VNC over SSH functionality of Jump Desktop Beta (Version 9.7.0, Build 90705), going from IPadOS 16 to an Ubuntu 22.02 LTS Tightvnc instance.  

I generated the public/private PEM keys using the instructions in this post:

https://support.jumpdesktop.com/hc/en-us/articles/216426203-iOS-How-do-I-use-SSH-public-key-authentication-

I checked that the keys work by successfully logging in with an SSH session using the keys.

However, when I try to use the same keys to login with the VNC over SSH functionality of Jump Desktop (using the instructions at https://support.jumpdesktop.com/hc/en-us/articles/216423843-iOS-How-to-setup-a-SSH-connection), I get the error message:

“Could not create SSH tunnel.  Public Key Authentication Failed.  The SSH server didn’t accept the username and public key combination”.  

I would appreciate any help!  Thank you!  

 

 

0

• 

  Antti V September 14, 2022 07:46 (Edited September 14, 2022 07:58)

  I have exactly the same issue, Jump Desktop iOS 9.6.8 Build 90608 on iPados 15.7 to Ubuntu 22.04.1 LTS.

  The key has been generated as described above and imported to Jump via file access (private key dropped to Jump's app directory from Files and then selected for use).

  /var/log/auth.log:

  Sep 14 10:51:16 (redacted) sshd[3227]: error: PAM: Authentication failure for illegal user  from 192.168.1.45
  Sep 14 10:51:16 (redacted) sshd[3227]: Failed keyboard-interactive/pam for invalid user  from 192.168.1.45 port 50640 ssh2

  The username is correct and can otherwise login over ssh.

  0

  Comment actions Permalink
• 

  Kiddy Von January 25, 2023 12:39

  I have exactly the same issue, too. When I used password to build VNC over SSH tunnel, it works. But failed using key files.

  My jump version is 9.7.8 and IPadOS version is16.1. I checked that the keys work by successfully logging in with an SSH session using the keys.

   

  0

  Comment actions Permalink
• 

  jeevestobs . February 08, 2023 16:56

  You need to add this line to /etc/ssh/sshd_config and restart SSH service to solve this:

  PubkeyAcceptedAlgorithms=+ssh-rsa

  0

  Comment actions Permalink
• 

  manish mukherjee March 17, 2024 05:43

  thanks @jeevestobs, that worked

  0

  Comment actions Permalink

Please sign in to leave a comment.