Traefik–Poste.io SSL Setup
Budget: ₹600 – ₹1,500 INR
I’m running a VPS where Dokploy spins up several Docker containers behind Traefik v2. One of those containers is a Poste.io mail server. DNS (A/AAAA, MX, SPF, DKIM) is already correct, but Poste.io fails to enable its built-in Let’s Encrypt because Traefik currently owns ports 80/443 and handles ACME for my other apps.
Here’s what I need:
• Adjust Traefik v2 so it no longer blocks Poste.io’s certificate requests while still issuing certificates for the rest of my stack. I’m fine with whichever clean solution you prefer—separate entrypoints, passthrough TLS, wildcard cert sharing, or disabling Traefik’s ACME only for mail-related sub-domains—as long as it survives container restarts and renewals.
• Update the relevant Docker / Dokploy configs (labels, static or dynamic files) plus any Poste.io overrides, then commit them to my repo.
• Prove success: Poste.io’s admin panel should show an active Let’s Encrypt certificate, SMTP/IMAP/POP3/HTTPS must negotiate TLS correctly, and Traefik must still serve valid certificates for my other services.
Please document the key steps so I can replicate the setup on a fresh VPS later.
Here’s what I need:
• Adjust Traefik v2 so it no longer blocks Poste.io’s certificate requests while still issuing certificates for the rest of my stack. I’m fine with whichever clean solution you prefer—separate entrypoints, passthrough TLS, wildcard cert sharing, or disabling Traefik’s ACME only for mail-related sub-domains—as long as it survives container restarts and renewals.
• Update the relevant Docker / Dokploy configs (labels, static or dynamic files) plus any Poste.io overrides, then commit them to my repo.
• Prove success: Poste.io’s admin panel should show an active Let’s Encrypt certificate, SMTP/IMAP/POP3/HTTPS must negotiate TLS correctly, and Traefik must still serve valid certificates for my other services.
Please document the key steps so I can replicate the setup on a fresh VPS later.