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

No Support for Reverse Proxy? #31

Open
junglesub opened this issue Dec 1, 2024 · 1 comment
Open

No Support for Reverse Proxy? #31

junglesub opened this issue Dec 1, 2024 · 1 comment

Comments

@junglesub
Copy link

Description

The container works perfectly when accessed directly via localhost, but when routed through my Nginx reverse proxy, the connection seems to be denied. I suspect the issue lies in how the container handles requests when proxied.

Steps to Reproduce

Run the container using the provided docker-compose.yml (with exposed port 8899).
Configure Nginx as a reverse proxy to route traffic to the container.
Attempt to access the service through the Nginx proxy URL.
Observe the connection issue (denied or not reachable).
Expected Behavior
The service should respond seamlessly through the Nginx proxy, just as it does when accessed via localhost.

Actual Behavior

The service fails to respond when accessed via the reverse proxy. Error logs suggest the connection is being denied or improperly forwarded.

Log

2024/12/01 03:29:33 [error] 14050#14050: *1427985 connect() failed (111: Connection refused) while connecting to upstream, client: ***, server: cors.***.com, request: "GET / HTTP/1.1", upstream: "http://127.0.0.1:8899/", host: "cors.***.com"

While accessing via localhost works fine

image

@junglesub
Copy link
Author

Digging in more, I think it is my setup issue. I will do more investigation.

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