As a followup of what I wrote here.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.
I've tried to find out what's the culprit here. Thought it was my ISP, but this seems to be wrong. For the tech savvy (and maybe the admins here):
We went for several different ISPs and did tracepaths to each of the servers (hc.octowow.st, pvp.octowow.st and normal.octowow.st). Both PvP and HC realm give me the same (vaild) answer, which reaches the endpoint royalehosting.net. The normal realm however completely cuts connectivity, once it goes out of my ISPs pipeline. Usually, every realm is showing me a path through twelve99.net, but the normal realm doesn't.
I believe the reason why it worked for so many people with ProtonVPN is that the path got updated from there on and was fine. For lots of other ISPs it seemingly didn't. If you want to try out if you can connect with your own PC, you could try:
Windows:
tracert normal.octowow.st
Linux:
tracepath normal.octowow.st
Don't worry about the different amount of hops - it depends on the ISP you're on. If the last replies you get are from "royalehosting.net", you're probably good to go.