Could not create4 SSH tunnel: invalid privatekey: <chars>

[emangini-onshape]

I'm trying to use TurboVNC (2.2.5) w/ SSH on OS X Catalina 10.15.7 The only deviation from the default settings is that we are enabling "Use VNC server as a gateway" in the Security settings.

We have nodes in AWS that we need to be able to VNC into from our developer laptops.

SSH works fine on its own. I'm able to connect, copy via scp etc. The keys are created with this command -> ssh-keygen -t rsa -b 2048 -m PEM -C. (I've also tried 4096 as a size) I've confirmed that the private key contains -----BEGIN RSA PRIVATE KEY-----

They key has been added to the ssh-agent.

When I click 'connect', I immediately get the error message above.

It doesn't matter what I put in the VNC server: in the 'New TurboVNC Connection' dialog, because it's never attempting to make a connection. I never see failures on the remote side of the connection, and I can actually disable my network and still see the same behavior (or just put a bogus string in the VNC Server: field)

It clearly doesn't like my key (all keys need love), but it's in the same format w/ the same size as other working systems, so I'm at a bit of a loss.

Assistance would be greatly appreciated.

[dcommander]

Attempting to reproduce. Stand by.

[dcommander]

Is there anything in ~/.ssh/config (on the client)?

[emangini-onshape]

Host bf_ed HostName User builder IdentityFile ~/.ssh/buildkey

From: DRC notifications@github.com Reply-To: TurboVNC/turbovnc reply@reply.github.com Date: Thursday, October 22, 2020 at 1:45 PM To: TurboVNC/turbovnc turbovnc@noreply.github.com Cc: "Mangini, Ed" emangini@ptc.com, Author author@noreply.github.com Subject: Re: [TurboVNC/turbovnc] Could not create4 SSH tunnel: invalid privatekey: (#245)

External email from: noreply@github.com

Is there anything in ~/.ssh/config?

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHubhttps://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FTurboVNC%2Fturbovnc%2Fissues%2F245%23issuecomment-714653995&data=04%7C01%7Cemangini%40ptc.com%7C6d246e237bbc467bbb1c08d876b24914%7Cb9921086ff774d0d828acb3381f678e2%7C0%7C0%7C637389855387300605%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=Xw7nlVPS%2Bw0nDYtQaMgOi3axVLif4JQdNLd%2Bu24NIqg%3D&reserved=0, or unsubscribehttps://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FARN6M2RA4ATXKCVPXWB4U6TSMBVSLANCNFSM4S3PD6IA&data=04%7C01%7Cemangini%40ptc.com%7C6d246e237bbc467bbb1c08d876b24914%7Cb9921086ff774d0d828acb3381f678e2%7C0%7C0%7C637389855387310599%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=iCicvupWOUe2xt824HvYWWZjKjfRvuVJQtpKVS6aRj8%3D&reserved=0.

[dcommander]

Is the config entry with ~/.ssh/buildkey supposed to be the entry for the AWS host? If so, are you using the config hostname 'bf_ed' when attempting to connect to the host with the TurboVNC Viewer?

[emangini-onshape]

Yes, but the ip address is the HostName. The “Host” is just the alias.

So when I ssh@bf_ed, I get to the host fine. Like I mentioned, it works outside of turbovnc perfectly.

From: DRC notifications@github.com Reply-To: TurboVNC/turbovnc reply@reply.github.com Date: Thursday, October 22, 2020 at 2:05 PM To: TurboVNC/turbovnc turbovnc@noreply.github.com Cc: "Mangini, Ed" emangini@ptc.com, Author author@noreply.github.com Subject: Re: [TurboVNC/turbovnc] Could not create4 SSH tunnel: invalid privatekey: (#245)

External email from: noreply@github.com

Is the config entry with ~/.ssh/buildkey supposed to be the entry for the AWS host? If so, are you using the config hostname 'bf_ed' when attempting to connect to the host with the TurboVNC Viewer?

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHubhttps://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FTurboVNC%2Fturbovnc%2Fissues%2F245%23issuecomment-714665334&data=04%7C01%7Cemangini%40ptc.com%7C887dd20267e648f0a32908d876b51d55%7Cb9921086ff774d0d828acb3381f678e2%7C0%7C0%7C637389867537958704%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=CW97zZJ5laS8ouIn%2FhTJmGCs2xzTvNDrdwoqgdK5i8g%3D&reserved=0, or unsubscribehttps://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FARN6M2RUF7UFJKISWFOOZ53SMBX7JANCNFSM4S3PD6IA&data=04%7C01%7Cemangini%40ptc.com%7C887dd20267e648f0a32908d876b51d55%7Cb9921086ff774d0d828acb3381f678e2%7C0%7C0%7C637389867537958704%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=xsnp4J%2Fx0eB9d3lNJZ1CGfTEsQNEE34gU%2BuQnBJbsds%3D&reserved=0.

[emangini-onshape]

Also, I don’t think I’m getting that far to be honest.

No matter what I put in the VNC Server: dialog.. It fails to read my key. I ran tcpdump, and it’s not even trying to connect.

From: "Mangini, Ed" emangini@ptc.com Date: Thursday, October 22, 2020 at 2:07 PM To: TurboVNC/turbovnc reply@reply.github.com, TurboVNC/turbovnc turbovnc@noreply.github.com Cc: Author author@noreply.github.com Subject: Re: [TurboVNC/turbovnc] Could not create4 SSH tunnel: invalid privatekey: (#245)

Yes, but the ip address is the HostName. The “Host” is just the alias.

So when I ssh@bf_ed, I get to the host fine. Like I mentioned, it works outside of turbovnc perfectly.

From: DRC notifications@github.com Reply-To: TurboVNC/turbovnc reply@reply.github.com Date: Thursday, October 22, 2020 at 2:05 PM To: TurboVNC/turbovnc turbovnc@noreply.github.com Cc: "Mangini, Ed" emangini@ptc.com, Author author@noreply.github.com Subject: Re: [TurboVNC/turbovnc] Could not create4 SSH tunnel: invalid privatekey: (#245)

External email from: noreply@github.com

Is the config entry with ~/.ssh/buildkey supposed to be the entry for the AWS host? If so, are you using the config hostname 'bf_ed' when attempting to connect to the host with the TurboVNC Viewer?

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHubhttps://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FTurboVNC%2Fturbovnc%2Fissues%2F245%23issuecomment-714665334&data=04%7C01%7Cemangini%40ptc.com%7C887dd20267e648f0a32908d876b51d55%7Cb9921086ff774d0d828acb3381f678e2%7C0%7C0%7C637389867537958704%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=CW97zZJ5laS8ouIn%2FhTJmGCs2xzTvNDrdwoqgdK5i8g%3D&reserved=0, or unsubscribehttps://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FARN6M2RUF7UFJKISWFOOZ53SMBX7JANCNFSM4S3PD6IA&data=04%7C01%7Cemangini%40ptc.com%7C887dd20267e648f0a32908d876b51d55%7Cb9921086ff774d0d828acb3381f678e2%7C0%7C0%7C637389867537958704%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=xsnp4J%2Fx0eB9d3lNJZ1CGfTEsQNEE34gU%2BuQnBJbsds%3D&reserved=0.

[dcommander]

The TurboVNC Viewer, like OpenSSH, uses the private key ~/.ssh/id_dsa or ~/.ssh/id_rsa by default. The TurboVNC Viewer also understands OpenSSH config files, so if you attempt to connect to {IP address}:{display number} using the TurboVNC Viewer, the viewer will attempt to use the private key in ~/.ssh/id_dsa or ~/.ssh/id_rsa. If, however, you attempt to connect to bf_ed:{display number}, then the TurboVNC Viewer will read the corresponding OpenSSH config file entry and use the correct private key. So if you're attempting to connect to {IP address}:{display number} using the TurboVNC Viewer, and ~/.ssh/id_dsa or ~/.ssh/id_rsa exists and doesn't contain a proper private key, then that would explain the issue.

If that doesn't explain the issue, then my next question is which version of Java you are using. You can get that information from the TurboVNC Viewer's "About" dialog.

Also, if you're comfortable using the Terminal, you can get all sorts of OpenSSH debugging info from the TurboVNC Viewer by launching it with:

/opt/TurboVNC/bin/vncviewer bf_ed:{display number} -tunnel -loglevel 110

You can also pass -sshkeyfile {file} to specify a private key file (equivalent of the -o option in OpenSSH.)

The only way I am able to reproduce that error dialog is if the private key file that the TurboVNC Viewer attempts to use is truly invalid-- that is, if the key file doesn't really contain a private key. However, it's possible that the error has another cause. I just need to be able to reproduce it in the manner it's occurring for you before I can determine the cause.

Note also: I contracted with PTC through Phil Kania earlier this year to document the procedure for installing VirtualGL and TurboVNC on your EC2 instances and connecting to them, and we both tested TurboVNC 2.2.5 during that engagement. So if nothing I've said so far explains the issue, then apparently the issue is outside of the scope of what we tested.

[emangini-onshape]

Bingo

There is a separate id_rsa file, which is probably part of the issue. That id_rsa file is using the newer openssh format (not PEM). However, that’s for a different purpose and it needs to remain with the newer openssh format. It won’t support PEM.

I’m able to connect if I specify the correct file via the cli, however Phil assures me he is doing the same thing as I am and he doesn’t have to do this via the CLI.

Despite being able to connect, there’s no video.

From: DRC notifications@github.com Reply-To: TurboVNC/turbovnc reply@reply.github.com Date: Thursday, October 22, 2020 at 2:53 PM To: TurboVNC/turbovnc turbovnc@noreply.github.com Cc: "Mangini, Ed" emangini@ptc.com, Author author@noreply.github.com Subject: Re: [TurboVNC/turbovnc] Could not create4 SSH tunnel: invalid privatekey: (#245)

External email from: noreply@github.com

The TurboVNC Viewer, like OpenSSH, uses the private key ~/.ssh/id_dsa or ~/.ssh/id_rsa by default. The TurboVNC Viewer also understands OpenSSH config files, so if you attempt to connect to {IP address}:{display number} using the TurboVNC Viewer, the viewer will attempt to use the private key in ~/.ssh/id_dsa or ~/.ssh/id_rsa. If, however, you attempt to connect to bf_ed:{display number}, then the TurboVNC Viewer will read the corresponding OpenSSH config file entry and use the correct private key. So if you're attempting to connect to {IP address}:{display number} using the TurboVNC Viewer, and ~/.ssh/id_dsa or ~/.ssh/id_rsa exists and doesn't contain a proper private key, then that would explain the issue.

If that doesn't explain the issue, then my next question is which version of Java you are using. You can get that information from the TurboVNC Viewer's "About" dialog.

Also, if you're comfortable using the Terminal, you can get all sorts of OpenSSH debugging info from the TurboVNC Viewer by launching it with:

/opt/TurboVNC/bin/vncviewer bf_ed:{display number} -tunnel -loglevel 110

You can also pass -sshkeyfile {file} to specify a private key file (equivalent of the -o option in OpenSSH.)

The only way I am able to reproduce that error dialog is if the private key file that the TurboVNC Viewer attempts to use is truly invalid-- that is, if the key file doesn't really contain a private key. However, it's possible that the error has another cause. I just need to be able to reproduce it in the manner it's occurring for you before I can determine the cause.

Note also: I contracted with PTC through Phil Kania earlier this year to document the procedure for installing VirtualGL and TurboVNC on your EC2 instances and connecting to them, and we both tested TurboVNC 2.2.5 during that engagement. So if nothing I've said so far explains the issue, then apparently the issue is outside of the scope of what we tested.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHubhttps://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FTurboVNC%2Fturbovnc%2Fissues%2F245%23issuecomment-714692729&data=04%7C01%7Cemangini%40ptc.com%7C34537048888a405a851808d876bbd220%7Cb9921086ff774d0d828acb3381f678e2%7C0%7C0%7C637389896344082391%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=gts9%2BFJk2v%2FG3TVyE3kQT2dhXTn68lZpaOg8nC31KV4%3D&reserved=0, or unsubscribehttps://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FARN6M2SGCQNYMY7CM3IC6HLSMB5QRANCNFSM4S3PD6IA&data=04%7C01%7Cemangini%40ptc.com%7C34537048888a405a851808d876bbd220%7Cb9921086ff774d0d828acb3381f678e2%7C0%7C0%7C637389896344092359%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=l0hY3XeIdZkmCcSbULQE5o07pU6UfNZ84po%2FVb%2BVMAM%3D&reserved=0.

[dcommander]

It shouldn't be necessary to use the command line. But again, it is necessary to enter bf_ed as the hostname in the TurboVNC Viewer, or else it won't use the private key specified in the OpenSSH config file's "IdentityFile" field.

As far as the blank screen, that's odd. Double check that /etc/turbovncserver.conf (on the server) contains

$wm = "mate-session";

It should, according to the instructions I sent Phil.

[dcommander]

Also, I will modify the viewer so that the error message from an invalid private key shows which key it's trying to read.

[emangini-onshape]

So that’s the weird part.

I’m using bf_ed:1 in the viewer, but I still get the invalid key. Via CLI – no problem, but I get the black screen.

Is there a way to provide the “via” parameter on the CLI? I think that’s why I’m getting the black screen. I need to be able to provide it as a gateway.

From: DRC notifications@github.com Reply-To: TurboVNC/turbovnc reply@reply.github.com Date: Thursday, October 22, 2020 at 3:21 PM To: TurboVNC/turbovnc turbovnc@noreply.github.com Cc: "Mangini, Ed" emangini@ptc.com, Author author@noreply.github.com Subject: Re: [TurboVNC/turbovnc] Could not create4 SSH tunnel: invalid privatekey: (#245)

External email from: noreply@github.com

It shouldn't be necessary to use the command line. But again, it is necessary to enter bf_ed as the hostname in the TurboVNC Viewer, or else it won't use the private key specified in the OpenSSH config file's "IdentityFile" field.

As far as the blank screen, that's odd. Double check that /etc/turbovncserver.conf contains

$wm = "mate-session";

It should, according to the instructions I sent Phil.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHubhttps://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FTurboVNC%2Fturbovnc%2Fissues%2F245%23issuecomment-714708474&data=04%7C01%7Cemangini%40ptc.com%7C293811fb5b9f42d977c308d876bfb225%7Cb9921086ff774d0d828acb3381f678e2%7C0%7C0%7C637389912981811973%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=Aeh8tjjRJlBZeIIpzbqDXe3rCjgmthDoMZmHsXPBa0g%3D&reserved=0, or unsubscribehttps://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FARN6M2R7TNTTSJ7PIHQ3GILSMCA3XANCNFSM4S3PD6IA&data=04%7C01%7Cemangini%40ptc.com%7C293811fb5b9f42d977c308d876bfb225%7Cb9921086ff774d0d828acb3381f678e2%7C0%7C0%7C637389912981821968%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=xWhlgTTk0bqvs5r3gfESUlq%2By%2FvsKUQXn1GRUirV170%3D&reserved=0.

[dcommander]

If you're getting a TurboVNC Viewer window with blank contents, then that means that the SSH and RFB connections were successful, so anything related to a gateway isn't the problem. But perhaps that's not what you meant by "no video."

The -via option shouldn't be needed with AWS. That would only be needed if the TurboVNC Server is behind an SSH gateway and is running on a different machine than the SSH gateway machine. Otherwise, -tunnel/ "Use VNC server as gateway" is what you need.

[emangini-onshape]

That’s a good idea.

lsof shows me that you’re hitting id_rsa regardless of what key I specify in .ssh/config. I confirmed it.

I moved my existing id_rsa to another name and moved the non rsa to id_rsa and it works in the viewer as well as the CLI.

However, I have a black screen in either case.

builder@ip-10-86-13-73:~$ grep mate .vnc/turbovncserver.conf

"mate-session" or "2d")

$wm = "mate-session" builder@ip-10-86-13-73:~$

From: DRC notifications@github.com Reply-To: TurboVNC/turbovnc reply@reply.github.com Date: Thursday, October 22, 2020 at 3:24 PM To: TurboVNC/turbovnc turbovnc@noreply.github.com Cc: "Mangini, Ed" emangini@ptc.com, Author author@noreply.github.com Subject: Re: [TurboVNC/turbovnc] Could not create4 SSH tunnel: invalid privatekey: (#245)

External email from: noreply@github.com

Also, I will modify the viewer so that the error message from an invalid private key shows which key it's trying to read.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHubhttps://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FTurboVNC%2Fturbovnc%2Fissues%2F245%23issuecomment-714709921&data=04%7C01%7Cemangini%40ptc.com%7C90c62d433bee471f316e08d876c01a85%7Cb9921086ff774d0d828acb3381f678e2%7C0%7C0%7C637389914735760954%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=irPh1JaxkPef5kNjWfD7WjR4yLFNRjdv23VQhuu6KF0%3D&reserved=0, or unsubscribehttps://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FARN6M2QPK3BW235KCU22UHTSMCBGBANCNFSM4S3PD6IA&data=04%7C01%7Cemangini%40ptc.com%7C90c62d433bee471f316e08d876c01a85%7Cb9921086ff774d0d828acb3381f678e2%7C0%7C0%7C637389914735770952%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=ujbKMFOIFEmRVMuhror4SA%2Fh2CFAKeoC5bC2mtA5I2Q%3D&reserved=0.

[emangini-onshape]

Roger that

It looks like the UI is using id_rsa no matter what is placed in the “server” field. I had a newer id_rsa (using OPENSSH format) for a red hat service I have that “really really needs it to be named id_rsa. I can move it for now.

I’m bouncing the Vnc server to see if that’s what is causing the black screen. It’s just black. Trying CTRL-ALT-DEL and the other buttons have no effect. I would expect to see some visual “effect” by selecting a refresh.

From: DRC notifications@github.com Reply-To: TurboVNC/turbovnc reply@reply.github.com Date: Thursday, October 22, 2020 at 3:34 PM To: TurboVNC/turbovnc turbovnc@noreply.github.com Cc: "Mangini, Ed" emangini@ptc.com, Author author@noreply.github.com Subject: Re: [TurboVNC/turbovnc] Could not create4 SSH tunnel: invalid privatekey: (#245)

External email from: noreply@github.com

If you're getting a TurboVNC Viewer window with blank contents, then that means that the SSH and RFB connections were successful, so anything related to a gateway isn't the problem. But perhaps that's not what you meant by "no video."

The -via option shouldn't be needed with AWS. That would only be needed if the TurboVNC Server is behind an SSH gateway and is running on a different machine than the SSH gateway machine. Otherwise, -tunnel/ "Use VNC server as gateway" is what you need.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHubhttps://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FTurboVNC%2Fturbovnc%2Fissues%2F245%23issuecomment-714715330&data=04%7C01%7Cemangini%40ptc.com%7Cd79f6863a26d4311d6e208d876c1825e%7Cb9921086ff774d0d828acb3381f678e2%7C0%7C0%7C637389920779911882%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=t4P4wO2wcpgjCzGCyzbm4F75KYd5Okg4WksNDdfSyuc%3D&reserved=0, or unsubscribehttps://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FARN6M2TCTTPYDIE4MVX7IHTSMCCL3ANCNFSM4S3PD6IA&data=04%7C01%7Cemangini%40ptc.com%7Cd79f6863a26d4311d6e208d876c1825e%7Cb9921086ff774d0d828acb3381f678e2%7C0%7C0%7C637389920779916862%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=3A2MkIP0oQhxiU1FzG1zpcFzHBclJ3UmtbbmRs8yJ40%3D&reserved=0.

[dcommander]

That’s a good idea. lsof shows me that you’re hitting id_rsa regardless of what key I specify in .ssh/config. I confirmed it. I moved my existing id_rsa to another name and moved the non rsa to id_rsa and it works in the viewer as well as the CLI.

I think I see the issue. Stand by.

However, I have a black screen in either case. builder@ip-10-86-13-73:~$ grep mate .vnc/turbovncserver.conf ## "mate-session" or "2d") $wm = "mate-session"

Oops. There should be a semicolon after that line, and I think I may have given instructions to Phil that didn't include said semicolon.

[emangini-onshape]

Rock on!

It actually works after I bounced the server, so I think we’re in good shape. Now if we can just make secure connections to AWS viable for RT synchronous traffic. 😊

From: DRC notifications@github.com Reply-To: TurboVNC/turbovnc reply@reply.github.com Date: Thursday, October 22, 2020 at 4:03 PM To: TurboVNC/turbovnc turbovnc@noreply.github.com Cc: "Mangini, Ed" emangini@ptc.com, Author author@noreply.github.com Subject: Re: [TurboVNC/turbovnc] Could not create4 SSH tunnel: invalid privatekey: (#245)

External email from: noreply@github.com

That’s a good idea. lsof shows me that you’re hitting id_rsa regardless of what key I specify in .ssh/config. I confirmed it. I moved my existing id_rsa to another name and moved the non rsa to id_rsa and it works in the viewer as well as the CLI.

I think I see the issue. Stand by.

However, I have a black screen in either case. builder@ip-10-86-13-73:~$ grep mate .vnc/turbovncserver.conf ## "mate-session" or "2d") $wm = "mate-session"

Oops. There should be a semicolon after that line, and I think I may have given instructions to Phil that didn't include said semicolon.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHubhttps://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FTurboVNC%2Fturbovnc%2Fissues%2F245%23issuecomment-714729169&data=04%7C01%7Cemangini%40ptc.com%7C720127bdf84e44ccb6dc08d876c57a82%7Cb9921086ff774d0d828acb3381f678e2%7C0%7C0%7C637389937836168418%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=ziuTB%2F5UsFE3UGMxznckI3vZIa9hHF8GeAcUKMgmuRs%3D&reserved=0, or unsubscribehttps://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FARN6M2QMNHLRR4KJO7AB4YDSMCFT7ANCNFSM4S3PD6IA&data=04%7C01%7Cemangini%40ptc.com%7C720127bdf84e44ccb6dc08d876c57a82%7Cb9921086ff774d0d828acb3381f678e2%7C0%7C0%7C637389937836178414%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=2sq2%2B8OHZrjwAwc%2FxxmTN4IWGOzaE0hLKjk3Q3y8nBQ%3D&reserved=0.

[dcommander]

The latest 2.2.x pre-release build should have a fix for this issue by the time you read this. https://turbovnc.org/DeveloperInfo/PreReleases It was a legitimate bug in the TurboVNC Viewer whereby ~/.ssh/id_dsa and ~/.ssh/id_rsa were allowed to take precedence even if IdentityFile was specified in the OpenSSH config file. That has been fixed, and the viewer also now specifies which private key file it was trying to use if an "invalid privatekey" error occurs.