DDoS Updates

[Rightintwo]

Hey just wanted to say, thanks for all the hard work, i see so many negative nancies in here. It's not like it's the teams fault they are getting attacked. If your weekend is ruined because you cannot play i suggest stopping for a while anyway.

Thanks to the team for trying to get this running, if you do not stay annonymous we won;t be able to play ever.
Hope to see you guys succeed soon!

[Skeleton]

Thanks to the team for their dedication to addressing the issue. I understand there are certain issues out of your hands due to 3rd party providers. As someone who works in infra I know how frustrating it can be to churn through NOC's with incredibly siloed teams and lack of escalation procedure that makes escalation on these types of issues a massive headache.

And for the tourtists crying and threatening to delete their accounts, I know you are incapable of doing so. Prove me wrong.

Take the Log Breaker guild, for instance; it completely fell apart due to DDoS issues. Some members moved to the "Forever" beta, others went to different private projects, while a few—myself included—have stayed here for now. The reason is painfully simple: the DDoS attacks made it nearly impossible to complete a raid properly over the course of a month. We faced constant disconnects and login failures; there was even an incident where the raid leader was banned mid-raid—allegedly for RMT—though, in fairness, the ban was lifted a few hours later. We had to constantly reschedule raids; there were times we rescheduled our Molten Core run three times in a single week. We’d log in and kill a boss, only for some members to get kicked and unable to reconnect, forcing us to postpone the raid by a few hours or until the next day. Then we’d try again, kill one or two bosses, and—bam—more disconnects, leading to another postponement.

Just this past weekend, several members of the guild I joined after Log Breaker disbanded also left the project. They moved to a server that has a low player count but runs stably. People just want to play the game—and here, they simply can't.

this has got to be the most obvious ai generated reply i've seen on this forum to date.

[Theflokithar]

Are you online now? I can not connect.


My public IP is 85.***.221.27. The website says:

"Your current connection is not on the whitelist."

When I try to connect, the client stays on "Connecting...".

From Linux, I also tested the realm connection directly:

play.octowow.st → 92.114.107.111

92.114.107.111:3724 times out, while the TCP connection never receives a SYN-ACK.

Could you please check whether my IP is being blocked by the server firewall/DDoS protection or needs to be whitelisted?

Thank you.

[Paulelstak]

Yes they are online now.
Majority of my guild chilling online rn
When you finally get through, 2000 to 3000 people online
Why was connecting such a problem in the first place?

And then today it's back to 2 hours of disconnecting and authenticating. What makes it extra frustrating is that apparently only a subset of people are experiencing this while others chill and look at you like you're crazy

[Bronzefury1010]

Everyone treating this post like their personal time to share whatever individual performance issue they're having as if these devs aren't dealing with DDOS attacks and server migration while trying to protect their identities at the same time.

YOU ARE PLAYING A FREE VERSION OF AN OTHERWISE PAID SUBSCRIPTION PRODUCT YOU UNGRATEFUL BASTARDS!

I've had my fair share of connection issues as well, but for about 10 days now I can log on everyday, my guild has 50-100 people on at all times, the same people everyday. Dungeon groups actively form all the time, people are raiding. The server is alive but you wouldn't know it looking at these complainers that want to bring their personal grievances to the devs like it's a therapy session.

If you're so upset about the issues and don't have the patience to wait for the devs to solve them, you don't have to tell the rest of us you're on your way out. You can just leave, no one will notice.

To the team: Thank you so much for the upfront communication, it helps a lot with understanding what you're current issues and focuses are and why certain things are taking a longer time to solve than everyone would like.

[Tinmann]

Are you online now? I can not connect.


My public IP is 85.***.221.27. The website says:

"Your current connection is not on the whitelist."

When I try to connect, the client stays on "Connecting...".

From Linux, I also tested the realm connection directly:

play.octowow.st → 92.114.107.111

92.114.107.111:3724 times out, while the TCP connection never receives a SYN-ACK.

Could you please check whether my IP is being blocked by the server firewall/DDoS protection or needs to be whitelisted?

Thank you.

Same issue here on Linux over the weekend... SYN sent, no SYN-ACK ever comes back, it just times out. Not my network, tested 3 different source IPs so ruled out ISP, VPN, and local stuff. I made a few changes and had immediate success. The login is slow though, like it is fighting through the handshake, but it slowly gets through and was in.

sudo iptables -t mangle -A OUTPUT -p tcp -d 92.114.107.48 --dport 3724 -j TTL --ttl-set 128
sudo iptables -t mangle -A OUTPUT -p tcp -d 92.114.107.59 --dport 3724 -j TTL --ttl-set 128
sudo sysctl -w net.ipv4.tcp_timestamps=0
sudo sysctl -w net.ipv4.tcp_window_scaling=0

Swap the IPs for whatever yours resolves to if different, I've seen at least 3 in the rotation (.48, .59, .111). Window scaling being off will cap your max throughput on big downloads but doesn't matter for gameplay.... Can revert anytime by flushing the mangle rule and flipping those two sysctls back to 1.

[Moy]

OMG! Tinmann, you are my personal hero!
After your tips, I'm logging in in 3 seconds.
Thanks again

[Theflokithar]

Thank you Tinmann it works now. I also tested with timestamps 1 to not mess up my connections. It also works. Thanks buddy.

[Tinmann]

Thank you Tinmann it works now. I also tested with timestamps 1 to not mess up my connections. It also works. Thanks buddy.

This is good to know. I just used the information from https://packetstorm.news/files/id/43852 to do this. I figured it had to be a fingerprint of sorts since my wife's Windows Laptop going through the exact same network, same IP, connected just fine and I couldn't. So I will change my timestamp back to 1. Thank you back.

[Computer]

Are you online now? I can not connect.


My public IP is 85.***.221.27. The website says:

"Your current connection is not on the whitelist."

When I try to connect, the client stays on "Connecting...".

From Linux, I also tested the realm connection directly:

play.octowow.st → 92.114.107.111

92.114.107.111:3724 times out, while the TCP connection never receives a SYN-ACK.

Could you please check whether my IP is being blocked by the server firewall/DDoS protection or needs to be whitelisted?

Thank you.

Same issue here on Linux over the weekend... SYN sent, no SYN-ACK ever comes back, it just times out. Not my network, tested 3 different source IPs so ruled out ISP, VPN, and local stuff. I made a few changes and had immediate success. The login is slow though, like it is fighting through the handshake, but it slowly gets through and was in.

sudo iptables -t mangle -A OUTPUT -p tcp -d 92.114.107.48 --dport 3724 -j TTL --ttl-set 128
sudo iptables -t mangle -A OUTPUT -p tcp -d 92.114.107.59 --dport 3724 -j TTL --ttl-set 128
sudo sysctl -w net.ipv4.tcp_timestamps=0
sudo sysctl -w net.ipv4.tcp_window_scaling=0

Swap the IPs for whatever yours resolves to if different, I've seen at least 3 in the rotation (.48, .59, .111). Window scaling being off will cap your max throughput on big downloads but doesn't matter for gameplay.... Can revert anytime by flushing the mangle rule and flipping those two sysctls back to 1.

Actual god , this worked for me thank you