MHSanaei 1f052c0e8f fix: preserve TLS cert file paths when deploying inbound to remote node ...

When creating a Hysteria (or any TLS-required) inbound from the central
panel and deploying it to a remote node, sanitizeStreamSettingsForRemote
was unconditionally stripping certificateFile / keyFile from the TLS
settings. This left Xray on the remote node with a TLS block containing
no certificate, causing Xray to crash and the inbounds page to hang.

The fix: only strip cert file paths when inline certificate content
(certificate / key arrays) is also present in the same entry — those
file paths are then truly redundant. When only file paths are present
the user explicitly entered paths that live on the remote node's
filesystem; they are now passed through untouched.

Fixes #4370

2026-05-14 12:41:08 +02:00

..

local.go

feat(nodes): traffic-writer queue, full-mirror sync, WS event fixes

2026-05-10 16:25:23 +02:00

manager.go

feat(nodes): traffic-writer queue, full-mirror sync, WS event fixes

2026-05-10 16:25:23 +02:00

remote_test.go

fix: preserve TLS cert file paths when deploying inbound to remote node

2026-05-14 12:41:08 +02:00

remote.go

fix: preserve TLS cert file paths when deploying inbound to remote node

2026-05-14 12:41:08 +02:00

runtime.go

feat(nodes): traffic-writer queue, full-mirror sync, WS event fixes

2026-05-10 16:25:23 +02:00