Paste the Base32 secret you saved when you first set up TOTP (e.g. JBSWY3DPEHPK3PXP).
If you don't have it, you'll need to SSH into the server to rotate the encryption key.
Secret accepted. Add it to your authenticator app and enter a 6-digit code to confirm.
π€οΈ
--
--Β°
--
--
☆FREE TIER
DashCaddy Verification Info
Current version details and updater verification status.
Let's set up your self-hosted app dashboard. This will only take a few minutes.
Auto-detected from your browser. All deployed apps will use this timezone.
Choose your configuration:
Professional Home Lab Setup
Configure your custom TLD and certificate authority
Your apps will use this TLD. Examples: .sami, .home, .lab, .local, .internal
π± Preview: uptime.home, nextcloud.home
This name appears in browser certificate details. Make it memorable!
DashCaddy will automatically create DNS records for your apps
βΉοΈ How to get your token
Open Technitium DNS web panel
Go to Settings β API
Create a new token with "Administration" permission
Copy the token and paste it here
Simple Setup
Access your apps directly via IP addresses and ports
β What you'll have:
Direct access via IP:Port (e.g., http://<your-ip>:8080)
No DNS configuration needed
No SSL/certificate setup
Apps work immediately after deployment
β οΈ Limitations:
Must remember IP:Port for each app
No pretty URLs
HTTP only (no HTTPS encryption)
Not recommended for sensitive data
Use "localhost" for same-host deployments, or your server's IP
Public Server Setup
Configure for internet-accessible apps with Let's Encrypt SSL
Your registered domain name (must point to this server)
Required for Let's Encrypt certificate renewal notifications
β οΈ Requirements:
Port 80 and 443 must be open to the internet
Domain DNS must point to this server's public IP
Server must be reachable from the internet
Only one DNS record needed (for the main domain)
Review Your Configuration
Make sure everything looks correct before finishing
πΎ
Disk Usage & Health-Check Data
DashCaddy's health checks log response times, uptime history, and incidents for every monitored service.
Over time this data accumulates and can consume significant disk space β especially on small VPS or
SD-card installs. After setup, open Health β Configure β Global Settings to set a
data retention period (default 30 days), adjust the polling interval,
and configure a disk-usage warning threshold so you're alerted before storage runs low.
β You can change these settings later
Go to Settings β System Configuration to edit your setup anytime
β οΈ Disk Usage Note
Important information about storage before you finish
β οΈ
Disk Usage Note:
DashCaddy stores up to 500 health check entries per service (plus container statistics and event logs).
At high check frequencies this may consume significant disk space β on a host with many services the history file can grow to tens of megabytes.
Adjust the health check interval, max entries per service, and health retention period in Disk Safety (the πΎ Disk button in the top bar) to control disk usage.
π Recommended after setup
Open the πΎ Disk button in the top bar (opens the Disk Safety modal)
Set a health check polling interval (default: 30s)
Set a health retention period (default: 30 days)
Cap max health entries per service (default: 500)
Cap max stats entries (default: 500)
Click Clean Up Now to purge old data immediately
β You can change these settings later
Go to Settings β System Configuration to edit your setup anytime