<eebs>
cause I got it to connect by using a different host
<eebs>
but I was just curious if there was a way to get some additional info, or if timing out was as much info as was available
sarkyniin has joined #cinch
<dominikh>
not via cinch, no. you'd probably diagnose it via tools such as dig and ping and telnet and see if all hosts behave that way, etc
<dominikh>
the server is not telling us anything, not even rejecting the connection, hence a timeout
<eebs>
*nod* That's the conclusion I arrived at as well, thanks for the confirmation. I ended up pinging, got no response, and eventually used dig to find a different hostname that worked. Clearly something weird on their end
<eebs>
Thanks again though
<dominikh>
sure thing
djbkd has joined #cinch
djbkd has quit [Read error: Connection reset by peer]
_djbkd has joined #cinch
djbkd has joined #cinch
sarkyniin has quit [Ping timeout: 272 seconds]
_djbkd has quit [Ping timeout: 276 seconds]
sarkyniin has joined #cinch
djbkd has quit [Remote host closed the connection]
djbkd has joined #cinch
djbkd has quit [Remote host closed the connection]
djbkd has joined #cinch
djbkd has quit [Remote host closed the connection]
sarkyniin has quit [Remote host closed the connection]