Replies: 3 comments 2 replies
-
I reported this as #2056, because the implementation is currently ambiguous/inconsistent. {base_url} has been implemented as {return_from_grafana_url}. But by name, {base_url} should be the user-configurable path to the TeslaMate Web App itself. |
Beta Was this translation helpful? Give feedback.
-
This functionality would probably help a lot of people out, including me. I doubt that I am the only one who wants to reverse proxy Teslamate to a subpath ( |
Beta Was this translation helpful? Give feedback.
-
Same problem here. All icons and non html stuff is lost when working with teslamate app (not grafana) behind a nginx proxy server. |
Beta Was this translation helpful? Give feedback.
-
I was able to get it working in grafana using these settings:
https://grafana.com/docs/grafana/v8.0/administration/configuration/#root_url
https://grafana.com/docs/grafana/v8.0/administration/configuration/#serve_from_sub_path
But Teslamate is generating links based on the root path: ie.
https://mydomain/settings
instead ofhttps://mydomain/mysubpath/settings
(my reverse proxy is forwardinghttps://mydomain/mysubpath/*
to teslamate with my subpath chopped off ie.http://localhost:4000/*
This is slightly related to #1893 I am guessing.
Beta Was this translation helpful? Give feedback.
All reactions