[Feature]: naiveproxy

[PUDGE133]

Is your feature request related to a problem?

The problem is that the Vless + Reality combination is already causing problems for some users in Russia.

Describe the solution you'd like

Is it physically possible to implement this proxy in this convenient web panel?

Alternatives you've considered

No response

Concrete use case

No response

Mockups, screenshots, or examples

No response

Which parts of the panel would this affect?

No response

Are you willing to help?

• I'd like to implement this feature myself and open a PR.
• I can help test once a PR is open.

Before submitting

• I searched existing issues and this feature has not been requested.
• This feature request is written in English.

[github-actions]

This looks like a duplicate of #4038, which requested the same NaïveProxy integration. Please follow that issue for updates.

Note that naiveproxy uses its own transport layer (based on Chromium's network stack) and is not part of Xray-core, which is the engine 3x-ui wraps. Adding naiveproxy support would require significant architectural work beyond a typical panel feature. If there is renewed interest in this, consider adding a comment or reaction to the original issue.

[elector1337]

This is doable, and it's already working — I just posted details on the canonical issue #4038.

Short version: my 3X-UI fork elector1337/3x-ui-naive runs NaiveProxy (Caddy + klzgrad's forward_proxy) as a managed child process next to Xray, from a dedicated /panel/naive page — with traffic stats/limits, multiple users (each with its own URL + QR), HTTP/3 toggle, subscription and Telegram-bot integration.

Out of the box:

docker pull ghcr.io/elector1337/3x-ui-naive:latest

@PUDGE133 you mentioned you're happy to help test — that'd be hugely appreciated. 🙏

[PUDGE133]

@PUDGE133, вы упомянули, что готовы помочь с тестированием — мы будем вам очень признательны. 🙏

Yes, I'm ready to test it. However, my hosting is currently experiencing some issues, and I need time for them to fix the data center issues.

I understand that you somehow managed to implement naiveproxy alongside 3x-ui. However, I'm not quite sure how? After all, you're not using a fork, but your own repository. How can I be sure your product is secure? Or is it some kind of add-on to the official 3x-ui repository?

[PUDGE133]

@elector1337
With all due respect to your work, this is not a fork. Here are the forks: https://github.com/MHSanaei/3x-ui/forks?include=active&page=1&period=2y&sort_by=last_updated

[elector1337]

You're right, and that's a fair point. That repo is a standalone one, not a github fork, so it doesn't show up in that list. So I just forked the real thing properly, here it is: https://github.com/elector1337/3x-ui . You can find it in the forks list now under elector1337. It's the same code, the naive work lives on the feature/naive-proxy branch.

About security, you don't have to trust me on my word, it's fully open source so you can just read it. It is not an add-on you install on top of official 3x-ui, it is the whole panel with naive built in. And naive is not forced into xray, it runs as a separate caddy process (caddy with klzgrad forward_proxy), the panel only manages that process. The entire difference from upstream sits in one branch, so you can compare it line by line, or build the binary yourself instead of using my docker image if you prefer.

No rush at all on the testing, sort out your hosting first and just ping me whenever you are ready. Thanks for actually looking into it.

[PUDGE133]

@elector1337 Okay. Now I'm basically ready to test it, but I don't have access to my VPS yet. So I can't say when I'll be able to test it. Plus, I don't have much experience installing this panel. My hosting provider has options with the 3x-ui panel pre-installed. And your fork isn't included, of course. So I'll have to do it manually, which is a bit complicated for me. So, for now, I'm waiting for my VPS to be fixed.

[PUDGE133]

@elector1337 #5962