Device registration
Claiming a device, naming it, checking the slug and confirming it appears in your account.
Early support
Stuck one hop away? Let’s get you connected.
lanhopper support is still taking shape, but the goal is simple: help you register devices, understand connection paths and reach the network service you actually need.
Connection checklist
field notes
$ lanhopper status factory-gateway
device online, outbound link active
$ ssh -J factory@lanhopper.com root@192.168.8.12
checking account key and target reachability...
route ready from inside the LAN
Help areas
Support for the parts that usually go sideways first.
The formal help center is not here yet. For now, this page is a map of the common questions we expect around early deployments.
Network reachability
Understanding public-side status, LAN interfaces, local IPs and whether a target host is reachable.
Terminal access
Opening SSH, Telnet or serial sessions and using direct SSH jump, SOCKS or local forwarding.
Web tunnels
Publishing an internal web UI through a protected domain and choosing protocol or rewrite options.
Before contacting us
A few details make remote debugging much faster.
If you are reporting a problem, send the practical facts around the device and target service. No need for a perfect diagnosis.
Still early:
support channels and response expectations are not formalized yet. We are using early requests to build the right process.
Device context
- Device name or slug
- Whether it appears online
- Platform and version if visible
Target service
- Host or local IP
- Protocol and port
- Browser, SSH or serial path
Observed behavior
- Error message or status
- What worked before
- Recent network changes
Contact paths
Use the closest door for the kind of question you have.
These are placeholder paths for now, but the categories are real. They reflect the conversations lanhopper should be ready to handle.
1
Setup and first connection
You have a device and want help getting from registration to the first successful route.
2
Protocol-specific troubleshooting
SSH, Telnet, serial, web tunnel, SOCKS or port forwarding does not behave as expected.
3
Deployment conversation
You are thinking about multiple devices, customer sites or operational requirements.
Tell us what you are trying to reach.
The fastest support conversation starts with the device, the target service and what happened when you tried.