AnyTLS unstable in Hiddify app when subscription link is added without /sub/ (stable with /sub/ and in other apps)
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 53/100
Research direction
Compare the AnyTLS outbound generated for the Hiddify app format (without /sub/) with the /sub/ share-link output; the issue does not name the generating files or tests. Start by tracing how each subscription path builds its AnyTLS configuration, then check the relevant outputs for differences. Done when the two paths produce equivalent AnyTLS behavior and the Hiddify app connection is stable with either link.
Written by the indexing model from the issue text.
Description
Summary
AnyTLS configs from a Hiddify Manager subscription are unstable in the Hiddify app when the subscription link is added without /sub/: the connection only works sometimes. The same configs are always stable:
- in other client apps (with the same link), and
- in the Hiddify app when the link is added with
/sub/.
Details
- Protocol: AnyTLS.
- Link without
/sub/(auto-detected format for the Hiddify app): connects only occasionally / unstable. - Link with
/sub/(plain share-link subscription): always stable in Hiddify. - Other apps: always fine.
Likely cause (unverified)
Without /sub/, the panel serves a format generated specifically for the Hiddify app (sing-box JSON / auto). The AnyTLS outbound generated in that format probably differs from the share link (e.g. TLS/SNI, ALPN, fingerprint, padding or idle-session settings), which would explain why the same server is stable via /sub/ and in other apps.
Expected
AnyTLS should behave the same whichever subscription path is used. Please compare the AnyTLS outbound produced for the Hiddify app (link without /sub/) with the one produced from the /sub/ share link and fix the difference.
- Dominant language
- Python
- Stars
- 9.5k
- Forks
- 1.1k
- Avg merge
- 1d 2h
- Merged PRs (30d)
- 9
Getting set up
- Ships a Dockerfile or Docker Compose file
- No 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/Hiddify-Manager
-
Difficulty 1/5 Under an hour Newbie friendliness 88/100
hiddify/Hiddify-Manager#5689 ·
Maintainers usually reply within 1 day
-
enhancement from-telegram
Difficulty 4/5 3-5 days Newbie friendliness 40/100
hiddify/Hiddify-Manager#5691 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 3/5 1-2 days Newbie friendliness 35/100
hiddify/Hiddify-Manager#5690 ·
Maintainers usually reply within 1 day
-
bug
Difficulty 3/5 1-2 days Newbie friendliness 45/100
hiddify/Hiddify-Manager#5688 ·
Maintainers usually reply within 1 day
-
bug
Difficulty 3/5 Half a day Newbie friendliness 45/100
hiddify/Hiddify-Manager#5687 ·
Maintainers usually reply within 1 day
All issues in hiddify/Hiddify-Manager
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