xtlsapi does not work with Vmess inbound
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 48/100
Research direction
Start by reproducing the reported xray_client.add_client(inbound_tag, user_id, user_email, "vmess") call against a Vmess inbound and compare it with the working Vless path. Trace how the client is added and verify that the generated Xray configuration contains the supplied user; done means the Vmess client can connect without the "user do not exist" error.
Written by the indexing model from the issue text.
Description
Bug description
For adding client to Vmess inbound I used this line of code
xray_client.add_client(inbound_tag, user_id, user_email, "vmess")
I got no error but when I want to connect to the config,
The Xray debug log shows this:
proxy/vmess/encoding: invalid user > user do not exist
Xray core version: 25.6.8
(The Vless protocol is ok)
- Dominant language
- Python
- Stars
- 64
- Forks
- 20
- PR merge metrics
- No merged PRs in 30d
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from hiddify/xtlsapi
-
bug help wanted
Difficulty 4/5 3-5 days Newbie friendliness 15/100
-
bug help wanted
Difficulty 4/5 3-5 days Newbie friendliness 42/100
-
Difficulty 4/5 3-5 days Newbie friendliness 25/100
-
enhancement question
Difficulty 4/5 3-5 days Newbie friendliness 35/100
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
Maintainers usually reply within 1 day
-
documentation
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
Maintainers usually reply within 1 day
-
Install the skills as a Claude Code pluginPossibly taken @ruban-24 claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
Maintainers usually reply within 6 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
FAIRmat-NFDI/pynxtools#874 ·
-
Eval: PublicationOpendata
Difficulty 2/5 1-3 hours Newbie friendliness 66/100