Certificate (I assume you mean SSL) wouldn't cause an ISP to block it, nor would it cause it to be unpingable. This looks like a networking issue. There is some route that is down near his host, or there are firewall/routing rules blocking some people.
You are viewing a single comment's thread from:
Yes, looks like a networking issue, but I still don't believe that it is coming from my hoster. What's the last reachable point in your tracert?
I don't have it front of me as I closed it, but some france colo.
Seems to be a local DNS cache issue. @pixelfan was able to solve it by resetting his router.
Whatever my hoster changed, the way it was done was not really professional in my eyes. I will take further steps...
Priority for realising a 'Local SteemWorld' has changed today.
It isn't DNS. I can't ping the site by name or IP.
Pinging by IP requires no DNS.
I don't know what else is being cached in the router. Since resetting the router solved the problem for him, there must be something with it. Did changing the local IP solve it? That would mean his previous IP was blocked... The ISP (First Colo) is the point before the final 37.17.224.60.
I tried the IP directly. I can’t ping it so there is nothing I can do to make it work. I have zero ability to contact the server in any fashion.
Rebooting router didn’t work (which make sense as it isn’t a DNS issue for me).
Not sure what you mean by changing the local IP but I cannot ping it so nothing else will work if I can’t even get a packet to and from the server.
Ok, so changing the local (router's) IP does not do the trick.
Do you get a packet from 212.224.102.133?
PING 37.17.224.60 (37.17.224.60) 56(84) bytes of data.
64 bytes from 37.17.224.60: icmp_seq=1 ttl=34 time=100 ms
64 bytes from 37.17.224.60: icmp_seq=2 ttl=34 time=100 ms
64 bytes from 37.17.224.60: icmp_seq=3 ttl=34 time=100 ms
--- 37.17.224.60 ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 2001ms
rtt min/avg/max/mdev = 100.676/100.689/100.707/0.366 ms
I can ping from one of my servers, but not my machine. I am not the only one who can't access it so I know it isn't limited to me.
I believe it is networking related (routing/firewall) and the fact his provider just did maintenance is awfully suspicious timing.
Yup, I feel handicapt... without steemworld...
Check my latest comment hereunder...