SSH sucking

@cherring:

Is my IP being bombarded, if so what can I do about it?

Your network graphs in the web interface should give you the answer to that question.

I'd suggest a traceroute to determine where the packetloss is.

Are you connecting from behind a NAT router? That seems to be the most common cause of ssh dropouts - the NAT entries are commonly cleared after 10 minutes without traffic. Try setting 'ClientAliveInterval 300' in sshd_config.

I just moved my port back off 22 and I'm back onto working fine, I figured out how to run my process on the non standard port. Sorted.