// the find
yonggekkk/Doprax-Xray
Doprax一键五协议共存脚本：Xray内核，支持vless，vmess，trojan，shadowsocks，socks五协议同时在线，支持Cloudflare Argo隧道自动生成分享链接
A shell script that deploys Xray on Doprax's container platform and runs VLESS, VMess, Trojan, Shadowsocks and SOCKS side by side over WebSocket, behind one TLS endpoint. It can also start a Cloudflare Argo tunnel and print share links. It suits people who wanted a cheap proxy box and were willing to set a few environment variables and follow the README.
- All five protocols share one host and port, separated only by WebSocket path (/uuid-vl, /uuid-vm, and so on), so the CDN and tunnel options stay simple on the client side.
- The Argo integration generates the public hostname and the share links itself, which removes the most error-prone manual step for anyone without a domain of their own.
- The whole thing is small enough to read in one sitting: an entrypoint.sh, a config.json template, an nginx.conf and a Dockerfile. Nothing is built at deploy time, so it is clear what Xray is started with.
- It ships nine selectable static decoy sites, taken from mack-a's v2ray-agent, so the root domain looks like an ordinary website to a casual probe rather than the bare Nginx welcome page.
- The project is effectively dead. The README says Doprax containers are now paid-only and the project will not be updated, and the last push was January 2024. Anything that breaks against a newer Xray or a changed Doprax runtime will stay broken.
- The default UUID ea4909ef-7ca6-4b46-bf2e-6c07896ef338 is printed in the README as the fallback when no uuid variable is set. Every deployment that skipped that variable shares one credential, and anyone who has read the README can use it.
- The Argo hostname changes on every platform restart, and the only way to find the new one is to open a shell and run cat log. That rules the Argo path out for anything that needs a stable endpoint.
- The variable table still has a placeholder row reading 更新中…… (still being updated), and the docs are Chinese-only. Someone outside that audience has to work out the client parameter rules from a list of paths and ports with no explanation of why they matter.