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

--web.external-url breaks healthcheck to localhost #4163

Closed
nazarewk opened this Issue May 15, 2018 · 6 comments

Comments

Projects
None yet
3 participants
@nazarewk
Copy link

nazarewk commented May 15, 2018

I am pretty sure this is exactly the same as prometheus/alertmanager#1382

@nazarewk nazarewk changed the title --web.exernal-url breaks healthcheck to localhost --web.external-url breaks healthcheck to localhost May 15, 2018

@anthraxn8b

This comment has been minimized.

Copy link

anthraxn8b commented May 22, 2018

This is interesting. In my case prometheus (2.2.1) healthcheck seems to work fine on localhost even if an external-url is set.
Du you use vanilla containers or do you build your own ones?

@nazarewk

This comment has been minimized.

Copy link
Author

nazarewk commented May 23, 2018

I'm using stable/prometheus with as little changes as possible (so yeah, vanilla containers)

@anthraxn8b

This comment has been minimized.

Copy link

anthraxn8b commented Jun 1, 2018

@nazarewk, could you please try to set --web.external-url=https://yourDomain/yourPathPrefix --web.route-prefix=/ to enforce the route prefix not to be inherited by the web external url?
Also alter your healthcheck to point to wget --quiet --spider http://localhost:9090/graph to avoid being redirected to yourPathPrefix (this happens to serve the external url correctly - as far as it looks like the original request path is no longer taken into account if the web external url is set).
Please tell me if it worked! THX!

@brian-brazil

This comment has been minimized.

Copy link
Member

brian-brazil commented Jun 13, 2018

This looks like a misunderstanding of how --web.external-url works so it makes more sense to ask questions like this on the prometheus-users mailing list rather than in a GitHub issue. On the mailing list, more people are available to potentially respond to your question, and the whole community can benefit from the answers provided.

@anthraxn8b

This comment has been minimized.

Copy link

anthraxn8b commented Jun 13, 2018

@brian-brazil, you are right, but this means you have to create another account on another platform - and if you believe in an issue this would be the right place ;-)

@lock

This comment has been minimized.

Copy link

lock bot commented Mar 22, 2019

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

@lock lock bot locked and limited conversation to collaborators Mar 22, 2019

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
You can’t perform that action at this time.