Remote access7 min
WebProxy for private UIs
Open HTTP and HTTPS management pages without public port forwards.
Outcome
A private router, NAS, printer or appliance UI opens through Wantastic.
Before you start
- An online device
- A reachable HTTP/HTTPS service
- The target scheme and port
Define the target precisely
- 1Verify the UI works on the local network.
- 2Record HTTP versus HTTPS and the exact port.
- 3Use a literal connected address or a name resolvable in the management path.
- 4Create the WebProxy entry for the intended device.
Operational note: WebProxy does not replace the appliance login, certificate or base URL configuration.
Open and validate the UI
- 1Launch the entry.
- 2Confirm page title and device identity before signing in.
- 3Check navigation remains in the intended application.
- 4Test WebSockets and absolute redirects if the application uses them.
- 5Keep the appliance's own authentication enabled.
Verify the result
The private UI loads without WAN forwarding.
Login reaches the expected appliance.
Original authentication remains required.
Revoking the path removes reachability.
Common issues
Blank page or redirect loop.
Likely cause
The app hard-codes its hostname, scheme or base path.
Fix
Correct scheme/port and configure trusted proxy or base URL settings where supported.
TLS warning.
Likely cause
The appliance uses a self-signed or name-mismatched certificate.
Fix
Verify its fingerprint out of band and replace it with an internal CA certificate when possible.
Continue with
WebSSH sessionsOpen a browser terminal over the private overlay and recover from transient transport loss.Security modelReduce public exposure, credential sprawl and lateral reach while keeping operations practical.Common issues and fixesStart from the symptom, isolate the failing layer and verify recovery at the target.