Arcane is a clean and intuitive web interface for managing Docker containers, images, networks, and volumes. It removes the need for daily terminal work and lets you control your Docker environment directly from a browser.
On LumaDock, Arcane is automatically deployed using Docker Compose on Debian 13 during the first boot. No manual installation steps are required.
How Arcane is deployed on LumaDock
When you deploy a VPS with Arcane, the setup happens automatically at first boot.
Arcane runs as a Docker based service and listens on a dedicated port.
Docker and Docker Compose are already configured as part of the deployment, so the panel is ready to use once the VPS is online.
This approach keeps the system clean and avoids conflicts with other services.
Accessing the Arcane web interface
After the VPS finishes provisioning, Arcane becomes available through your browser.
Step 1 – Open the Arcane panel
Open your browser and go to:
http://your-public-ip:3552
Replace your-public-ip with the public IP address of your VPS.
Default login credentials
Arcane ships with default credentials that are displayed after deployment.
Step 2 – Log in with default credentials
Username:
arcanePassword:
arcane-admin
After the first login, Arcane will prompt you to change the default password. This step is mandatory and helps secure access to the panel.
What you can manage with Arcane
Arcane focuses on Docker management through a visual interface.
From the dashboard, you can:
Start, stop, and restart containers
Create and remove Docker images
Manage networks and volumes
Inspect container logs and status
Advanced Docker tasks are still possible over SSH, but most daily operations can be handled directly in the panel.
Using Arcane behind a reverse proxy
Arcane can be placed behind a reverse proxy such as nginx. This is useful if you want to access it through a domain name and enable HTTPS.
The reverse proxy must support WebSockets and be configured correctly. Below is an official sample nginx configuration.
server {
listen 80;
server_name arcane.yourdomain.com;
return 301 https://$host$request_uri;
}
server {
listen 443 ssl http2;
server_name arcane.yourdomain.com;
ssl_certificate /etc/letsencrypt/live/arcane.yourdomain.com/fullchain.pem;
ssl_certificate_key /etc/letsencrypt/live/arcane.yourdomain.com/privkey.pem;
add_header X-Frame-Options "*";
location / {
add_header X-Robots-Tag "noindex, nofollow";
proxy_pass http://127.0.0.1:3552;
proxy_set_header X-Real-IP $remote_addr;
proxy_set_header Host $host;
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
proxy_set_header X-Forwarded-Proto $scheme;
proxy_http_version 1.1;
proxy_set_header Upgrade $http_upgrade;
proxy_set_header Connection "upgrade";
proxy_cache_bypass $http_upgrade;
}
access_log /var/log/nginx/arcane-access.log;
error_log /var/log/nginx/arcane-error.log debug;
}
Make sure your firewall allows access to ports 80 and 443 when using a reverse proxy.
Security recommendations
Arcane provides full control over Docker, so securing it is important.
Recommended actions:
Change the default password immediately
Use a firewall to restrict access to port 3552
Prefer HTTPS when exposing Arcane publicly
Keep Debian and Docker packages updated
Avoid exposing Arcane directly to the internet without authentication or TLS.
Learn more about Arcane
For detailed feature descriptions and advanced configuration options, refer to the official Arcane documentation.
Arcane is a solid choice if you want visual control over Docker without giving up flexibility or control.



