Issue with the Proxy Feature of the Built-in VLESS Configs and Feature Suggestion for HTTP/HTTPS Port Selection

[Turbine8845]

Dear Vahid,
Thank you for the amazing code and for making it available as an open-source project. I have encountered an issue with the proxy feature of the built-in VLESS configs introduced in version 2.3. This feature, which was designed to address the inability to visit web pages behind Cloudflare, initially operated flawlessly. However, it has recently stopped functioning and now attempts to visit web pages behind Cloudflare result in a PR_END_OF_FILE_ERROR. This error also occurs when trying to access a web page behind Cloudflare using configs merged with the worker.
It seems that the URL used to retrieve proxy IPs, which I believe is https://raw.githubusercontent.com/vfarid/v2ray-worker/main/resources/proxy-list.txt, now redirects to a page containing only workers.bestip.one. A workaround for this issue would be greatly appreciated if possible.
Additionally, I would like to suggest a feature for your consideration. In my testing, I have found that edge/serverless VLESS configs generated using Cloudflare workers are sometimes more reliable and faster for internet connectivity with certain ISPs when using HTTP Cloudflare ports, as opposed to the HTTPS Cloudflare ports currently utilized in the code. Thus, I guess integrating the option to generate VLESS configs using both HTTP and HTTPS Cloudflare ports in the code could be a valuable addition for users.
Thank you for all your efforts and your incredible project.

[vfarid]

Yep, it version 2.3 the proxyIP war hard-coded to "workers.bestip.one" but there was possibility to replace proxyip using control panel. Anyway in version 2.4 I changed the algorithm in order to get proxy ips from this repo on-demand. So the problem is resolved.