Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Nginx on web container proxies to incorrect port on data container in local development environment #1538

Open
eecavanna opened this issue Feb 7, 2025 · 0 comments

Comments

@eecavanna
Copy link
Collaborator

eecavanna commented Feb 7, 2025

The Nginx server running on the web container is configured to proxy requests to port 8080 of the data container, as shown here:

location /data/ {
proxy_pass http://data:8080/;
proxy_buffering off;
}

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:

data:
image: nginx

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.

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant