xray not activated on 14.2.0

Open
#5,682 2 comments 0 reactions 0 assignees View on GitHub

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

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

bug need_attention

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

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/Hiddify-Manager

All issues in hiddify/Hiddify-Manager

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.