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
However, the data container is configured to listen (on the Docker network) on port 80, not 8080. That is implicit as we are not overriding its default configuration:
As a result, when trying to do a bulk download locally, the web container reports this error:
connect() failed (111: Connection refused) while connecting to upstream, [...], upstream: "http://172.21.0.2:8080/[...]
Task
The task here is to reconcile the two port numbers: either have the web container proxy to port 80, or have the data container listen on port 8080. Please keep in mind how changes made here will impact our production and development environments on Spin.
The Nginx server running on the
web
container is configured to proxy requests to port 8080 of thedata
container, as shown here:nmdc-server/web/nginx.conf.template
Lines 37 to 40 in c0c7f14
However, the
data
container is configured to listen (on the Docker network) on port 80, not 8080. That is implicit as we are not overriding its default configuration:nmdc-server/docker-compose.yml
Lines 5 to 8 in c0c7f14
As a result, when trying to do a bulk download locally, the
web
container reports this error:Task
The task here is to reconcile the two port numbers: either have the
web
container proxy to port 80, or have thedata
container listen on port 8080. Please keep in mind how changes made here will impact our production and development environments on Spin.Related
This is related to a longstanding issue of some networking-related information being hard-coded in the
nmdc-server
repo.I first noticed this issue while working on #1536.
The text was updated successfully, but these errors were encountered: