D
Dokploy•6mo ago
Firdaus

Dokploy not reachable with custom domain

Hi all, I followed the docs here https://docs.dokploy.com/en/docs/core/domain/requirements but I cannot access the dokploy dashboard through my custom domain. Here are some info that might be useful and screenshots: - I use Digital Ocean droplet for VPS provider - Domain is registered on Cloudflare (domain is purchased from there) - Added a DNS record (as per the docs) - Change Cloudflare mode to Full (Strict) - Change the domain in dokploy dashboard dashboard/settings/server - Set certificate to None in dokploy - Reload Traefik Also, there seems to be an error in the Traefik log 2024-11-03T18:34:35Z ERR error="service \"dokploy-traefik\" error: port is missing" container=dokploy-traefik-y71gm3253qxpigvo1habu4ecg providerName=swarm Please let me know anything else you need from me 🙏
Requirements
See a requirements for a domain for the Dokploy panel
No description
No description
No description
11 Replies
Firdaus
FirdausOP•6mo ago
Forgot to send this screenshot
No description
AgustĂ­n
Agustín•6mo ago
Hello đź‘‹ Try with Full instead of Full (Strict) on your Cloudflare SSL config
No description
Firdaus
FirdausOP•6mo ago
I just tried it, still same issue. I also tried refreshing Traefik after I change from Full (Strict) to Full and the issue is still the same
AgustĂ­n
Agustín•6mo ago
Try it again and delete the cloudflare cache under cloudflare cache options (purge btn) It takes some minutes to apply the changes
Firdaus
FirdausOP•6mo ago
No description
Firdaus
FirdausOP•6mo ago
I clicked purged everything will wait a bit as you suggested it seems the issue still persist
AgustĂ­n
Agustín•6mo ago
Another thing you could try is setting the certificate to Let's Encrypt—Cloudflare should override it. I think it’s worth a shot; I’m not entirely sure why setting the certificate to 'none' is causing a 404
Firdaus
FirdausOP•6mo ago
yup that did the trick changing the cert fixed it I followed the instruction on the docs, but I guess my case is just different for some reason
AgustĂ­n
Agustín•6mo ago
Sounds good, I believe it’s a bug, as I’m experiencing the same issue—setting the certificate to 'none' makes the panel inaccessible from the subdomain
Siumauricio
Siumauricio•6mo ago
when you have full strict in cloudfare you need to use certificate letsencrypt
Firdaus
FirdausOP•6mo ago
I see Might be just me but it wasn't clearly stated in the docs

Did you find this page helpful?