XRayMesh v3.1.0 - Tunnels Between Servers Fixed

XRayMesh 3.1.0 fixes tunnels between servers: you can again create, edit and delete a tunnel on another server of the mesh from any panel.

Install / update

bash <(curl -fsSL https://raw.githubusercontent.com/Erfan-XRay/XRayMesh/main/xraymesh.sh)

Servers on 3.0.x or 2.2.x: run xraymesh update or use Update in the panel. Update the server whose panel you use to manage tunnels; the other servers work with it as they are.

Tunnels on other servers

• No more "NetworkError" or JSON errors: picking another server as a tunnel's origin crashed the panel while it forwarded the request, so the browser got no answer. Create, edit and delete now reach that server.
• Enough time for the first tunnel: the first tunnel of an engine installs it on that server, which can take minutes. Remote changes now wait up to 270 seconds instead of 8, and an offline server is reported within seconds.
• Clear errors: a failed change says why: the server is offline, the network secrets differ, the server needs an update, or it is still applying the change.
• Safer changes: the panel checks requests from other servers the same way as its own, runs tunnel changes on a server one at a time, and never sends a timed-out change twice.
• Destination list: no longer offers the tunnel's own origin server.
• While a change runs on another server, the form says it can take a few minutes.

Panel

• An unexpected server error now shows a readable message instead of dropping the connection.

Full list of changes: CHANGELOG.md