Intermittent 502 Bad Gateway with Multiple Domains or Ports on the Same Service

[binaryYuki]

Hello community,

I've been experiencing a persistent and strange issue for quite a long time, and I wanted to reach out for insights or suggestions. Here's the problem:

When I run the same service and bind it to two different domains, one of the domains will often display a 502 Bad Gateway error. This happens even though both domains are pointing to the same service.

Additionally, I've noticed a similar issue when using different ports for the same service. For example, one port will work perfectly fine, while the other port will intermittently fail with a 502 Bad Gateway error.

What's even more perplexing is that the behavior seems random at times. Sometimes everything works as expected, but other times one of the domains or ports will fail without any clear reason.

Key Observations:

• The issue happens with both different domains and different ports for the same service.
• One domain/port will work, while the other will intermittently fail with a 502 Bad Gateway error.
• The issue seems random—sometimes everything works, and other times it doesn't.
• Restarting the service or the reverse proxy (if applicable) sometimes resolves the issue temporarily.

I‘ve tried #821 and #1004 but seems doesn't work for me

[Siumauricio]

Hi, can you share your docker compose?

[binaryYuki]

Hi,

Thanks for following up!

I deployed it as a standalone server instead of using Compose. After reinstalling the system, everything is working properly now. It seems the issue was related to Traefik's cache or server DNS.

I'll mark it as resolved as it seems not a bug of dokploy.