Jump to content

Edit History

flowers_ph

flowers_ph

On 9/29/2025 at 7:21 PM, Progressify said:

I hope you were able to resolve your issue. Here are some possible solutions you can try.

When using Traefik, keep in mind the following:

Bad Gateway: This usually means the container is not correctly connected to the Traefik network, or the container has multiple networks and Traefik cannot determine which one to use. In this case, simply add the following label: 

- "traefik.docker.network=<your-traefik-network-name>"

 

404: This usually means the container is stopped or has been killed. If the container is running, you may need to add the load balancer label: 

- "traefik.http.services.<your-traefik-service-name>.loadbalancer.server.port=<port-where-apache-is-running>"

For example: 

- "traefik.http.services.mynewprestashopsite.loadbalancer.server.port=8000"

 

Thanks for the reply. I got it working - it was actually quite a thing to get it working. I can share labels and middleware if anyone needs it.

flowers_ph

flowers_ph

On 9/29/2025 at 7:21 PM, Progressify said:

I hope you were able to resolve your issue. Here are some possible solutions you can try.

When using Traefik, keep in mind the following:

Bad Gateway: This usually means the container is not correctly connected to the Traefik network, or the container has multiple networks and Traefik cannot determine which one to use. In this case, simply add the following label: 

- "traefik.docker.network=<your-traefik-network-name>"

 

404: This usually means the container is stopped or has been killed. If the container is running, you may need to add the load balancer label: 

- "traefik.http.services.<your-traefik-service-name>.loadbalancer.server.port=<port-where-apache-is-running>"

For example: 

- "traefik.http.services.mynewprestashopsite.loadbalancer.server.port=8000"

 

thansk for the reply. I got it working - it was actaully quite a thing to get it working. I can share labels and middleware if anyone needs it.

×
×
  • Create New...