Solving 1101 Error

[Ahmad-2213]

As you mentioned in latest version of the code , script is detected by cloudflare. (However I haven't encountered it yet)
Potentially if the sensitive words and functions covered , there would be a possiblity for this script to work on cloudflare again.
This is a long story short, but bpb panel had the same problem , they're still trying to solve it completely but as the first step , They renamed Functions and removed charactristics of proxy so the script would work once again.
Please take a look at this project:
https://github.com/liMilCo/BPB-ReCoder

Similar actions would make the code work.( Probably )

Also you can Check the Issue on BPB repo that claims it fixes the BAN problem:
bia-pain-bache/BPB-Worker-Panel#711

The main Idea they implemented is removing the charactristics of WS protocol ( same for XHTTP) by renaming functions .
They may also rewise the console log as it contains sensitive words.

[vrnobody]

I know how to bypass error 1101, but once I publish the method, Cloudflare will find another way. This script was destined to be banned from the day it was born. It is time to say goodbye. Thank you for your support.

[tomxiang1]

我知道如何绕过错误 1101，但一旦我发布该方法，Cloudflare 就会找到其他方法。这个脚本从诞生之日起就注定会被禁止。是时候说再见了。感谢你们的支持。

每一个用户都要随机加入一些混淆代码，因为cf会把你发布的混淆代码的哈希加入黑名单。

[Ahmad-2213]

I know how to bypass error 1101, but once I publish the method, Cloudflare will find another way. This script was destined to be banned from the day it was born. It is time to say goodbye. Thank you for your support.

As the last approach , Isn't there any ways to develop Packet-up which might be Compatible with Pages?
Because both Stream-up/Stream-one need gRPC to be enabled which is not supported by Pages.
I've noticed that the request limitation does not apply on pages , because the script I'm using for WS is fine when the limit is exceeded.
Thanks in advance.

[vrnobody]

That has already been explained in #2 (comment). Only stream-one mode can deploy to Cloudflare.