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.

Sign up for GitHub

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

Jump to bottom

Reverse-proxy to 127.0.0.1 #220

Merged
merged 1 commit into from Sep 6, 2018
Merged

Reverse-proxy to 127.0.0.1 #220

merged 1 commit into from Sep 6, 2018

Conversation

ikapelyukhin
Copy link
Contributor

@ikapelyukhin ikapelyukhin commented Sep 5, 2018 •
edited

The backend doesn't listen on ::1, nginx will try both IPv4 and IPv6 addresses and produce error messages for the IPv6 address if the hosts file contains both:

127.0.0.1	localhost
::1             localhost

2018/09/04 14:49:29 [error] 26743#26743: *4 connect() failed (111: Connection refused) while connecting to upstream, client: 111.111.111.111, server: rmt, request: "POST /connect/systems/products HTTP/1.1", upstream: "http://[::1]:4224/connect/systems/products", host: "example.com"

@ikapelyukhin
Reverse-proxy to 127.0.0.1
2fed8c7 
The backend doesn't listen on ::1, nginx will try both IPv4 and IPv6 addresses and produce error messages for the IPv6 address.
Sergeykot
Sergeykot approved these changes Sep 6, 2018
View reviewed changes
Copy link
Contributor

@Sergeykot Sergeykot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM 👍

@ikapelyukhin ikapelyukhin merged commit e4c940e into master Sep 6, 2018
@ikapelyukhin ikapelyukhin deleted the nginx_use_127_0_0_1 branch September 6, 2018 13:21
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@Sergeykot Sergeykot Sergeykot approved these changes

Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.

None yet
2 participants
@ikapelyukhin @Sergeykot