All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.
Need help figuring out why I can't connect to a host
I'm running a sourcemod server and while checking the logs I noticed there were dozen of [Cannot connect to update.sourcemod.net] errors. Trying to figure out why, the first thing I tried was opening update.sourcemod.net from my browser and it opened without problems. So I went looking at the server iptables and nothing there as well.
Traceroute from the VPS seems confirming it cannot find a route to the host or it is being blocked however the VPS provider's tech support replied that the problem is at the website's side for a malconfigured IPv6 but I expressed my doubt about the answer because I can connect fine from home both on IPv4 and IPv6, but ticket got closed without receiving any answer, so now I'm left finding out why on my own.
What could be the problem and a possible solution?
Here the traceroute from inside VPS:
traceroute to update.sourcemod.net (104.28.24.81), 30 hops max, 60 byte packets 1 hosted.by.prometeus.net (193.234.224.1) 0.764 ms 0.779 ms 0.811 ms 2 gw-cdlan-2.prometeus.cdlan.net (217.171.46.253) 0.313 ms * * 3 * * * 4 * * * 5 * * * 6 * * * 7 * * * 8 * * * 9 * * * 10 * * * 11 * * * 12 * * * 13 * * * 14 * * * 15 * * * 16 * * * 17 * * * 18 * * * 19 * * * 20 * * * 21 * * * 22 * * * 23 * * * 24 * * * 25 * * * 26 * * * 27 * * * 28 * * * 29 * * * 30 * * *
Traceroute from home connection:
traceroute to update.sourcemod.net (104.28.24.81), 64 hops max, 52 byte packets 1 192.168.1.3 (192.168.1.3) 2.335 ms 0.822 ms 0.824 ms 2 192.168.1.1 (192.168.1.1) 2.091 ms 2.614 ms 2.470 ms 3 * * * 4 172.18.49.141 (172.18.49.141) 1962.287 ms 172.18.49.17 (172.18.49.17) 508.231 ms 172.18.49.145 (172.18.49.145) 502.495 ms 5 172.18.48.25 (172.18.48.25) 373.084 ms 172.18.48.45 (172.18.48.45) 414.128 ms 172.18.48.29 (172.18.48.29) 357.941 ms 6 172.19.244.178 (172.19.244.178) 480.133 ms 95.883 ms 50.558 ms 7 eth-trunk15.milano1.mil.seabone.net (93.186.128.217) 71.101 ms 336.586 ms hu1-0-0-0.milano50.mil.seabone.net (93.186.128.193) 392.252 ms 8 et-7-1-0.milano51.mil.seabone.net (195.22.196.215) 491.420 ms et-7-3-0.milano51.mil.seabone.net (195.22.196.191) 545.848 ms 424.277 ms 9 cloudflare.milano51.mil.seabone.net (195.22.196.97) 396.529 ms 562.921 ms 613.972 ms 10 104.28.24.81 (104.28.24.81) 419.341 ms 346.314 ms 381.040 ms
Comments
What they said doesn't make sense, why would misconfigured IPv6 break IPv4 routing?
Looks like a possible routig issue
Hello,
We can exclude website issue because you're able to traceroute from home.
Do you have by any chance another server from that same provider a vps a dedi whatever to run "traceroute to update.sourcemod.net" to try to exclude your vps as well from the equation?
Not personally sure what the issue could be, but the website appears to be unreachable from the provider's looking glass for Italy as well. I would recommend getting in touch with your provider as it appears to be an issue from their side.