Re: [bitfolk] users Digest, Vol 54, Issue 2

Top Page
Author: Andy Smith
Date:  
To: users
Subject: Re: [bitfolk] users Digest, Vol 54, Issue 2

Reply to this message
gpg: Signature made Thu May 9 20:14:53 2013 UTC
gpg: using DSA key 2099B64CBF15490B
gpg: Good signature from "Andy Smith <andy@strugglers.net>" [unknown]
gpg: aka "Andrew James Smith <andy@strugglers.net>" [unknown]
gpg: aka "Andy Smith (UKUUG) <andy.smith@ukuug.org>" [unknown]
gpg: aka "Andy Smith (BitFolk Ltd.) <andy@bitfolk.com>" [unknown]
gpg: aka "Andy Smith (Linux User Groups UK) <andy@lug.org.uk>" [unknown]
gpg: aka "Andy Smith (Cernio Technology Cooperative) <andy.smith@cernio.com>" [unknown]
On Thu, May 09, 2013 at 07:20:45PM +0100, Steven Walker wrote:
> I think that it is clear it is not a problem with either my setup
> or Bitfolk and it is best to drop the topic. If we find any
> successful solution I will post it here just in case anyone might
> be interested.


I don't think it actually is clear that it is not a problem with your
setup I'm afraid. I would want to check the hosts.deny, also run an
sshd on a different port foregrounded with -v to see what it says
when you connect from the problem host.

When you are on the network that you have problems from, can you SSH
into the BitFolk console host? If you can then this makes a
configuration issue on your VPS slightly more likely. This may also
be the easiest way to get onto the VPS (from console) and run an
sshd as described.

Cheers,
Andy

--
http://bitfolk.com/ -- No-nonsense VPS hosting