Files
v2rayA/service/common
Zakk 7b4ad06e75 fix: reach the core's proxy ports on loopback inside Docker
In Docker, subscription and RoutingA updates through the core dialled
the default gateway instead of 127.0.0.1, a leftover from when the core
ran outside v2rayA's container. The core now runs in v2rayA's own
network namespace and, unless port sharing is on, listens on 127.0.0.1
only. With host networking the gateway is the LAN router, and on a
bridge network the request only came back to the container when port
sharing was on and the port was published, so updates in the "proxy"
and "port rules" modes failed with connection refused.

Fixes #2139
2026-11-17 23:11:30 +11:00
..
2026-08-16 15:35:44 +03:00
2026-02-04 21:11:26 +08:00