Join GitHub today
GitHub is home to over 31 million developers working together to host and review code, manage projects, and build software together.
Sign upLinks to /route-prefix/api/ but only responds on /api/ #3083
Comments
This comment has been minimized.
This comment has been minimized.
|
Aside: I could change my proxy to strip off the prefix when proxying. However, the static assets (e.g. javascript) are served under the
|
This comment has been minimized.
This comment has been minimized.
|
This suggests a nasty proxy workaround which does appear to work!
|
This comment has been minimized.
This comment has been minimized.
|
@candlerb do you know if it worked in version 1.x? I'll try to take a look tonight or tomorrow. |
This comment has been minimized.
This comment has been minimized.
Sorry I don't, I have only been working with 2.0 beta. |
brian-brazil
added
component/ui
dev-2.0
help wanted
kind/bug
labels
Aug 21, 2017
krasi-georgiev
referenced this issue
Sep 4, 2017
Merged
fixes #3083 - api ignores prefix option - when binary started with custom web.external-url #3137
fabxc
added a commit
that referenced
this issue
Sep 18, 2017
This comment has been minimized.
This comment has been minimized.
williamstein
commented
Sep 21, 2017
|
For what it is worth, I just hit this issue with the 2.0 beta, found it here, then build the dev-2.0 branch from source (the merged PR mentioned above), and it fixed the problem. |
This comment has been minimized.
This comment has been minimized.
|
Thanks. I will install 2.0.0-beta5, released 2 minutes ago :-) |
This comment has been minimized.
This comment has been minimized.
|
Looks good - thank you! |
This comment has been minimized.
This comment has been minimized.
|
Closed in #3137 |
gouthamve
closed this
Sep 28, 2017
This comment has been minimized.
This comment has been minimized.
lock
bot
commented
Mar 23, 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. |
candlerb commentedAug 16, 2017
What did you do?
Run prometheus with these flags:
and behind an Apache reverse proxy
Opened the page at https://example.com/prometheus/graph
What did you expect to see?
Usual prometheus front page
What did you see instead? Under which circumstances?
Usual prometheus front page but with red box: "Error loading available metrics!"
Opening the Javascript console showed that it got a 404 error trying to access
https://example.com/prometheus/api/v1/label/__name__/values?_=1502894473124
Testing this directly from the proxy:
BUT:
So it appears that the api endpoint doesn't honour the route-prefix.
Environment
System information:
Linux 4.4.0-87-generic x86_64
Prometheus version:
Alertmanager version:
n/a
Prometheus configuration file:
default
Alertmanager configuration file:
n/a
Logs:
n/a