Closed lorenzomigliorero closed 1 month ago
+1 same issue here (getting error 502)
I also get error 502 when I deploy a Node JS app. Healthcheck is working fine.
I'm using Caddy.
The option to switch back to Traefik is disabled so I can't test on Traefik.
This setup has quite unexpected behavior.
I have three applications (Nuxt using SSR with node .output/server/index.mjs
).
Two of these applications work perfectly, and just one is causing issues.
All three have the exact same setup.
This one is causing issues and doesn't work either with Static build + Nginx or with Node.
THE ONLY difference between them is the proxy port (each one has a unique available port) and the subdomain.
Did you guys make some progress within this subject?
This has been addressed and if you want you can generate labels only for the specific proxy you are using, the only downside to this is that you will have to manually regenerate the labels for each source if you switch proxies and have this option enabled. Note that there is no harm in having both traffic and caddy labels, it is just not as clean as just having one. The option is under Server > Proxy and then:
Description
I have one server with Caddy as a proxy, but all my resources (no matter the build pack) contain labels for both Traefik and Caddy. Only the caddy ones should be generated. I'm unsure how tricky it is to solve, but it'd be a nice addition.
Minimal Reproduction (if possible, example repository)
Version
v4.0.0-beta.307