Richard Taylor wrote: > > Hi > > > > I am not able to ssh in to the webserver. It looks like the ssh server > > is not running or a firewall is blocking access to port 22. > > > > Could someone take a look: > > > > rjt(wiki)[~]:520: ssh -v [email protected] > > OpenSSH_5.2p1, OpenSSL 0.9.8k 25 Mar 2009 > > debug1: Reading configuration data /Users/rjt/.ssh/config > > debug1: Applying options for * > > debug1: Reading configuration data /etc/ssh_config > > debug1: Connecting to www.europython.eu [89.16.178.71] port 22. > > debug1: connect to address 89.16.178.71 port 22: Operation timed out > > ssh: connect to host www.europython.eu port 22: Operation timed out > > > > Many thanks > > > > Richard
Hi Richard, Well I have ssh'd in using my Vodafone 3g connection and got the following: q...@duiker:~$ ssh -v [email protected] OpenSSH_5.1p1 Debian-6ubuntu2, OpenSSL 0.9.8g 19 Oct 2007 debug1: Reading configuration data /etc/ssh/ssh_config debug1: Applying options for * debug1: Connecting to www.europython.eu [89.16.178.71] port 22. debug1: Connection established. debug1: identity file /home/q/.ssh/identity type -1 debug1: identity file /home/q/.ssh/id_rsa type -1 debug1: identity file /home/q/.ssh/id_dsa type -1 debug1: Remote protocol version 2.0, remote software version OpenSSH_5.1p1 Debian-5 debug1: match: OpenSSH_5.1p1 Debian-5 pat OpenSSH* debug1: Enabling compatibility mode for protocol 2.0 debug1: Local version string SSH-2.0-OpenSSH_5.1p1 Debian-6ubuntu2 debug1: SSH2_MSG_KEXINIT sent debug1: SSH2_MSG_KEXINIT received debug1: kex: server->client aes128-cbc hmac-md5 none debug1: kex: client->server aes128-cbc hmac-md5 none debug1: SSH2_MSG_KEX_DH_GEX_REQUEST(1024<1024<8192) sent debug1: expecting SSH2_MSG_KEX_DH_GEX_GROUP debug1: SSH2_MSG_KEX_DH_GEX_INIT sent debug1: expecting SSH2_MSG_KEX_DH_GEX_REPLY debug1: Host 'www.europython.eu' is known and matches the RSA host key. debug1: Found key in /home/q/.ssh/known_hosts:20 debug1: ssh_rsa_verify: signature correct 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,password debug1: Next authentication method: publickey debug1: Trying private key: /home/q/.ssh/identity debug1: Trying private key: /home/q/.ssh/id_rsa debug1: Trying private key: /home/q/.ssh/id_dsa debug1: Next authentication method: password [email protected]'s password: .... Dare I suggest it's at your end, or somewhere along your path, or something to do with your ssh.config? Cheers, Q _______________________________________________ Europython-improve mailing list [email protected] http://mail.python.org/mailman/listinfo/europython-improve
