This tutorial outlines the process for securing your AI agent, OpenClaw, on MilesWeb. The article entails the SSL role in facilitating the process. After configuration, your OpenClaw dashboard is accessible via HTTPS using an automatically assigned subdomain.
SSL is required for OpenClaw to function correctly. Without it, dashboard access over plain HTTP triggers errors that prevent normal operation, including “Device identity required,” “Device signature expired,” and “Control UI requires device identity (use HTTPS or localhost secure context).” It is recommended to configure SSL immediately after deploying OpenClaw to avoid running into these issues.
Adding SSL with Traefik
OpenClaw’s Docker deployment constitutes pre-configured Traefik labels. This means you do not need to manually configure certificates; deploying the Traefik project alongside OpenClaw automatically enables SSL.
Step 1 – Deploy Traefik from the Docker catalog
- Go to your control panel → VPS → select your server → Docker Manager.
- Click on Deploy Traefik.
- Enter the valid email address for SSL. An invalid email results in an unsuccessful SSL installation.
- Wait for the Traefik deployment status to confirm it is running as the container boots.
- You deploy Traefik before or after OpenClaw; the order does not matter.
Step 2 – Access OpenClaw via HTTPS
- Once both OpenClaw and Traefik are running:
- Go to Docker Manager → Docker projects.
- Find your OpenClaw project in the list.
- Click on “Open link” located in the “Access” column.
- You are redirected to your secured OpenClaw dashboard at a URL such as https://openclaw-xxxx.srv123456.mlwb.cloud.
NOTE: Without Traefik, the Open link redirects to your VPS IP address and port without using SSL. Once Traefik is active, the system automatically prioritizes the secured subdomain, ensuring the ‘Open link’ feature defaults to an HTTPS connection.
Your OpenClaw is now SSL-encrypted. Any traffic to your dashboard is automatically encrypted, and no additional settings are necessary. It will revert your dashboard to plain HTTP, resulting in device identity and signature errors, effectively preventing access to the control interface.
