233boy / 233boy/Xray

man, what can i say?

Open
#76 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Shell
Stars
2.7k
Forks
1.1k
Avg merge
1d 6h
Merged PRs (30d)
2

Description

Xray 24.11.30 (Xray, Penetrates Everything.) 98a72b6 (go1.23.3 linux/amd64)
A unified platform for anti-censorship.
2024/12/10 02:01:17 Using confdir from arg: /etc/xray/conf
2024/12/10 02:01:17 [Info] infra/conf/serial: Reading config: &{Name:/etc/xray/config.json Format:json}
2024/12/10 02:01:17 [Info] infra/conf/serial: Reading config: &{Name:/etc/xray/conf/Shadowsocks-12447.json Format:json}
2024/12/10 02:01:17 [Info] infra/conf: [/etc/xray/conf/Shadowsocks-12447.json] appended inbound with tag: Shadowsocks-12447.json
2024/12/10 02:01:17 [Info] infra/conf/serial: Reading config: &{Name:/etc/xray/conf/Shadowsocks-37582.json Format:json}
2024/12/10 02:01:17 [Info] infra/conf: [/etc/xray/conf/Shadowsocks-37582.json] appended inbound with tag: Shadowsocks-37582.json
2024/12/10 02:01:17 [Info] infra/conf/serial: Reading config: &{Name:/etc/xray/conf/Shadowsocks-55665.json Format:json}
2024/12/10 02:01:17 [Info] infra/conf: [/etc/xray/conf/Shadowsocks-55665.json] appended inbound with tag: Shadowsocks-55665.json
2024/12/10 02:01:17 [Info] infra/conf/serial: Reading config: &{Name:/etc/xray/conf/VLESS-REALITY-17871.json Format:json}
2024/12/10 02:01:17 [Info] infra/conf: [/etc/xray/conf/VLESS-REALITY-17871.json] appended inbound with tag: VLESS-REALITY-17871.json
Failed to start: app/proxyman/inbound: failed to listen TCP on 64870 > transport/internet: failed to listen on address: 127.0.0.1:64870 > transport/internet/tcp: failed to listen TCP on 127.0.0.1:64870 > listen tcp 127.0.0.1:64870: bind: cannot assign requested address

Contributor guide

No contributing guide indexed for this repository

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.

Research direction

Start with the logged configuration paths /etc/xray/config.json and /etc/xray/conf/*.json, then trace which entry requests 127.0.0.1:64870. Reproduce the startup failure and determine the configuration change or script behavior needed for Xray to start without the bind error.

Written by the indexing model from the issue text.

Assessment

Tech stack
shell
Domain
networking
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.