Ok so I have played wow for a very long time including retail and as well as many other
private servers as well.
When I first start your client and I am using your client and launcher it logs
me into the game ok and then it says that it is trying to log me into the realm
which is the Wowpanda 5x realm and it just times out. Then it goes backt to select
your realm again. It does this and you have to do this about 3 times or so and then
it finally lets you in.
Again this is the PandaWow x5 realm.
I believe this to be an issue with your server on your end either the server is overloaded
or something is going on because it should not time out like this when it is trying to connect
to the realm.
So this is something server related here that you need to take a look at on your end.
I believe that your servers may be over loaded or I know you run multiple realms
FYI I am not your average end user either I am a trained network admin myself.
So I am by no way a dumb individual.
Do not blame my connection this is not a connection issue on my end.
my connection is just great. I can get over of 800 Mps Download and 160 Mbps upload
on my connection there is no connection issues here!
https://www.speedtest.net/my-result/d/c586c5c7-59c4-4807-b887-7ddcf0364c5a
This isn't the first time this has happened it does it on a regular basis when you
log in.
Please look into this issue please with your servers.
Screenshot can be seen at https://ibb.co/Hg57MCh
It did this today Oct 3 2024 and it has done it consistantly in the past as well
when I am logging in. I log into my account ok and then when it tries to connect
to the realm it times out.
I did a standard ICMP traceroute to your server and as well as a TCP Traceroute
to your realm from one of my debian 12 servers here. I am located in Canada.
I mean the latency is a bit high but it should not cause the realm not to be
able to log each time.
The time out in the ICMP traceroute does not bother me that is just mean that
the hop has disabled a response to ICMP type 6 requests (ping) which is pretty
common.
logon.pandawow.me IPs: 51.77.58.247, 37.187.183.235
Why are you hosting on ovh.net? they absolutely suck. Those morons don't
know how to maintain servers for the life of them. LOL
https://apps.db.ripe.net/db-web-ui/query?bflag=false&dflag=false&rflag=true&searchtext=51.77.58.247&source=RIPE
https://apps.db.ripe.net/db-web-ui/query?bflag=false&dflag=false&rflag=true&searchtext=37.187.183.235&source=RIPE
ICMP traceroute done about 10:19 AM MDT (GMT-0600)
C:\>tracert logon.pandawow.me
Tracing route to logon.pandawow.me [51.77.58.247]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms gateway.homenet.darkshado.local [192.168.100.1]
2 8 ms 8 ms 8 ms 68.151.192.1
3 9 ms 8 ms 8 ms rc2ar-be125-1.ed.shawcable.net [64.59.184.185]
4 8 ms 9 ms 9 ms 24.244.59.153
5 9 ms 8 ms 9 ms rc2ar-be212.ed.shawcable.net [24.244.58.117]
6 10 ms 8 ms 10 ms rc2we-be7.ed.shawcable.net [66.163.70.129]
7 * * * Request timed out.
8 28 ms 28 ms 33 ms rc2wt-be100.wa.shawcable.net [66.163.75.233]
9 28 ms 28 ms 29 ms rc1wt-be18-1.wa.shawcable.net [66.163.64.81]
10 29 ms 30 ms 29 ms six.sea.wa.us.ovh.net [206.81.80.214]
11 * * * Request timed out.
12 * * * Request timed out.
13 * * * Request timed out.
14 78 ms 79 ms 78 ms be105.chi-ch2-sbb2-8k.il.us [142.44.208.160]
15 78 ms 77 ms 82 ms be103.bhs-g2-nc5.qc.ca [192.99.146.140]
16 * 87 ms * nyc-ny1-sbb2-8k.nj.us [192.99.146.139]
17 152 ms 152 ms 152 ms be104.lon-drch-sbb1-nc5.uk.eu [192.99.146.132]
18 157 ms 158 ms 158 ms be101.rbx-g4-nc5.fr.eu [54.36.50.231]
19 165 ms 165 ms 164 ms fra-fr5-sbb2-nc5.de.eu [54.36.50.232]
20 185 ms 185 ms 184 ms be104.waw-atm-sbb1-nc5.pl.eu [54.36.50.117]
21 185 ms 186 ms 185 ms be101.waw1-oza1-g2-nc5.pl.eu [213.186.32.203]
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 187 ms 185 ms 185 ms vps-f33f45d3.vps.ovh.net [51.77.58.247]
Trace complete.
I would like to see the latency a bit lower but I mean it should still be able
to log into the realm with no problems with this latency. Again
this is why you don't host with ovh.net but I mean that still doesn't explain
why the realm is timing out when it tries to connect is this a shared server
or a dedicated server? If it is shared why are you using a shared server
for a server like this maybe you would need to move it to a dedicated
server either that or if it is a dedicated server I know you run multiple realms
so how many realms are there running on this server?
Logging in works perfectly it is the next step of it trying to connect to
the realm that is where the issue occurs.
TCP/IP Traceroute done 10:15 AM MDT (GMT-600)
root@server1:~# tcptraceroute logon.pandawow.me 80
Selected device eth0, address 192.168.100.3, port 45365 for outgoing packets
Tracing the path to logon.pandawow.me (51.77.58.247) on TCP port 80 (http), 30 hops max
1 192.168.100.1 0.212 ms 0.147 ms 0.152 ms
2 68.151.192.1 9.406 ms 7.814 ms 9.372 ms
3 rc2ar-be125-1.ed.shawcable.net (64.59.184.185) 9.310 ms 9.347 ms 9.750 ms
4 24.244.59.153 9.012 ms 8.568 ms 9.174 ms
5 rc2ar-be212.ed.shawcable.net (24.244.58.117) 9.845 ms 9.581 ms 9.836 ms
6 rc2we-be7.ed.shawcable.net (66.163.70.129) 9.681 ms 9.769 ms 8.903 ms
7 * * rc3no-be6.cg.shawcable.net (66.163.64.69) 14.063 ms
8 rc2wt-be100.wa.shawcable.net (66.163.75.233) 29.158 ms 28.762 ms 28.701 ms
9 rc1wt-be18-1.wa.shawcable.net (66.163.64.81) 29.088 ms 29.117 ms 28.342 ms
10 six.sea.wa.us.ovh.net (206.81.80.214) 28.886 ms 31.395 ms 32.637 ms
11 * * *
12 * * *
13 * * *
14 be105.chi-ch2-sbb2-8k.il.us (142.44.208.160) 78.364 ms 77.687 ms 78.665 ms
15 be103.bhs-g2-nc5.qc.ca (192.99.146.140) 79.203 ms 80.524 ms 181.606 ms
16 * nyc-ny1-sbb2-8k.nj.us (192.99.146.139) 89.104 ms 87.631 ms
17 be104.lon-drch-sbb1-nc5.uk.eu (192.99.146.132) 151.029 ms 151.847 ms 151.553 ms
18 be101.rbx-g2-nc5.fr.eu (213.251.130.102) 156.418 ms 155.129 ms 157.066 ms
19 fra-fr5-sbb2-nc5.de.eu (54.36.50.232) 164.243 ms 164.376 ms 163.504 ms
20 be104.waw-atm-sbb1-nc5.pl.eu (54.36.50.117) 184.996 ms 184.411 ms 184.255 ms
21 be101.waw1-oza1-g2-nc5.pl.eu (213.186.32.203) 184.746 ms 184.652 ms 184.833 ms
22 * * *
23 * * *
24 * * *
25 * * *
26 * * *
27 * * *
28 * * *
29 * * *
30 * * *
There is no VPN or proxy or anything like that either here.
Can you please look into this issue please.
Jamie (she / her)
