MacOS Sierra cannot access AWS Ubuntu Desktop via RealVNC client and SSH tunneling
I need to access Ubuntu Desktop 18.x on AWS from my Mac. I have used putty and and am able to connect via ssh.
https://www.digitalocean.com/community/tutorials/how-to-install-and-configure-vnc-on-ubuntu-18-04
I have added the -i option to include the pem file in addition to the tunneling info above.
When I open RealVNC on the Mac and attempt to connect to Ubuntu on AWS, I get a message with a permission denied message.
I can get it working with Putty (setting tunnel and auth info in the Putty GUI) on Windows 10 with no issues.
Any suggestions? I have spent quite a bit of time searching and also noticed in the comments on the link above that other users had the same problem (no one posted a solution). Not sure what I am doing incorrectly on the Mac that prevents me from accessing the desktop.
macos ubuntu ssh tunnel realvnc
asked Jan 17 at 23:25
Cali CodrCali Codr
1
add a comment |
I need to access Ubuntu Desktop 18.x on AWS from my Mac. I have used putty and and am able to connect via ssh.
https://www.digitalocean.com/community/tutorials/how-to-install-and-configure-vnc-on-ubuntu-18-04
I have added the -i option to include the pem file in addition to the tunneling info above.
When I open RealVNC on the Mac and attempt to connect to Ubuntu on AWS, I get a message with a permission denied message.
I can get it working with Putty (setting tunnel and auth info in the Putty GUI) on Windows 10 with no issues.
Any suggestions? I have spent quite a bit of time searching and also noticed in the comments on the link above that other users had the same problem (no one posted a solution). Not sure what I am doing incorrectly on the Mac that prevents me from accessing the desktop.
macos ubuntu ssh tunnel realvnc
asked Jan 17 at 23:25
Cali CodrCali Codr
1
Have you read this answer? Also, it seems like this forum thread is also related. Are you runningvncserverasec2-useror asroot?
– Itai Steinherz
Jan 19 at 17:13
I finally figured out what he real issue was. I was trying to connect using the IP address (not the fullAWS hostname). I was trying to use the private IP (getting it from the instance after logging in using ifconfig). Turns out that you have to rightclick on the instance detail, select Networking, then to "Manage IP addresses". You can then see that there's a public and private IP. Only the public IP will work for use with ssh. Note that you won't be able to ping the Public IP (unless you make some config changes in AWS). I ended up not having this issue on Putty/Win since I used the HN
– Cali Codr
Jan 21 at 1:45
Yes, but his works the best. stackoverflow.com/questions/3475069/…. You then have to choose the VNC client option (under properties) to let VNCServer manage the encryption (ignore the warning about the lack of encryption). Specifically, use "ssh -i mypem.pem -L 5901:127.0.0.1:5901 username@serverName". You can export the pem from Windows putty, or install putty on ssh. Note that I never got that warning from the latest VNC client for Windows 10. – As mentioned above, server name has to the the full AWS hostname or the public IP address.
– Cali Codr
Jan 21 at 1:46
add a comment |
I need to access Ubuntu Desktop 18.x on AWS from my Mac. I have used putty and and am able to connect via ssh.
https://www.digitalocean.com/community/tutorials/how-to-install-and-configure-vnc-on-ubuntu-18-04
I have added the -i option to include the pem file in addition to the tunneling info above.
When I open RealVNC on the Mac and attempt to connect to Ubuntu on AWS, I get a message with a permission denied message.
I can get it working with Putty (setting tunnel and auth info in the Putty GUI) on Windows 10 with no issues.
Any suggestions? I have spent quite a bit of time searching and also noticed in the comments on the link above that other users had the same problem (no one posted a solution). Not sure what I am doing incorrectly on the Mac that prevents me from accessing the desktop.
macos ubuntu ssh tunnel realvnc
asked Jan 17 at 23:25
Cali CodrCali Codr
1
I need to access Ubuntu Desktop 18.x on AWS from my Mac. I have used putty and and am able to connect via ssh.
https://www.digitalocean.com/community/tutorials/how-to-install-and-configure-vnc-on-ubuntu-18-04
I have added the -i option to include the pem file in addition to the tunneling info above.
When I open RealVNC on the Mac and attempt to connect to Ubuntu on AWS, I get a message with a permission denied message.
I can get it working with Putty (setting tunnel and auth info in the Putty GUI) on Windows 10 with no issues.
Any suggestions? I have spent quite a bit of time searching and also noticed in the comments on the link above that other users had the same problem (no one posted a solution). Not sure what I am doing incorrectly on the Mac that prevents me from accessing the desktop.
macos ubuntu ssh tunnel realvnc
macos ubuntu ssh tunnel realvnc
asked Jan 17 at 23:25
Cali CodrCali Codr
1
asked Jan 17 at 23:25
Cali CodrCali Codr
1
asked Jan 17 at 23:25
Cali CodrCali Codr
1
asked Jan 17 at 23:25
Cali CodrCali Codr
1
asked Jan 17 at 23:25
Cali CodrCali Codr
1
1
Have you read this answer? Also, it seems like this forum thread is also related. Are you runningvncserverasec2-useror asroot?
– Itai Steinherz
Jan 19 at 17:13
I finally figured out what he real issue was. I was trying to connect using the IP address (not the fullAWS hostname). I was trying to use the private IP (getting it from the instance after logging in using ifconfig). Turns out that you have to rightclick on the instance detail, select Networking, then to "Manage IP addresses". You can then see that there's a public and private IP. Only the public IP will work for use with ssh. Note that you won't be able to ping the Public IP (unless you make some config changes in AWS). I ended up not having this issue on Putty/Win since I used the HN
– Cali Codr
Jan 21 at 1:45
Yes, but his works the best. stackoverflow.com/questions/3475069/…. You then have to choose the VNC client option (under properties) to let VNCServer manage the encryption (ignore the warning about the lack of encryption). Specifically, use "ssh -i mypem.pem -L 5901:127.0.0.1:5901 username@serverName". You can export the pem from Windows putty, or install putty on ssh. Note that I never got that warning from the latest VNC client for Windows 10. – As mentioned above, server name has to the the full AWS hostname or the public IP address.
– Cali Codr
Jan 21 at 1:46
add a comment |
Have you read this answer? Also, it seems like this forum thread is also related. Are you runningvncserverasec2-useror asroot?
– Itai Steinherz
Jan 19 at 17:13
I finally figured out what he real issue was. I was trying to connect using the IP address (not the fullAWS hostname). I was trying to use the private IP (getting it from the instance after logging in using ifconfig). Turns out that you have to rightclick on the instance detail, select Networking, then to "Manage IP addresses". You can then see that there's a public and private IP. Only the public IP will work for use with ssh. Note that you won't be able to ping the Public IP (unless you make some config changes in AWS). I ended up not having this issue on Putty/Win since I used the HN
– Cali Codr
Jan 21 at 1:45
Yes, but his works the best. stackoverflow.com/questions/3475069/…. You then have to choose the VNC client option (under properties) to let VNCServer manage the encryption (ignore the warning about the lack of encryption). Specifically, use "ssh -i mypem.pem -L 5901:127.0.0.1:5901 username@serverName". You can export the pem from Windows putty, or install putty on ssh. Note that I never got that warning from the latest VNC client for Windows 10. – As mentioned above, server name has to the the full AWS hostname or the public IP address.
– Cali Codr
Jan 21 at 1:46
Have you read this answer? Also, it seems like this forum thread is also related. Are you running
vncserver as ec2-user or as root?– Itai Steinherz
Jan 19 at 17:13
Have you read this answer? Also, it seems like this forum thread is also related. Are you running
vncserver as ec2-user or as root?– Itai Steinherz
Jan 19 at 17:13
I finally figured out what he real issue was. I was trying to connect using the IP address (not the fullAWS hostname). I was trying to use the private IP (getting it from the instance after logging in using ifconfig). Turns out that you have to rightclick on the instance detail, select Networking, then to "Manage IP addresses". You can then see that there's a public and private IP. Only the public IP will work for use with ssh. Note that you won't be able to ping the Public IP (unless you make some config changes in AWS). I ended up not having this issue on Putty/Win since I used the HN
– Cali Codr
Jan 21 at 1:45
I finally figured out what he real issue was. I was trying to connect using the IP address (not the fullAWS hostname). I was trying to use the private IP (getting it from the instance after logging in using ifconfig). Turns out that you have to rightclick on the instance detail, select Networking, then to "Manage IP addresses". You can then see that there's a public and private IP. Only the public IP will work for use with ssh. Note that you won't be able to ping the Public IP (unless you make some config changes in AWS). I ended up not having this issue on Putty/Win since I used the HN
– Cali Codr
Jan 21 at 1:45
Yes, but his works the best. stackoverflow.com/questions/3475069/…. You then have to choose the VNC client option (under properties) to let VNCServer manage the encryption (ignore the warning about the lack of encryption). Specifically, use "ssh -i mypem.pem -L 5901:127.0.0.1:5901 username@serverName". You can export the pem from Windows putty, or install putty on ssh. Note that I never got that warning from the latest VNC client for Windows 10. – As mentioned above, server name has to the the full AWS hostname or the public IP address.
– Cali Codr
Jan 21 at 1:46
Yes, but his works the best. stackoverflow.com/questions/3475069/…. You then have to choose the VNC client option (under properties) to let VNCServer manage the encryption (ignore the warning about the lack of encryption). Specifically, use "ssh -i mypem.pem -L 5901:127.0.0.1:5901 username@serverName". You can export the pem from Windows putty, or install putty on ssh. Note that I never got that warning from the latest VNC client for Windows 10. – As mentioned above, server name has to the the full AWS hostname or the public IP address.
– Cali Codr
Jan 21 at 1:46
add a comment |
0
active
oldest
votes
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "3"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1395573%2fmacos-sierra-cannot-access-aws-ubuntu-desktop-via-realvnc-client-and-ssh-tunneli%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
0
active
oldest
votes
0
active
oldest
votes
active
oldest
votes
active
oldest
votes
Thanks for contributing an answer to Super User!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1395573%2fmacos-sierra-cannot-access-aws-ubuntu-desktop-via-realvnc-client-and-ssh-tunneli%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Have you read this answer? Also, it seems like this forum thread is also related. Are you running
vncserverasec2-useror asroot?– Itai Steinherz
Jan 19 at 17:13
I finally figured out what he real issue was. I was trying to connect using the IP address (not the fullAWS hostname). I was trying to use the private IP (getting it from the instance after logging in using ifconfig). Turns out that you have to rightclick on the instance detail, select Networking, then to "Manage IP addresses". You can then see that there's a public and private IP. Only the public IP will work for use with ssh. Note that you won't be able to ping the Public IP (unless you make some config changes in AWS). I ended up not having this issue on Putty/Win since I used the HN
– Cali Codr
Jan 21 at 1:45
Yes, but his works the best. stackoverflow.com/questions/3475069/…. You then have to choose the VNC client option (under properties) to let VNCServer manage the encryption (ignore the warning about the lack of encryption). Specifically, use "ssh -i mypem.pem -L 5901:127.0.0.1:5901 username@serverName". You can export the pem from Windows putty, or install putty on ssh. Note that I never got that warning from the latest VNC client for Windows 10. – As mentioned above, server name has to the the full AWS hostname or the public IP address.
– Cali Codr
Jan 21 at 1:46