xtlsapi does not work with Vmess inbound

Open
#10 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
48/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
python
Domain
api, backend

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 help wanted

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

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from hiddify/xtlsapi

All issues in hiddify/xtlsapi

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.