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

[frontend-proxy] No healthy upstream #1935

Open
rogercoll opened this issue Jan 22, 2025 · 2 comments · May be fixed by #1936
Open

[frontend-proxy] No healthy upstream #1935

rogercoll opened this issue Jan 22, 2025 · 2 comments · May be fixed by #1936
Labels
bug Something isn't working

Comments

@rogercoll
Copy link
Contributor

Bug Report

Which version of the demo you are using? afbc808

$ curl http://127.0.0.1:8080
no healthy upstream%

Symptom

Using older versions of envoy (<1.32-latest) does not produce this issue: 3c763db#diff-2f30c32fefb10725d234937a6a1dbc0a67d40329d926db35aec09bbc3ebacc57L4

Reproduce

In a Linux machine, make start

Additional Context

Trying to find the root cause
@rogercoll rogercoll added the bug Something isn't working label Jan 22, 2025
This was referenced Jan 22, 2025
Open
Open
@mviitane
Copy link
Member

Weird. I can't reproduce in my environment.

$ curl http://127.0.0.1:8080
<!DOCTYPE html><html><head><meta charSet="utf-8"/><meta name="viewport" content="width...

@rogercoll
Copy link
Contributor Author

Weird. I can't reproduce in my environment.

$ curl http://127.0.0.1:8080
<!DOCTYPE html><html><head><meta charSet="utf-8"/><meta name="viewport" content="width...

Agree, it only happens in some environments and since envoy 1.32 (same with new 1.33 version). It seems that is related with how envoy uses the DNS resolver within Docker, the fix disables using the "host" one.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug Something isn't working
Projects
None yet
Milestone
No milestone
2 participants
@rogercoll @mviitane