HOKIO / PRODUCT GUIDE
Give your local web app a public URL.
A Hokio URL link carries supported HTTP requests from a browser or client to an application running on your own device. The assigned address stays with the link while it remains active.
URL connection path
Browser or HTTP client → HTTPS gateway → URL relay → outbound device connection → your local web app.
Run your application on the device. Choose its local target in the Hokio program on that device. The panel displays the reported target for inspection; it cannot choose or change the application's port.
Set up a URL from your device
Install the native Hokio preview. Sign in to your workspace and generate a code in Connect a device. Then run:
hokio setup
hokio service install
hokio service start
hokio statusFor the portable Windows download use .\hokio.exe. In setup, enter the code, select Public URL or Both, enter your application's listening port, and choose a name. Availability is checked before registration; the name is reserved only on successful registration. If taken or reserved, choose another name and retry setup. Webhook names are assigned automatically.
The preview reserves a Webhook link during registration even for URL-only mode. The workspace must also have URL capacity and the URL feature enabled. If provisioning remains pending, check its panel status before repeating setup. The existing Store and legacy clients do not provide this native URL setup.
New URL links allow GET, HEAD, and OPTIONS. Enable other required methods in the link policy before testing forms or APIs. After starting the background service, you can close the terminal while your application stays running. Windows automatic startup occurs at user sign-in; Linux requires its user service manager. For startup and recovery, follow the complete connection guide.
Check the URL connection in order
- Confirm the local application responds on the device before opening a public URL.
- Connect the device in your workspace and confirm its URL runtime state.
- Read the assigned URL and effective methods, paths, body limits and timeout in the link detail.
- Send a harmless HTTP request to the assigned URL and inspect its status and request ID in Hokio.
The application's own login, sessions and permissions remain its responsibility. A login page or application error is a response from that application; it is not proof of a relay failure.
Understand a failed URL request
- Policy denial or rate limit
- Review the effective methods, paths and traffic limits for the link.
- Device offline
- Restore the device's outbound connection, then retry the request.
- Local target unavailable
- Start or repair your application on the device and confirm its listening port there.
- Unsupported transport
- Check the effective HTTP limits shown in the panel. Browser WebSocket upgrades and unrestricted uploads are not promised.
The public URL stays assigned during a recoverable connection failure. Requests received while offline are not replayed automatically.