On Tue, 11 Dec 2018 14:23:59 -0800, Samuel Sieb wrote:
On 12/11/18 1:54 PM, Beartooth wrote:
On Tue, 11 Dec 2018 12:53:03 -0800, Samuel Sieb wrote:
I can connect to that port fine. Do you have something like fail2ban on the server that would block your connection? Can you try connecting from another location?
I thought I had fail2ban, but rpm -q says not.
I tried just now on my little netbook, and got what looks to me to be the same:
But you're still trying from the same location, right?
Yes: it's a different machine in the next room, using my one access route.
But as others have said, it depends on where you try from whether or not it works. So it sounds like a networking issue somewhere. It could be the server, the hosting provider, or your internet provider. What happens if you try using traceroute?
Hoo, boy! I haven't so much as heard of traceroute in ten or fifteen years, and never did grep its uses. I can look it up, of course, but it might be worth your while to just tell me a command (and to use it as root if that should be desirable).