You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I’m experiencing an issue with the Bitnami Grafana Helm Chart (part of kube-prometheus-stack version 67.9.0) where the redirect_uri is being set to http://<domain>:3000/ instead of the expected value using HTTPS. This is causing problems with OAuth integration (e.g., GitHub login). I attempted to override this by setting the GF_SERVER_ROOT_URL environment variable using extraEnvVars in the values.yaml configuration, as follows:
However, this environment variable does not appear in the Grafana container when inspecting with printenv, and the issue with the redirect_uri persists. It seems the extraEnvVars configuration is not being applied correctly. Could you confirm if this is a bug or if additional steps are required to configure the root_url properly through the Helm Chart?
What do you see instead?
http://<domain>:3000/ instead of the expected value using HTTPS without :3000 port
Additional information
kube-prometheus-stack-67.9.0
The text was updated successfully, but these errors were encountered:
Name and Version
bitnami/grafana latest
What architecture are you using?
amd64
What steps will reproduce the bug?
I’m experiencing an issue with the Bitnami Grafana Helm Chart (part of kube-prometheus-stack version 67.9.0) where the
redirect_uri
is being set tohttp://<domain>:3000/
instead of the expected value using HTTPS. This is causing problems with OAuth integration (e.g., GitHub login). I attempted to override this by setting theGF_SERVER_ROOT_URL
environment variable usingextraEnvVars
in the values.yaml configuration, as follows:However, this environment variable does not appear in the Grafana container when inspecting with printenv, and the issue with the redirect_uri persists. It seems the extraEnvVars configuration is not being applied correctly. Could you confirm if this is a bug or if additional steps are required to configure the root_url properly through the Helm Chart?
What do you see instead?
http://<domain>:3000/
instead of the expected value using HTTPS without:3000
portAdditional information
kube-prometheus-stack-67.9.0
The text was updated successfully, but these errors were encountered: