-
-
Notifications
You must be signed in to change notification settings - Fork 2
Open
Milestone
Description
Problem
Deeploy currently requires ports 80/443 to be available. Users with existing services on those ports (nginx, Caddy, etc.) can't easily run deeploy alongside them.
Feedback from community:
"Ports 80, 443 open - Mostly gonna be an issue. Why can't we proxy?"
Research
Checked how Coolify and Dokploy handle this:
- Same limitation - they also require 80/443 or manual configuration
- Both recommend Cloudflare Tunnels as workaround
- No elegant automatic solution exists in the ecosystem
Proposed Solution
1. Configurable ports via .env (2 lines change)
docker-compose.yml
ports:
- "${HTTP_PORT:-80}:80"
- "${HTTPS_PORT:-443}:443"User can then set in /opt/deeploy/.env:
HTTP_PORT=8080
HTTPS_PORT=84432. Documentation for
- Custom ports setup
- Cloudflare Tunnels setup
Important caveat (must be documented clearly)
Both options break deeploy's zero-config experience:
- Custom ports: User must manually configure their proxy for each domain
- Cloudflare Tunnels: User must manually add each domain in Cloudflare dashboard
The only fully automatic setup remains: dedicated VPS where deeploy owns ports 80/443.
Files to modify
- docker-compose.yml – add env var interpolation for ports
- docs/ – add "Running behind a proxy" guide
- docs/ – add "Cloudflare Tunnels" guide
- README.md – add note about dedicated VPS recommendation
Metadata
Metadata
Assignees
Labels
No labels