DDoS Round 5

[Kestrel]

We are being hit harder today than we have all week. We have some additional protections in place but unfortunately it appears some players are unable to connect through those additional filters. We are working with our third party provider in an attempt to loosen these filters and fix this for those affected, in the meantime a VPN should allow you to connect normaly.

We are going to be retiring the IP that octowow.st previously pointed to and migrating to a fully proxied setup. What this means is anyone not pointing their realmlist.wtf to play.octowow.st will no longer be able to connect shortly as we complete this flip.

We currently only have approximately 50% of our players using the new play.octowow.st realmlist configuration. We hope to have more adoption before swapping but have to make a choice here and think swapping now is best.

Thank you again for all of your patience and we will post more updates in this thread.

[Berdal]

Keep at it guys! Myself, and I'm sure most others, aren't going anywhere. We'll ride out the storm with you!

This will make the server more robust long-term, and I figure as long as OctoWoW keep pumping out quality patches, we'll win the players in the long run.

[Denin]

Is too bad but yeah, not going anywhere. Will just play a bit less while this is going on and a permanent solution is found.

Personally this just makes me more loyal to Octo than the other way around. As long as a fix is eventually up and running. It's easy to forget that Turtle had issues too, them always managing to fix them was what gave them my loyalty then.

I wasn't sure about Octo to begin with but i haven't seen anything other than honesty from the devs here and i mostly like how they handle things. Bugs are fixed fast as they are reported and i have found very little to complain about.

Keep it up! Cheers@Octowow.

[Mdesure12]

Yeah! Besides turtle this has been the best experience!

Keep up the defense

[Odnoc]

Updated my realmlist, seems to have broken the launcher. Also, launcher resets it back to "octowow.st"

Seems to work after updating, but then after launcher resets it to "octowow.st" it causes the issue:
Unable to parse "https://octowow.st/launcher-updates/lat ... =1k17cbbav"

Everything works when skipping launcher and executing directly from client (obviously since the launcher is not changing the realmlist).

[Drakokan]

Updated my realmlist, seems to have broken the launcher. Also, launcher resets it back to "octowow.st"

Seems to work after updating, but then after launcher resets it to "octowow.st" it causes the issue:
Unable to parse "https://octowow.st/launcher-updates/lat ... =1k17cbbav"

Replace the launcher from the download site. it gonna go to be 1.3.8 and don't have any problem compared to try to download it directly from the Launcher.
For me doing this fix the launcher loop and weird various bug.

[Artemk]

Updated my realmlist, seems to have broken the launcher. Also, launcher resets it back to "octowow.st"

Seems to work after updating, but then after launcher resets it to "octowow.st" it causes the issue:
Unable to parse "https://octowow.st/launcher-updates/lat ... =1k17cbbav"

Replace the launcher from the download site. it gonna go to be 1.3.8 and don't have any problem compared to try to download it directly from the Launcher.
For me doing this fix the launcher loop and weird various bug.

Even after reinstalling the launcher and Realmlist, the connection to the server is still broken on the loading screen, and nothing works.

[Vencher]

this whole thing is getting old af.

[Fb]

We are being hit harder today than we have all week. We have some additional protections in place but unfortunately it appears some players are unable to connect through those additional filters. We are working with our third party provider in an attempt to loosen these filters and fix this for those affected, in the meantime a VPN should allow you to connect normaly.

We are going to be retiring the IP that octowow.st previously pointed to and migrating to a fully proxied setup. What this means is anyone not pointing their realmlist.wtf to play.octowow.st will no longer be able to connect shortly as we complete this flip.

We currently only have approximately 50% of our players using the new play.octowow.st realmlist configuration. We hope to have more adoption before swapping but have to make a choice here and think swapping now is best.

Thank you again for all of your patience and we will post more updates in this thread.

When I use the play.octowow.st realmlist, the ping is 4000+, when I use the old realmlist, the ping is about 100.

[Lavida]

launcher error :

please consider writing new C++\Qt launcher, I have been having problems with this web launcher since I start

Update check failed: Cannot parse update info from latest.yml in the latest release artifacts (https://octowow.st/launcher-updates/lat ... =1k17h7kgi): YAMLException: end of the stream or a document separator is expected (14:19) 11 | <script src="/bf.jquery.max.js"></script> 12 | <style> 13 | html, body { 14 | background: #212121; ------------------------^ 15 | color: #FAFAFA; 16 | margin-top: 10%; at generateError (C:\Users\Administrator\AppData\Local\Programs\OctoLauncher\resources\app.asar\node_modules\js-yaml\lib\loader.js:183:10) at throwError (C:\Users\Administrator\AppData\Local\Programs\OctoLauncher\resources\app.asar\node_modules\js-yaml\lib\loader.js:187:9) at readDocument (C:\Users\Administrator\AppData\Local\Programs\OctoLauncher\resources\app.asar\node_modules\js-yaml\lib\loader.js5) at loadDocuments (C:\Users\Administrator\AppData\Local\Programs\OctoLauncher\resources\app.asar\node_modules\js-yaml\lib\loader.js5) at Object.load (C:\Users\Administrator\AppData\Local\Programs\OctoLauncher\resources\app.asar\node_modules\js-yaml\lib\loader.js19) at Object.parseUpdateInfo (C:\Users\Administrator\AppData\Local\Programs\OctoLauncher\resources\app.asar\node_modules\electron-updater\out\providers\Provider.js:82:28) at GenericProvider.getLatestVersion (C:\Users\Administrator\AppData\Local\Programs\OctoLauncher\resources\app.asar\node_modules\electron-updater\out\providers\GenericProvider.js:23:35) at process.processTicksAndRejections (node:internal/process/task_queues:95:5) at async NsisUpdater.getUpdateInfoAndProvider (C:\Users\Administrator\AppData\Local\Programs\OctoLauncher\resources\app.asar\node_modules\electron-updater\out\AppUpdater.js:319:19) at async NsisUpdater.doCheckForUpdates (C:\Users\Administrator\AppData\Local\Programs\OctoLauncher\resources\app.asar\node_modules\electron-updater\out\AppUpdater.js:333:24), rawData: <!DOCTYPE HTML> <html lang="en-US"> <head> <meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /> <title>Just a moment please...</title> <meta name="description" content=""> <meta name="robots" content="noindex, nofollow" /> <meta name="viewport" content="width=device-width, initial-scale=1"> <link href='https://fonts.googleapis.com/css?family=Roboto:100,300' rel='stylesheet' type='text/css'> <link rel="stylesheet" href="https://maxcdn.bootstrapcdn.com/bootstr ... ap.min.css"> <script src="/bf.jquery.max.js"></script> <style> html, body { background: #212121; color: #FAFAFA; margin-top: 10%; font-family: 'Roboto'; } img.brand { display: block; opacity: .95; max-height: 85px; margin: 0 auto; opacity: .80; } h1.message { text-align: center; margin-top: 45px; font-weight: 100; font-size: 20px; text-transform: uppercase; opacity: .9; color: #E0E0E0; line-height: 30px; } h1.message a:link { text-decoration: none; color: #E0E0E0; fo