Noahclanman
Elite
They route your traffic through one or more servers before it exits through Cloudflare WARP, so the sites you visit see a Cloudflare IP instead of your ISP's, and your ISP only sees a TLS connection to my entry server.
What you need
A client that supports VLESS with XHTTP. Examples: v2rayNG or NekoBox on Android, Hiddify, v2rayN on Windows, Streisand or V2Box on iOS. Older client versions may not support XHTTP, so update first if the import fails.
Config 1: Multi-hop (3 servers + WARP)
Path:
Device > Entry (zxc.opencfg.xyz) > Relay 2 (zxcv.opencfg.xyz) > Relay 3 (xm.opencfg.xyz) > Exit (Cloudflare WARP)
Transport is XHTTP in stream-one mode over TLS, fingerprint set to Chrome.
vless://arise@zxc.opencfg.xyz:443?type=xhttp&path=%2Fassets&mode=stream-one&security=tls&alpn=h2%2Chttp%2F1.1&fp=chrome#Multi%20Hop%20XVPN%20%2B%20Warp
Config 2: Single entry + WARP (WebSocket)
Path:
Device > Entry/Relay (xm.opencfg.xyz) > Exit (Cloudflare WARP)
vless://8ff5dfff-fbdf-4503-a30e-5c8a0edbf464@xm.opencfg.xyz:443?type=ws&path=%2Fvlessws&host=xm.opencfg.xyz&security=tls&sni=xm.opencfg.xyz&alpn=h2%2Chttp%2F1.1&fp=chrome#Entry%20WS%20%2B%20Warp
Config 3: Single entry + WARP (XHTTP)
Same path as Config 2, different transport.
vless://8ff5dfff-fbdf-4503-a30e-5c8a0edbf464@xm.opencfg.xyz:443?type=xhttp&path=%2Fvlessxhttp&host=xm.opencfg.xyz&mode=auto&security=tls&sni=xm.opencfg.xyz&alpn=h2%2Chttp%2F1.1&fp=chrome#Entry%20XHTTP%20%2B%20Warp
Which one should you use?
More hops means more separation between your device and the exit, but also more latency. Config 1 is the choice if you care about privacy over speed. Configs 2 and 3 are lighter and faster for everyday use. WS and XHTTP behave differently depending on your ISP and network, so if one is slow or blocked, try the other.
Using Tor with this (optional)
You can set Tor as the final exit in a multi-hop chain, for example by running Tor Browser while connected to the entry VLESS server. The exit then becomes a Tor exit node instead of WARP. Keep in mind:
This improves privacy from your ISP and from the sites you visit, and it helps with bypassing some restrictions. It is not full anonymity. You are trusting the server operator (me) at the entry, and Cloudflare at the exit. Do not log in to accounts tied to your real identity and expect to stay anonymous. If your threat model is serious, use Tor properly.
Private servers and custom setups
For a private server (normal or bypass), a privacy and bypass setup, or scripts and custom scripts, message me here or on Telegram: @obakesenshi
Feedback is welcome. If a config stops working or is slow on your ISP, reply with your ISP and client app and I'll look into it.
What you need
A client that supports VLESS with XHTTP. Examples: v2rayNG or NekoBox on Android, Hiddify, v2rayN on Windows, Streisand or V2Box on iOS. Older client versions may not support XHTTP, so update first if the import fails.
Config 1: Multi-hop (3 servers + WARP)
Path:
Device > Entry (zxc.opencfg.xyz) > Relay 2 (zxcv.opencfg.xyz) > Relay 3 (xm.opencfg.xyz) > Exit (Cloudflare WARP)
Transport is XHTTP in stream-one mode over TLS, fingerprint set to Chrome.
vless://arise@zxc.opencfg.xyz:443?type=xhttp&path=%2Fassets&mode=stream-one&security=tls&alpn=h2%2Chttp%2F1.1&fp=chrome#Multi%20Hop%20XVPN%20%2B%20Warp
Config 2: Single entry + WARP (WebSocket)
Path:
Device > Entry/Relay (xm.opencfg.xyz) > Exit (Cloudflare WARP)
vless://8ff5dfff-fbdf-4503-a30e-5c8a0edbf464@xm.opencfg.xyz:443?type=ws&path=%2Fvlessws&host=xm.opencfg.xyz&security=tls&sni=xm.opencfg.xyz&alpn=h2%2Chttp%2F1.1&fp=chrome#Entry%20WS%20%2B%20Warp
Config 3: Single entry + WARP (XHTTP)
Same path as Config 2, different transport.
vless://8ff5dfff-fbdf-4503-a30e-5c8a0edbf464@xm.opencfg.xyz:443?type=xhttp&path=%2Fvlessxhttp&host=xm.opencfg.xyz&mode=auto&security=tls&sni=xm.opencfg.xyz&alpn=h2%2Chttp%2F1.1&fp=chrome#Entry%20XHTTP%20%2B%20Warp
Which one should you use?
More hops means more separation between your device and the exit, but also more latency. Config 1 is the choice if you care about privacy over speed. Configs 2 and 3 are lighter and faster for everyday use. WS and XHTTP behave differently depending on your ISP and network, so if one is slow or blocked, try the other.
Using Tor with this (optional)
You can set Tor as the final exit in a multi-hop chain, for example by running Tor Browser while connected to the entry VLESS server. The exit then becomes a Tor exit node instead of WARP. Keep in mind:
- Each extra hop adds latency. Fewer hops is faster.
- Running Tor over a regular VPN is generally not recommended.
- If you need stronger anonymity, use something like Tails, where Tor is the entry point. Another option is Tor Browser inside a browser like Brave while connected to an entry VLESS server.
This improves privacy from your ISP and from the sites you visit, and it helps with bypassing some restrictions. It is not full anonymity. You are trusting the server operator (me) at the entry, and Cloudflare at the exit. Do not log in to accounts tied to your real identity and expect to stay anonymous. If your threat model is serious, use Tor properly.
Private servers and custom setups
For a private server (normal or bypass), a privacy and bypass setup, or scripts and custom scripts, message me here or on Telegram: @obakesenshi
Feedback is welcome. If a config stops working or is slow on your ISP, reply with your ISP and client app and I'll look into it.