Common issues and their resolutions.
- DNS: Verify that your client machine can resolve the following subdomains:
desktop.<user>.remote-dev-box(for desktops)traefik.remote-dev-box(for the dashboard)- Quick Fix: Ensure these are in your
/etc/hostsor that your wildcard DNS is working.
- Dashboard: The Traefik dashboard is accessible at
https://traefik.${DOMAIN_NAME}/. - HTTPS: Ensure you are using
https://, as KasmVNC and Traefik require TLS. - Auth: Double-check your credentials in
users.htpasswd. Any valid user added viamanage_users.shcan access the dashboard. - Docker API Version: If you see "client version 1.24 is too old" in Traefik logs, your Docker host requires a newer API version (minimum 1.44 for Docker 29+).
- Fix: Upgrade Traefik to
v3.6.1or newer (e.g.,v3.6.8). - Override: If using
docker-compose.override.yml, ensure you override thetraefikimage version to a compliant release.
- Fix: Upgrade Traefik to
- This usually indicates the user container is starting or has crashed.
- Check container status:
./admin/manage_users.sh list. - View logs:
docker logs remote-dev-box-<username>.
- This is expected when using self-signed certificates. Click Advanced -> Proceed to access the desktop.
- For a more permanent fix, import the generated
certs/full_cert.peminto your browser's trust store.
- Ensure the container was started with the correct Seccomp profile. This is handled automatically by the deployment scripts using
admin/security/rdb.seccomp.json. - Check if your environment allows the
userfaultfdorptracesyscalls (if needed by your specific IDE flow), though these are restricted by default for security.
- Ensure you have the necessary Docker permissions or use
sudo. - Scripts in
admin/should be executable (chmod +x admin/*.sh).
- Traefik Propagation: Traefik takes ~2-5 seconds to reload configuration when a new route is added. The test script waits 5 seconds by default, but slow remote hosts may need more.
- Basic Auth: Ensure you haven't changed your password without updating the test environment (the test uses the username as the password by default for
<username>). - RDB Daemon: Verify the proxy daemon is running:
ps aux | grep rdb.
- Path: Ensure you are running the test from the root of the project or that
rdbis in yourPATH. - Provisioning: If
~/admin/testing/is missing, ensure the box was created with the latestmanage_users.sh.
- Seccomp: This is usually a Seccomp violation. Check
dmesgon the host:sudo dmesg | grep seccomp. - If a required syscall is blocked, it must be added to
admin/security/traefik.seccomp.json(for infrastructure) oradmin/security/rdb.seccomp.json(for users).