I posted a LONG time ago about this.. did some digging then.. and it seemed some of the admin actually followed suit with some of the setting changes needed to reduce some of the disconnect errors..

1006 is a cloudflare socket issue.. solely on the cloudflare side. BUT.. .......... njag- Paul; has SOME admin rights to the settings right on the cloudflare server but not all..


some of the key notes from my former posts about the 1006 dc's



A WebSocket error 1006, often encountered with Cloudflare, typically indicates an abnormal connection closure without a proper closing handshake, suggesting a potential issue with the connection or Cloudflare's settings.


Here's a breakdown of potential causes and solutions:


Possible Causes:


Abnormal Connection Closure:
Error 1006 signifies that the WebSocket connection was closed unexpectedly, without a proper closing handshake. (dropped packet in transmission)

Cloudflare's Idle Timeout:
Cloudflare might have an idle timeout setting that closes WebSocket connections that remain dormant for a certain period (e.g., 100 seconds).

HAProxy Issues:
If you're using HAProxy, the issue might be between Cloudflare and HAProxy, or HAProxy itself might be rate-limiting connections.

Zone Lockdown or Security Features:
In the Cloudflare Workers app, if a customer uses Zone Lockdown or other security features, it could block the Google Cloud Platform IPs used by the Preview tab, leading to error 1006.

Azure App Service Idle Timeout:
If you're using Azure App Service, an idle timeout setting might be closing WebSocket connections prematurely.

Web Server Issues:
The web server might be closing the connection prematurely, or there might be issues with the web server's configuration.



Troubleshooting and Solutions:


Check Cloudflare Logs:
Examine Cloudflare logs for any specific errors or warnings related to the WebSocket connections.

Review Cloudflare Settings:
Ensure that your Cloudflare settings, especially those related to security and caching, are not inadvertently blocking or terminating WebSocket connections.

Disable Cloudflare Proxy (Temporarily):
Temporarily disable Cloudflare's proxy to see if the issue persists. This can help determine if the problem lies with Cloudflare's infrastructure.

Check HAProxy Configuration:
If you're using HAProxy, review its configuration to ensure that it's not causing any issues with WebSocket connections.

Contact Cloudflare Support:
If you've tried the above steps and the issue persists, reach out to Cloudflare support for assistance.

Mimic Human Behavior:
If you're scraping a website and encountering error 1006, try mimicking human behavior by using premium proxies or rotating IPs to avoid being identified as a bot.

Check Azure App Service Settings:
If you're using Azure App Service, review its idle timeout settings and adjust them if necessary.




not sure if any of this will help anyone. but clearing all of your browser cache also sometimes helps.. but in doing so, removes auto log in info.. :\

This post was edited by Canadian_Born on Mar 21 2025 08:13pm

Dang, well done. I personally suspect the initial answer you provided:

Abnormal Connection Closure:
Error 1006 signifies that the WebSocket connection was closed unexpectedly, without a proper closing handshake. (dropped packet in transmission)

This reflects the IPS of the User (me), connection speed and route from A(me) to Z(server) connection and during the transfer through the ports, Packets have been lost or slowed. Note: Weather is the dominant factor when transmitting from A to Z (or C) Portals.

IPS maybe fast as lightning, however, any portal it goes through at that time may not be open and you lost a packet or more while being transferred to the next portal or re-directed one... THAT IS JUST my guess on the matter.

Other factors to count.

EDIT: Most of my Cloudfire issues are from Australia (portal # 3) ... so can you imagine how many Portals of Packet transfer I need to get through from A to Z and back to A?

This post was edited by izParagonzi on Mar 25 2025 10:23pm

Might have to make that pict my signature It is crazy how it always seems to happen at the end...probably only remember those and not the 1006 that happen early in the mute process.

Here is my thought... I just tested starting a mute and then aborting after about 2 seconds. The mute was returned to me when I aborted. I know I've accidently hit abort late while muting and have lost the mute.

Why cant the same coding that allows the mute to be returned to me when I abort very early in the process should be changed to allow the item to be returned during the muting process when a 1006 disconnect occurs?

I'm not a computer guy or tech savy. I just like to apply common sense to a situation.

If a mute can be returned from hitting abort (very early in mute process) then a mute should be able to be returned from 1006.

My 2 cents

I

As long as u havent started clicking transmute you can always abort an item, even if u hold stabilize for 5min or whatever.
But the single click on transmute and u cant keep the item anymore

Thanks for clarifying!

back to back 1006s.
fg pit working as intended

and another...

has paul or anyone addressed this ever? even to say tough shit this is how it is? at least to acknowledge it?

This post was edited by FuzzySocks on Mar 26 2025 05:56pm

14:15 Disconnected from server. (1006)
14:29 Disconnected from server. (1006)
15:03 Disconnected from server. (1006)
15:10 Disconnected from server. (1006)
15:49 Disconnected from server. (1006)
15:50 Disconnected from server. (1006)
15:52 Disconnected from server. (1006)
16:31 Disconnected from server. (1006)

My day so far. Thank fuck I haven't been muting.

This post was edited by tealeaves on Mar 26 2025 06:36pm

Ouch.

14.29 (2.29 PM)
15.03 (3.03 PM) ... like 30 minutes before 1006? ... not as for the rest???
15.10 (3.10 PM) ... 7 minutes
15.49 (3.49 PM) ... 32 minutes
15.50 (3.50 PM) ... 1 minute
15.52 (3.52 PM) ... 2 minutes
16.31 (4.31 PM) ... 39 minutes.

Hmm ... from 3.49 pm to 3.50 pm could be an issue... what happened during the other times of the 1006?

EDIT: We can not (including you) copy/paste from chat logs in game (however we were told we could) ... so your post means you basically typed it all out from your chat logs ignoring what happened in between (yup I do that also)... however, I have learnt to take a prntscrn of it using Lightshot.

Oh btw.. Kevin said he would fix this issue (copy/paste) over a year ago when I pointed out that Paul had stated in an update that we could copy/paste from the Chat logs in LS... however we still can't... I am still waiting.

This post was edited by izParagonzi on Mar 27 2025 06:20am

ctrl+c to copy selected text in chat log
ctrl+p to paste

///edit example

02:37 evilwoman [*halpn34] (Guild: Storm) failed the softcore Master Quest.
04:01 Ajushi [*AlmondTofu] (Guild: Plus Ultra) failed the softcore Master Quest.
05:19 Smurfed [*pointnclick] failed the softcore Master Quest.
05:24 PO0 [*PO0] (Guild: Newb) failed the softcore Master Quest.
07:39 Dia [*xDiAx] (Guild: Storm) failed the softcore Master Quest.

This post was edited by Tye on Mar 27 2025 06:23am

Oh... I guess this applies to those using Google Chrome 7, Windows 7 which is obsolete with a 1gb RAM PC with a 3.2 Windows Rating with Dual Core etc... yup, I have a crap RAM, outdated operating system to boot, however none of your shit works with what I am using that can still RUN 3 window open... JSP, Anime site and Playing LS with only 1GB RAM. wow... wo in the post by tealeaves where there was a 20+ minute interval of NOTHING HAPPENING in between wasn't posted like YOUR copy/.paste scenario or point to prove me wrong? Did you just type it all out??? You don't have a corresponding Image to prove your post... so STFU or get a SS.

EDIT: here is an example of typing shit to prove a point.... btw... I am not even playing Ladder Slasher:

02:37 Jwhat [*WhatTTF] (Guild: Platinum) failed the Hardcore Master Quest.
02:40 Cumwhat[*Tofu] (Guild: Platinum) failed the Hardcore Master Quest.
02:42 Squidfire[*Porcullus] failed the Hardcore Master Quest.
03:05 PO0 [*PO0] (Guild: Newb) failed the softcore Master Quest.
03.44 izTwatzi [*izParagonzi] (Guild: Kirby) failed the Hardcore Master Quest.
04:15 Disconnected from server. (1006)
04.20 Gained a level ... etc
04:22 Emblem ... etc

etc
etc

Oh... your post with times make it more suspicious... how many hours and minutes you copy / pasted your text???

02:37 evilwoman [*halpn34] (Guild: Storm) failed the softcore Master Quest.
04:01 Ajushi [*AlmondTofu] (Guild: Plus Ultra) failed the softcore Master Quest.
05:19 Smurfed [*pointnclick] failed the softcore Master Quest.
05:24 PO0 [*PO0] (Guild: Newb) failed the softcore Master Quest.
07:39 Dia [*xDiAx] (Guild: Storm) failed the softcore Master Quest.


Hmm... 1.5 hours
1.10 hours
5 minutes
2 + hours

.... woah... talk about a lot of shit in your post aye.

This post was edited by izParagonzi on Mar 27 2025 06:55am