OctoWow - Forums

Foregone wrote: Fri Sep 11, 2026 10:18 am This is not a definitive solution to the problem, but I heard several "working" tricks for some people now:

1. Reset / Flush DNS
The first thing to try would be to flush your DNS. Depending on how your setup at home is, this might be a bit more complicated, especially for people who rock their own home server, but I trust they know what to do. If you're one of the few people just having your own PC on the router, try the following

Windows
- ipconfig /flushdns
- ipconfig /release
- ipconfig /renew
- netsh winsock reset

Linux
- resolvectl flush-caches
- ip route flush cache
- systemctl restart systemd-resolved (if you are using systemd)
- systemctl restart systemd-networkd (if you are using systemd)

2. Reset your router
If you have the possibility of resetting just the cache and maybe just do a quick reconnect, do that. Otherwise a complete router restart usually does the same. It causes the router to forget all the saved routes and dns cache entries. This CAN help, but doesn't have to.

3. Restart PC
After doing the first steps and not having any luck, you could also try to restart your PC. Some say it helped in this situation. Usually it's the same effect as 1., but who knows what you've got running on your PC.

4. Running a VPN
Some reports state that running a VPN, connected do Finland, Denmark or the Netherlands, helps circumventing this problem. ProtonVPN is a name I hear often, but you might try other ones.

--------------------

Just wanted to get out there that NONE of these solutions help me personally. I've completely cleared every cache of my home server, my PC, my router and restarted everything through. Not even with a VPN it works on my end. Not sure what causes this, but if someone in Germany is using Vodafone, I'd be glad for every bit of help here.

Hope you can connect to the server, folks.

Foregone wrote: Fri Sep 11, 2026 10:18 am This is not a definitive solution to the problem, but I heard several "working" tricks for some people now:

1. Reset / Flush DNS
The first thing to try would be to flush your DNS. Depending on how your setup at home is, this might be a bit more complicated, especially for people who rock their own home server, but I trust they know what to do. If you're one of the few people just having your own PC on the router, try the following

Windows
- ipconfig /flushdns
- ipconfig /release
- ipconfig /renew
- netsh winsock reset

Linux
- resolvectl flush-caches
- ip route flush cache
- systemctl restart systemd-resolved (if you are using systemd)
- systemctl restart systemd-networkd (if you are using systemd)

2. Reset your router
If you have the possibility of resetting just the cache and maybe just do a quick reconnect, do that. Otherwise a complete router restart usually does the same. It causes the router to forget all the saved routes and dns cache entries. This CAN help, but doesn't have to.

3. Restart PC
After doing the first steps and not having any luck, you could also try to restart your PC. Some say it helped in this situation. Usually it's the same effect as 1., but who knows what you've got running on your PC.

4. Running a VPN
Some reports state that running a VPN, connected do Finland, Denmark or the Netherlands, helps circumventing this problem. ProtonVPN is a name I hear often, but you might try other ones.

--------------------

Just wanted to get out there that NONE of these solutions help me personally. I've completely cleared every cache of my home server, my PC, my router and restarted everything through. Not even with a VPN it works on my end. Not sure what causes this, but if someone in Germany is using Vodafone, I'd be glad for every bit of help here.

Hope you can connect to the server, folks.

Franz wrote: Fri Sep 11, 2026 1:12 pm Following up on the DNS flush / router reset / VPN suggestions above — wanted to share some traceroute data that narrows down where the problem actually sits, since none of the client-side fixes worked for me either at first.

I ran tracert against all three realm IPs (.47 hc, .48 normal, .49 pvp — they're sequential, same subnet) from three completely independent networks:

Deutsche Telekom (direct, no VPN): hc and pvp both route through NTT -> Telia (twelve99) -> royalehosting.net successfully. normal dies right after leaving DTAG's own backbone, before ever reaching a transit provider — full 30 hops, no response.
VPN exit in Finland (different ISP, different transit — via DataIX): hc and pvp reach royalehosting.net fine again. normal dies mid-transit at the DataIX exchange, before ever reaching royalehosting.
VPN exit in Netherlands (yet another unrelated ISP): hc and pvp reach royalehosting's network within 3 hops. normal fails at that exact same hop — never gets a response.

So across three unrelated ISPs, three different countries, three different transit paths, the pattern is identical every time: .47 and .49 always get through, .48 never does — and it fails right around where each path reaches royalehosting.net's own network.

That's hard to explain as an ISP or transit-provider problem, since it reproduces on networks that don't share any infrastructure. The most likely explanation is a null-route / blackhole on that specific IP applied at or very close to royalehosting's own network — probably leftover from DDoS mitigation — rather than anything wrong with our end.

If anyone's in touch with the server operator or royalehosting's NOC/abuse contact, this "neighbor IPs work, this one doesn't, from three unrelated countries" pattern is worth flagging directly — that's really the only place it can get fixed. VPN "working" for some people was likely just catching a network path where that specific block wasn't currently propagated, not an actual fix.

Micko1987 wrote: Fri Sep 11, 2026 8:46 am The only thing that fixed it for me was trying a VPN, instantly was able to login after that.