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
I was unable to get the proxy pass working with my app container until I added the service to my existing docker-compose.yml and specified the app service name as the UPSTREAM: target (where target is the name of the docker container that is running the proxied app. Not 127.0.0.1, the local IP, LAN IP, nor even the docker IP that is randomly generated worked. Perhaps the network needs to be specified in the docker-compose.yml service description, perhaps there is some other nuance. None of this is documented.
The error I was getting was 502: Bad gateway
Docker logs on app were empty, logs on proxy read something like (I have obscured actual domains):
I was unable to get the proxy pass working with my app container until I added the service to my existing docker-compose.yml and specified the app service name as the
UPSTREAM: target
(wheretarget
is the name of the docker container that is running the proxied app. Not 127.0.0.1, the local IP, LAN IP, nor even the docker IP that is randomly generated worked. Perhaps the network needs to be specified in the docker-compose.yml service description, perhaps there is some other nuance. None of this is documented.The error I was getting was 502: Bad gateway
Docker logs on app were empty, logs on proxy read something like (I have obscured actual domains):
The text was updated successfully, but these errors were encountered: