Replies: 1 comment 8 replies
-
As per the Grafana documentation it requires the server root url variable set to serve from a subpath. This is set to a known value to ensure ingress functions, which probably won't be overwritten. If you want to proxy to it, I would suggest using a different name (i.e. grafana.somedomain.com), so you don't have this issue, or run your own version somewhere with configuration you can fully control. |
Beta Was this translation helpful? Give feedback.
8 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Help, I've read numerous posts, forum and official doc and cannot get the addon to behave like the Grafana documentation
Problem/Motivation
I want to be able to share Dashboard and iPanels within my LAN and from outside.
Expected behavior
If I browse to mydomain.net/grafana or 192.168.1.1:3000, should be redirected to Grafana
Actual behavior
For some reason, I always get "If you're seeing this Grafana has failed to load its application files" when trying to reverse proxy Grafana.
Steps to reproduce
I have the add-on installed in HomeAssistant.
Add-on version: 7.4.0
You are running the latest version of this add-on.
System: Home Assistant OS 7.1 (amd64 / qemux86-64)
Home Assistant Core: 2021.12.10
Home Assistant Supervisor: 2021.12.2
When I browse to : mydomain.net/grafana , I get redirected to mydomain.net/api/hassio_ingress/ with the message "If you're seeing this Grafana has failed to load its application files"
Same behavior if I browse 192.168.1.1:3000
Grafana configuration :
And my NGINX config :
Beta Was this translation helpful? Give feedback.
All reactions