1

Public URL flipped to 502 today even though the app still opens locally, trying to narrow down the usual culprit before I start changing random things

1

Works on localhost and LAN IP, but remote users on the LocaltoNet address get refused immediately.

3

Tunnel connects fine, localhost works, but the public link now serves PHP as a download/raw output and I'm trying to pin down what changed.

1

Was working earlier through the public URL, localhost still loads fine. Trying to figure out whether to check HTTPS forcing, base URL settings, or forwarded headers first.

1

Tunnel target is still reachable through the LocaltoNet URL, only the custom hostname began failing today.

0

Login works and localhost still responds, but existing HTTP tunnels won't start or generate a public URL.

2

Worked earlier, no server changes today. Same PC and local devices can join fine, only the LocaltoNet TCP address fails immediately.

1

App is fine on localhost today, but the public tunnel started throwing 502 and I'm trying to narrow down the usual culprit.

0

Server works on 127.0.0.1, nothing changed on the router, trying to narrow down the LocaltoNet settings that matter first

0

Tunnel is up and the LocaltoNet URL opens fine, but my own domain suddenly fails in browser. Trying to figure out if this is DNS/proxy/cert side.

+