You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If you ssh into the node service and try to curl -L appserver_nginx, you'll see results from ALL apps you're running with an appserver_nginx container. Ex: your first result from curl might be from Site A, the next from Site B, the third back to Site A, and so on randomly.
The problem is not restricted to services of type: node; we've tested giving proxy settings to other services and experienced the same results. Nor is it restricted to resolving appserver_nginx; rather, it seems trying to curl any service that you have multiple instances of running (for example, two different apps served by Apache) will create the round robin-ing.
Based on this, I'm guessing this is probably caused by the way we set labels on the Docker containers to tell Traeffik how to setup the proxy URLs.
Note that we found this through a user trying to implement the guide on setting up BrowserSync. That may indicate that this is a new-ish issue, or it may simply indicate that most people don't experience this conflict because they didn't have two apps running with appserver_nginx containers.
The text was updated successfully, but these errors were encountered:
For an example app...
If you ssh into the
node
service and try tocurl -L appserver_nginx
, you'll see results from ALL apps you're running with anappserver_nginx
container. Ex: your first result fromcurl
might be from Site A, the next from Site B, the third back to Site A, and so on randomly.The problem is not restricted to services of
type: node
; we've tested givingproxy
settings to other services and experienced the same results. Nor is it restricted to resolvingappserver_nginx
; rather, it seems trying tocurl
any service that you have multiple instances of running (for example, two different apps served by Apache) will create the round robin-ing.Based on this, I'm guessing this is probably caused by the way we set labels on the Docker containers to tell Traeffik how to setup the proxy URLs.
Note that we found this through a user trying to implement the guide on setting up BrowserSync. That may indicate that this is a new-ish issue, or it may simply indicate that most people don't experience this conflict because they didn't have two apps running with
appserver_nginx
containers.The text was updated successfully, but these errors were encountered: