Resolving Disconnection Issues in OpenClaw Control UI

If you're working with OpenClaw and encounter the 'Disconnected (1008): control ui requires HTTPS or localhost (secure context)' error, you're not alone. This issue often arises when attempting to run the interface on a Hostinger VPS, as outlined in a user query on Reddit.

The core of this issue is that the control UI requires a secure connection provided by HTTPS or localhost, but your setup might be using HTTP. To restore access, you have a few options:

Solution Options

• Switch to HTTPS: Implement HTTPS using a tool like Tailscale Serve. This involves setting up Tailscale on your VPS to create a secure connection, ultimately preventing your browser from blocking the device identity.
• Use Localhost: If possible, run the application on localhost by visiting http://127.0.0.1:18789 directly on the gateway host.
• Allow Insecure HTTP Auth: For those who need to stay on HTTP, modify the configuration to allow insecure authentication. This involves setting gateway.controlUi.allowInsecureAuth: true in the configuration file, though this should only be done with care as it reduces your security posture.

Practical Steps

Start by determining which solution best fits your environment:

1. For HTTPS: Follow the Tailscale Serve documentation to configure HTTPS access.
2. For Localhost: Ensure your application and the machine accessing it are both on the same network, then open the specified URL.
3. For Insecure HTTP: Update your VPS configuration file to include gateway.controlUi.allowInsecureAuth: true. Be sure you understand the security implications.

This needs some configuration on your VPS. You'll typically be editing a configuration file, often found either in your project's directory or a system-wide configuration path depending on your setup.