xray not activated on 14.2.0
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 42/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- python
- Domain
- backend, networking
Research direction
The failure occurs while Xray loads /opt/hiddify-manager/generated/xray.json and rejects the GOOGLE-CN geosite rule. Start by tracing how the panel generates Xray routing rules and where its geodata is obtained or validated; the issue does not name a source file or test. Done means identifying and fixing the cause so Xray starts without requiring manual config edits or a panel reinstall.
Written by the indexing model from the issue text.
Description
Can anyone tell me how to fix the issue in panel 14.2.0 that’s preventing Xray from activating? All my VLESS connections are down!
Nov 12 10:35:32 WODPC xray[2022767]: Xray 26.10.31 (Xray, Penetrates Everything.) a4a3dff (go1.27.3 linux/amd64)
Nov 12 10:35:32 WODPC xray[2022767]: A unified platform for anti-censorship.
Nov 12 10:35:32 WODPC xray[2022767]: Failed to start: main: failed to load config files: [/opt/hiddify-manager/generated/xray.json] > infra/conf: failed to build routing configuration > infra/conf: invalid field rule > common/geodata: illegal domain rule: geosite:google-cn > common/geodata: failed to check code GOOGLE-CN from geosite.dat > EOF
Nov 12 10:35:32 WODPC systemd[1]: hiddify-xray.service: Main process exited, code=exited, status=23/n/a
Nov 12 10:35:32 WODPC systemd[1]: hiddify-xray.service: Failed with result 'exit-code'.
Nov 12 10:35:35 WODPC systemd[1]: hiddify-xray.service: Scheduled restart job, restart counter is at 167.110:40
Removing GOOGLE-CN from the Xray config used to help, but now it doesn't.
Reinstalling the panel doesn't help either.
- 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