Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 6 years ago.
Improve this question
While working on a Microsoft Azure virtual machine I noticed it was lagging significantly, so I decided to run the sudo reboot command then ssh back in. When I tried to ssh back in with
ssh user#ipaddress
i got the error:
ssh: connect to host xxx.xx.xx.xxx port 22: Operation timed out.
When I run the ssh command using -vvv i get:
OpenSSH_6.9p1, LibreSSL 2.1.8
debug1: Reading configuration data /etc/ssh/ssh_config
debug1: /etc/ssh/ssh_config line 20: Applying options for *
debug1: /etc/ssh/ssh_config line 53: Applying options for *
debug2: ssh_connect: needpriv 0
debug1: Connecting to xxx.xx.xx.xxx [xxx.xx.xx.xxx] port 22.
debug1: connect to address xxx.xx.xx.xxx port 22: Operation timed out
ssh: connect to host xxx.xx.xx.xxx port 22: Operation timed out
If you did a shutdown, IP of machine has been changed. Check it in the control panel.
Related
Closed. This question is not about programming or software development. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 4 days ago.
Improve this question
i have dibian server running and every time i make ssh connection this error comes
OpenSSH_for_Windows_8.1p1, LibreSSL 3.0.2
debug3: Failed to open file:C:/Users/User/.ssh/config error:2
debug3: Failed to open file:C:/ProgramData/ssh/ssh_config error:2
debug2: resolve_canonicalize: hostname 192.168.3.30 is address
debug2: ssh_connect_direct
debug1: Connecting to ***** [*****] port 22.
debug3: finish_connect - ERROR: async io completed with error: 10060, io:000001C796F03E30
debug1: connect to address 192.168.3.30 port 22: Connection timed out
ssh: connect to host 192.168.3.30 port 22: Connection timed out
i checked the ssh if it is installed or not on dibian and it was running
i checked if the port is closed but it was opened
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 6 years ago.
Improve this question
I am having issues using VNC between MacOS X and Linux.
I installed tightvnc server on CentOS Linux and vncviewer on Mac OS X. I have done all the setting to my best knowledge and then started vncserver on the Linux computer. I also opened the port 5901.
When I execute the command "vncviewer :1" on the Linux machine, things work fine. I can see desktop appear in a window.
From Mac OS X I am unable to connect to the Linux vncserver. The message I get is
"The connection was refused by the computer"
I am able to SSH from Mac to Linux so there is connection between the two computers but VNC won't work.
Can someone please help me save this issue. I have searched the web but found nothing that worked thus far.
Thanks!
Here is the message from the vnc log file.
Xvnc TigerVNC 1.1.0 - built May 11 2016 13:01:55
Copyright (C) 1999-2011 TigerVNC Team and many others (see README.txt)
See http://www.tigervnc.org for information on TigerVNC.
Underlying X server release 11704000, The X.Org Foundation
Tue Jan 24 10:03:36 2017
vncext: VNC extension running!
vncext: Listening for VNC connections on all interface(s), port 5901
vncext: Listening for HTTP connections on all interface(s), port 5801
vncext: created VNC server for screen 0
GNOME_KEYRING_SOCKET=/tmp/keyring-jWrQoB/socket
SSH_AUTH_SOCK=/tmp/keyring-jWrQoB/socket.ssh
GNOME_KEYRING_PID=7644
gnome-session[7629]: WARNING: Could not launch application 'linc-cleanup-sockets.desktop': Unable to start application: Failed to execute
child process "/usr/bin/linc-cleanup-sockets" (No such file or directory)
Failed to play sound: File or data not found
(polkit-gnome-authentication-agent-1:7668): GLib-GObject-WARNING **: cannot register existing type `_PolkitError'
(polkit-gnome-authentication-agent-1:7668): GLib-CRITICAL **: g_once_init_leave: assertion `initialization_value != 0' failed
An instance of nm-applet is already running.
Dropbox isn't running!
Dropbox is already running!
Initializing nautilus-dropbox 2015.10.28
(null): Warning no default label for /home/amit/.gvfs
Failure: Module initalization failed
** (gnome-panel:7657): WARNING **: panel-applet-frame.c:1288: failed to load applet OAFIID:GnoteApplet:
(null)
You can tunnel the VNC connection through SSH by using local port forwarding.
To start the port forward:
ssh -NTf -L 5901:localhost:5901 user#linux_server
Then point your VNC viewer at localhost.
vncviewer localhost:5901
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
Closed 6 years ago.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Improve this question
I have an AWS EC2 instance of Ubuntu 14.04. It's been about 6 months since I've logged into it, and now I can't get logged in.
I get Permission denied (Public Key)
The thing is, I backed up my .pem file in 3 places, and none of them work. I'm pretty experienced with AWS, and I've never had this happen before.
The command I'm using is ssh -v -i mykey.pem ubuntu#192.168.0.1
The output I'm getting from the command is this:
OpenSSH_7.1p2, OpenSSL 1.0.1f 6 Jan 2014
debug1: Reading configuration data /usr/local/etc/ssh_config
debug1: Connecting to ec2-192-168-0-1.compute-1.amazonaws.com [192.168.0.1] port 22.
debug1: Connection established.
debug1: permanently_set_uid: 0/0
debug1: key_load_public: No such file or directory
debug1: identity file mykey.pem type -1
debug1: key_load_public: No such file or directory
debug1: identity file mykey.pem-cert type -1
debug1: Enabling compatibility mode for protocol 2.0
debug1: Local version string SSH-2.0-OpenSSH_7.1
debug1: Remote protocol version 2.0, remote software version PaloAltoNetworks_0.2
debug1: no match: PaloAltoNetworks_0.2
debug1: Authenticating to ec2-192-168-0-1.compute-1.amazonaws.com:22 as 'ubuntu'
debug1: SSH2_MSG_KEXINIT sent
debug1: SSH2_MSG_KEXINIT received
debug1: kex: server->client aes128-ctr hmac-sha1 none
debug1: kex: client->server aes128-ctr hmac-sha1 none
debug1: SSH2_MSG_KEX_DH_GEX_REQUEST(1024<7680<8192) sent
debug1: got SSH2_MSG_KEX_DH_GEX_GROUP
debug1: SSH2_MSG_KEX_DH_GEX_INIT sent
debug1: got SSH2_MSG_KEX_DH_GEX_REPLY
debug1: Server host key: ssh-rsa SHA256:Mt8dMlt7QdgQ9kiju3OATK43jnN9oV2pZ4oGZdd46PA
debug1: Host 'ec2-192-168-0-1.compute-1.amazonaws.com' is known and matches the RSA host key.
debug1: Found key in /root/.ssh/known_hosts:34
debug1: SSH2_MSG_NEWKEYS sent
debug1: expecting SSH2_MSG_NEWKEYS
debug1: SSH2_MSG_NEWKEYS received
debug1: SSH2_MSG_SERVICE_REQUEST sent
debug1: SSH2_MSG_SERVICE_ACCEPT received
debug1: Authentications that can continue: publickey
debug1: Next authentication method: publickey
debug1: Trying private key: mykey.pem
debug1: Authentications that can continue: publickey
debug1: No more authentication methods to try.
Permission denied (publickey).
I have tried rebooting the machine several times.
I've tried this from 3 different locations, one with no firewall at all, and I get the same thing (except of course the lines about firewalls).
I finally gave up on trying to SSH in, and decided to use the AWS Management Console connect (A Java SSH Client directly from my browser (Java required))
This has failed. It doesn't support Chrome, and when I try from Firefox, it just freezes up, and never does anything...with no error in the browser console (that I can find...I'm kind of noob at browser troubleshooting).
It does the same thing in Edge and IE. I have tried this on all 3 computers, on Ubuntu Desktop, and Windows 10 with no luck.
After that fail, I found somewhere that said I can save it to a snapshot, and start a new instance from that snapshot, and use a different .pem file, just in case all 3 of my copies were somehow magically corrupt. I tried that, and the clone I made wouldn't ever start correctly (1/2 status check).
Is there anything I haven't tried?
EDIT 1
I have also tried changing the permissions of the .pem file to 400 and 600, as well as deleting the known_hosts file. Neither of these proved to be a solution.
Do you have any monitoring on the instance? If the disk filled up, that might explain some of the problems, but Cloudwatch won't be able to tell you how much space is in use. This might explain why an AMI won't boot correctly. You should be able to get to the boot log from the AWS console which might have some information in it. If the problem is disk space, you can launch another instance from your AMI but specify a large disk.
Is it possible that the instance was hacked somehow? If someone took it over, they may have changed/removed the key, or even changed the port sshd is listening to.
If your instance is truly hosed, and you want to get the data off it, you should be able to take a snapshot, create a new volume from that snapshot, and mount the resulting volume on a new instance.
Run
chmod 400 mykey.pem
And then try ssh again. This could be the error for Permission denied (Public Key).
I've had problems when the permissions on my key were to open.
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 7 years ago.
Improve this question
I have two PC in my network. I want that PC1 have got ssh access to PC2.
On PC2 I have installed ssh-server. In PC2 inet addr:192.168.0.100 . Next I execute on PC1 this command: ssh root#192.168.0.100 and get error: Connection timeout. I'm use Ubuntu 15.04
Why? What I need configure for my task?
UPD:
sudo netstat -tulpen | grep ":22"
tcp 0 0 0.0.0.0:22 0.0.0.0:* LISTEN 0 75804 8281/sshd
tcp6 0 0 :::22 :::* LISTEN 0 75806 8281/sshd
udp6 0 0 :::22918 :::* 0 65985 6596/dhclient
UPD2:
root#v400:/ # ssh -vv ivan#192.168.0.100
OpenSSH_6.4, OpenSSL 1.0.1j 15 Oct 2014
debug2: ssh_connect: needpriv 0
debug1: Connecting to 192.168.0.100 [192.168.0.100] port 22.
debug1: connect to address 192.168.0.100 port 22: Connection timed out
ssh: connect to host 192.168.0.100 port 22: Connection timed out
root#v400:/ # nc 192.168.0.100 22
Failed to connect nc 192.168.0.100:22
As came out in comments, disable ufw. Uncomplicated Firewall (ufw) will by default block ssh connections as well.
Closed. This question is off-topic. It is not currently accepting answers.
Want to improve this question? Update the question so it's on-topic for Stack Overflow.
Closed 10 years ago.
Improve this question
I have problem to connect with SSH to remote host but only on my home network (provider). If I am at another network (my friend in same city - different provider) the connection works perfect. Ping to the server (at my home) works. Also this problem I have only with this server. If I try connect to other host from my home network, it works. What should I do?
nich#ubuntu:/etc$ ssh -vvv xxx#www.sci.muni.cz
OpenSSH_5.9p1 Debian-5ubuntu1, OpenSSL 1.0.1 14 Mar 2012
debug1: Reading configuration data /etc/ssh/ssh_config
debug1: /etc/ssh/ssh_config line 19: Applying options for *
debug2: ssh_connect: needpriv 0
debug1: Connecting to www.sci.muni.cz [147.251.24.3] port 22.
debug1: Connection established.
debug1: identity file /home/nich/.ssh/id_rsa type -1
debug1: identity file /home/nich/.ssh/id_rsa-cert type -1
debug1: identity file /home/nich/.ssh/id_dsa type -1
debug1: identity file /home/nich/.ssh/id_dsa-cert type -1
debug1: identity file /home/nich/.ssh/id_ecdsa type -1
debug1: identity file /home/nich/.ssh/id_ecdsa-cert type -1
ssh_exchange_identification: Connection closed by remote host
nich#ubuntu:/etc$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 12.04.2 LTS
Release: 12.04
Codename: precise
Here's how you can attempt to create a tunnel.
intermediary is a machine you trust to do the forwarding for you
remote is the machine you're trying to get to
ssh -N -L 20000:remote:22 user#intermediary
Once you do this your local machine will listen on port 20000. When you connect with ssh to this port, on your host, the connection will be forwarded over the tunnel to intermediary who will in turn forward it to remote.