OctoWow - Forums

Posted: **Wed Oct 07, 2026 1:57 am**

I am in the SE United States using AT&T as my ISP. Currently, the IP address for play.octowow.st is "92.114.107.111 ". Earlier this morning, the IP was "92.114.107.59". If I try to ping either of these IPs, this is what I get:

Code: Select all

>>] ping 92.114.107.59
PING 92.114.107.59 (92.114.107.59) 56(84) bytes of data.
^C
--- 92.114.107.59 ping statistics ---
5 packets transmitted, 0 received, 100% packet loss, time 4096ms

Code: Select all

>>] ping 92.114.107.111
PING 92.114.107.111 (92.114.107.111) 56(84) bytes of data.
^C
--- 92.114.107.111 ping statistics ---
4 packets transmitted, 0 received, 100% packet loss, time 3093ms

While my "realmlist.wtf" file was pointed to the URL play.octowow.st and this URL resolved to a 92.114.0.0/16 IP, I could not connect to the WoW servers at all.

During a brief time in the late morning, play.octowow.st resolved to "185.246.188.177". While this was true, I was able to connect to the WoW server. Indeed, even now, when I ping this IP, I get this:

Code: Select all

>>] ping 185.246.188.177
PING 185.246.188.177 (185.246.188.177) 56(84) bytes of data.
64 bytes from 185.246.188.177: icmp_seq=1 ttl=47 time=114 ms
64 bytes from 185.246.188.177: icmp_seq=2 ttl=47 time=111 ms
64 bytes from 185.246.188.177: icmp_seq=3 ttl=47 time=113 ms
64 bytes from 185.246.188.177: icmp_seq=4 ttl=47 time=112 ms
^C
--- 185.246.188.177 ping statistics ---
5 packets transmitted, 4 received, 20% packet loss, time 4005ms
rtt min/avg/max/mdev = 111.006/112.326/113.576/1.082 ms

Not only can I ping it, it allows me to log in. Right now, I'm forced to hack my realmlist.wtf file to point to that specific IP address so I can log in and play. I can't use the launcher (it forcibly resets the realmlist.wtf back to "play.octowow.st" which locks me out).

Any help here would be very much appreciated.

Posted: **Wed Oct 07, 2026 3:09 am**

You are awsome! I'v tried everything and I'm sufferd from hours of trying but you are now solved my problem at the moment for first try. I thank you. Can you tell me or us how could you find that new IP? I belive we will be need this method in the near future. Or if it's risks the DDoS protection I understood if this information is holded back. Maybe this IP will solve our problem at longer time, so I'm just too happy and nervous about this succsess what you provided. Somehow especially you can find me in private if you mind so.
I thank you again, it helped me... now.

Posted: **Wed Oct 07, 2026 5:41 am**

Choochootrain wrote: Wed Oct 07, 2026 1:57 am Right now, I'm forced to hack my realmlist.wtf file to point to that specific IP address so I can log in and play.

Can you elaborate on this? Do you just change the >set realmlist "play octowow.st" to >set realmlist "185.246.188.177"?

Edit: For other technically incompetent folks, I just managed to log on by doing what I said above. Go into your octo wow folder, find realmlist.wtf (should be a notepad file) and edit it so that instead of saying (set realmlist "play.octowow.st") it says (set realmlist "185.246.188.177")

Posted: **Wed Oct 07, 2026 4:13 pm**

Doing some further research into this issue. The "working" IP mentioned above, 185.246.188.177, is owned by FlokiNET, the hosting provider mentioned by Kestrel in the most recent DDoS post.

Code: Select all

inetnum:        185.246.188.0 - 185.246.188.255
netname:        FlokiNET-Netherlands
country:        NL
admin-c:        KW2939-RIPE
tech-c:         KW2939-RIPE
status:         ASSIGNED PA
mnt-by:         lir-is-flokinetehf-1-MNT
created:        2022-01-12T15:07:57Z
last-modified:  2024-03-22T14:01:59Z
source:         RIPE

The "broken" IPs, e.g. 92.114.107.59 (really anything from the subnet 92.114.107.0/25), are owned by a different hosting provider:

Code: Select all

inetnum:        92.114.107.0 - 92.114.107.127
org-name:       RoyaleHosting BV
country:        NL
reg-nr:         82651329
org-type:       OTHER
address:        Galileïstraat 6
address:        7701 SK Dedemsvaart
address:        The Netherlands
abuse-c:        RBAC10-RIPE
mnt-ref:        RoyaleHosting
mnt-ref:        PREFIXBROKER-MNT
mnt-by:         PREFIXBROKER-MNT
mnt-by:         RoyaleHosting

I experimented with configuring my resolvd service to use FlokiNET's nameservers to resolve play.octowow.st (and only that FQDN), and at first, it seemed like it would work:

Code: Select all

>>] dig play.octowow.st

; <<>> DiG 9.18.50 <<>> play.octowow.st
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 52760
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 65494
;; QUESTION SECTION:
;play.octowow.st.               IN      A

;; ANSWER SECTION:
play.octowow.st.        295     IN      A       185.11.145.5

;; Query time: 1 msec
;; SERVER: 127.0.0.53#53(127.0.0.53) (UDP)
;; WHEN: Wed Oct 07 10:50:55 CDT 2026
;; MSG SIZE  rcvd: 60

Unfortunately, when I tried to use the new IP for play.octowow.st (185.11.145.5), it did the following when trying to connect to the server:

Connected
Authenticated
Hung on authentication
Disconnected me

Admittedly, this was different from the 92.114 IP (which simply hung and timed out), but what I tried doesn't seem to be a solution. I was able to confirm that the authentication/realm list port for was listening for TCP connections on 185.11.145.5, but it would seem that whatever is listening at the IP refuses to authenticate my account. Or, it is simply an abandoned clone of the login server.

Currently the only real "solution" is to set my realmlist.wtf file to have the following in it:

Code: Select all

set realmlist "185.246.188.177"

And you cannot use the launcher to run WoW; the first thing it does is clobber reamlist.wtf to point to play.octowow.st. You have to edit realmlist.wtf and launch WoW.exe directly. You can use the launcher to update when necessary, but after updating, you'll have to go back and edit the realmlist.wtf file again.

This is a terrible solution. It is, at best, a temporary band-aid. There is no guarantee that the "working" IP will be valid in a an hour, much less permanently. I hope someone will pay attention to this thread and address it.

Posted: **Wed Oct 07, 2026 6:23 pm**

Shinysheep wrote: Wed Oct 07, 2026 5:41 am
Choochootrain wrote: Wed Oct 07, 2026 1:57 am Right now, I'm forced to hack my realmlist.wtf file to point to that specific IP address so I can log in and play.
Can you elaborate on this? Do you just change the >set realmlist "play octowow.st" to >set realmlist "185.246.188.177"?

Edit: For other technically incompetent folks, I just managed to log on by doing what I said above. Go into your octo wow folder, find realmlist.wtf (should be a notepad file) and edit it so that instead of saying (set realmlist "play.octowow.st") it says (set realmlist "185.246.188.177")

Thank you, changing my realmlist again worked. To : set realmlist "185.246.188.177"

Appreciate it, thanks again.

Posted: **Wed Oct 07, 2026 8:26 pm**

Angryearwigs wrote: Wed Oct 07, 2026 6:23 pm
Shinysheep wrote: Wed Oct 07, 2026 5:41 am
Choochootrain wrote: Wed Oct 07, 2026 1:57 am Right now, I'm forced to hack my realmlist.wtf file to point to that specific IP address so I can log in and play.
Can you elaborate on this? Do you just change the >set realmlist "play octowow.st" to >set realmlist "185.246.188.177"?

Edit: For other technically incompetent folks, I just managed to log on by doing what I said above. Go into your octo wow folder, find realmlist.wtf (should be a notepad file) and edit it so that instead of saying (set realmlist "play.octowow.st") it says (set realmlist "185.246.188.177")
Thank you, changing my realmlist again worked. To : set realmlist "185.246.188.177"

Appreciate it, thanks again.

No worries. BTW, there is a much more stable (if still not an actual) fix in this thread:

https://octowow.st/forum/viewtopic.php?t=2840

Huge thanks to Tinmann for the fix.

OctoWow - Forums

IP range 92.114.107.0/25 is a problem

IP range 92.114.107.0/25 is a problem

Re: IP range 92.114/16 is a problem

Re: IP range 92.114/16 is a problem

Re: IP range 92.114/16 is a problem

Re: IP range 92.114/16 is a problem

Re: IP range 92.114/16 is a problem