Unable to connect to Wargaming sign in page

[slashgob]

I've been unable to sign into the Wargaming website since having Virgin media. I can get around this using my mobile phone on the mobile network but not using wifi.

I can connect to https://eu.wargaming.net/en but if i click the sign-in link https://eu.wargaming.net/id/signin/ I just get a blank page.

I am able to play Wargamings World of Tanks with no issue, I just cannot log into my account!

Can anyone else access the sign-in link on Virgin Media?

[Client62]

Both links work fine for us.

For new VM accounts Child Safe may be enabled by default.   Turn this off in the Virgin Media online account.

Another option may be to set you PC / Console to use a Public DNS e.g. Google DNS 8.8.8.8 & 8.8.4.4

[slashgob]

Interesting... I'm using Pi-Hole as my DNS, I'll see if that could be causing the issue. Also all Parental COntrols and Anti-Virus are disabled. I have my own router, VM box is in bridge mode.

[Client62]

Check your DNS Is returning the same IP list from nslookup as say Google Public DNS / OpenDNS

Check tracert resolves to the destination, we have seen some instance of network routing faults that are local to customers. So what worked for us in Colchester may not work for your locality.

[slashgob]

nslookup gives me this:

Non-authoritative answer:
Name: eu.wargaming.net
Address: 92.223.7.169
Name: eu.wargaming.net
Address: 92.223.24.46

Which is the same as Cloudflare DNS.

Traceroute output is weird.. :

traceroute to eu.wargaming.net (92.223.7.169), 30 hops max, 60 byte packets
1 _gateway (10.0.0.1) 0.382 ms 1.930 ms 2.108 ms
2 10.53.36.121 (10.53.36.121) 10.260 ms 14.684 ms 14.341 ms
3 nott-core-2a-ae36-650.network.virginmedia.net (62.255.229.185) 15.050 ms 15.294 ms 15.532 ms
4 * * *
5 * * *
6 host-62-254-42.162.not-set-yet.virginmedia.net (62.254.42.162) 30.195 ms 22.987 ms 22.529 ms
7 nl-ams17b-rc1-lag-23-0.aorta.net (84.116.136.150) 23.414 ms nl-ams02a-rc2-lag-22-0.aorta.net (84.116.136.146) 28.656 ms 29.088 ms
8 * * *
9 * * *
10 * * *
11 * * *
12 * * *
13 5.188.135.193 (5.188.135.193) 33.311 ms 30.362 ms 29.848 ms
14 * * *
15 * * *
16 * * *
17 * * *
18 * * *
19 * * *
20 * * *
21 * * *
22 * * *
23 * * *
24 * * *
25 * * *
26 * * *
27 * * *
28 * * *
29 * * *
30 * * *

[Client62]

We also see the same two IPs.

The last IP on your tracert 188.135.193 is https://whatismyipaddress.com/ip/5.188.135.193

Our Tracert is shorter and has the final IP / host name resolved.

>>> tracert eu.wargaming.net

Tracing route to eu.wargaming.net [92.223.24.46]
over a maximum of 30 hops:

1 2 ms 1 ms 1 ms 192.168.0.1
2 * * * Request timed out.
3 15 ms 14 ms 13 ms nrth-core-2a-ae54-650.network.virginmedia.net [213.105.64.77]
4 * * * Request timed out.
5 * * * Request timed out.
6 20 ms 39 ms 19 ms aor.uk-lon03a-ri1.network.virginmedia.net [62.254.42.174]
7 * * * Request timed out.
8 * * * Request timed out.
9 * * * Request timed out.
10 * * * Request timed out.
11 * * * Request timed out.
12 * * * Request timed out.
13 * * * Request timed out.
14 30 ms 31 ms 31 ms 92.223.26.1
15 28 ms 28 ms 31 ms 92.223.20.1
16 30 ms 28 ms 30 ms ed-sl-c46.fe.core.pw [92.223.24.46]

Trace complete.

[Client62]

Below is the tracert to the alternative IP 92.223.7.169  ( I manually copied the IP in )
once again it completes the trace.  So both IPs appear to have a route for us.

Do both IPs fail to route for you ?

>>> tracert 92.223.7.169

Tracing route to 92.223.7.169 over a maximum of 30 hops

1 1 ms 1 ms 1 ms 192.168.0.1
2 * * * Request timed out.
3 15 ms 14 ms 12 ms nrth-core-2a-ae54-650.network.virginmedia.net [213.105.64.77]
4 * * * Request timed out.
5 * * * Request timed out.
6 22 ms 21 ms 18 ms aor.uk-lon03a-ri1.network.virginmedia.net [62.254.42.174]
7 * * * Request timed out.
8 * 24 ms 24 ms nl-ams17b-rc1-ae-14-0.aorta.net [84.116.137.21]
9 23 ms 22 ms 23 ms cz-prg02a-ra2-ae-99-45.aorta.net [84.116.136.149]
10 * * * Request timed out.
11 * * * Request timed out.
12 * * * Request timed out.
13 * * * Request timed out.
14 31 ms 29 ms 29 ms 5.188.135.193
15 28 ms 29 ms 28 ms 92.223.7.169

Trace complete.

[slashgob]

Neither seem to complete a trace. I increased hops to 50 but it doesn't look like it completes??

traceroute to 92.223.24.46 (92.223.24.46), 30 hops max, 60 byte packets
1 _gateway (10.0.0.1) 0.386 ms 1.991 ms 2.132 ms
2 10.53.36.121 (10.53.36.121) 13.032 ms 12.685 ms 13.304 ms
3 nott-core-2b-ae36-650.network.virginmedia.net (62.255.229.213) 20.509 ms 20.865 ms 21.138 ms
4 * * *
5 host-62-254-42.162.not-set-yet.virginmedia.net (62.254.42.162) 27.505 ms 27.830 ms 32.422 ms
6 nl-ams02a-rc2-lag-22-0.aorta.net (84.116.136.146) 33.389 ms nl-ams17b-rc1-lag-23-0.aorta.net (84.116.136.150) 20.755 ms 20.291 ms
7 * * *
8 * * *
9 * * *
10 * * *
11 * * *
12 92.223.26.1 (92.223.26.1) 38.745 ms 33.645 ms 34.000 ms
13 92.223.26.1 (92.223.26.1) 33.884 ms 37.006 ms 34.987 ms
14 * * *
15 * * *
16 * * *
17 * * *
18 * * *
19 * * *
20 * * *
21 * * *
22 * * *
23 * * *
24 * * *
25 * * *
26 * * *
27 * * *
28 * * *
29 * * *
30 * * *

traceroute to eu.wargaming.net (92.223.7.169), 50 hops max, 60 byte packets
1 _gateway (10.0.0.1) 1.824 ms 2.055 ms 2.191 ms
2 10.53.36.121 (10.53.36.121) 11.560 ms 11.842 ms 16.577 ms
3 nott-core-2a-ae36-650.network.virginmedia.net (62.255.229.185) 17.478 ms 17.768 ms 18.328 ms
4 * * *
5 * * *
6 host-62-254-42.162.not-set-yet.virginmedia.net (62.254.42.162) 32.584 ms 21.721 ms 51.078 ms
7 nl-ams17b-rc1-lag-23-0.aorta.net (84.116.136.150) 20.970 ms nl-ams02a-rc2-lag-22-0.aorta.net (84.116.136.146) 26.541 ms nl-ams17b-rc1-lag-23-0.aorta.net (84.116.136.150) 25.984 ms
8 * * *
9 * * *
10 * * *
11 * * *
12 * * *
13 5.188.135.193 (5.188.135.193) 35.728 ms 30.829 ms 27.994 ms
14 * * *
15 * * *
16 * * *
17 * * *
18 * * *
19 * * *
20 * * *
21 * * *
22 * * *
23 * * *
24 * * *
25 * * *
26 * * *
27 * * *
28 * * *
29 * * *
30 * * *
31 * * *
32 * * *
33 * * *
34 * * *
35 * * *
36 * * *
37 * * *
38 * * *
39 * * *
40 * * *
41 * * *
42 * * *
43 * * *
44 * * *
45 * * *
46 * * *
47 * * *
48 * * *
49 * * *
50 * * *

[slashgob]

Anyone able to explain the above traceroute?

[Matthew_ML]

Hey slashgob, thank you for reaching out and I am sorry to hear this.

Is this just happening on wargaming?

Does it happen on any other gaming website at all?

I've taken a look and your connection is looking fine, so is all the cache clear?

Are you in private mode when trying to access it?