Bad Gateway when Domain points to HTTPS service #3128
Replies: 10 comments
-
|
since you are using a proxy/load balancer in traefik it is usual that traefik terminates the ssl connection and just uses http-http for the last step to the container. |
Beta Was this translation helpful? Give feedback.
-
yes
It has self signed. Is that considered "valid"?
where can I set it? |
Beta Was this translation helpful? Give feedback.
-
|
reference |
Beta Was this translation helpful? Give feedback.
-
|
Thank you @djsisson . I've added
But unfortunatelly this did not work :( |
Beta Was this translation helpful? Give feedback.
-
|
Its a servers transport option only, which is static config. |
Beta Was this translation helpful? Give feedback.
-
Beta Was this translation helpful? Give feedback.
-
|
Using the n8n template, and using a custom domain following the docs in my case that I'm using cloudflare https://docs.dokploy.com/docs/core/domains/cloudflare works fine
|
Beta Was this translation helpful? Give feedback.
-
|
@eximius313 ok i must have misunderstood what you were trying to do, if you are using your own certificate to browse to a domain then you just need to add it to traefik, the servers transport is for inter container communication, which you do not need to alter https://doc.traefik.io/traefik/reference/routing-configuration/http/tls/tls-certificates/ |
Beta Was this translation helpful? Give feedback.
-
|
@Siumauricio - please notice, that in your example @djsisson - I'll look into it |
Beta Was this translation helpful? Give feedback.
-
|
Feel free to explore. I don't think this is a dokploy error. Bad gateways can occur for several reasons, the most common being:
I do not believe it is a dokploy issue as such. I will pass it on to discussions to keep the issues with bugs and features clean! Thank you |
Beta Was this translation helpful? Give feedback.







Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
To Reproduce
Current vs. Expected behavior
Current:
Browser dieplays "Bad Gateway"
Expected:
Domain routes to HTTPS
Provide environment information
Which area(s) are affected? (Select all that apply)
Docker Compose
Are you deploying the applications where Dokploy is installed or on a remote server?
Same server where Dokploy is installed
Additional context
Will you send a PR to fix it?
Maybe, need help
Beta Was this translation helpful? Give feedback.
All reactions