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

grafana: redirect_uri uses :3000 despite configuring GF_SERVER_ROOT_URL via extraEnvVars #31296

Open
apoca opened this issue Jan 10, 2025 · 0 comments
Assignees
Labels
grafana in-progress tech-issues The user has a technical issue about an application

Comments

@apoca
Copy link

apoca commented Jan 10, 2025

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 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:

grafana:
  extraEnvVars:
    - name: GF_SERVER_ROOT_URL
      value: https://grafana.mydomain.com/

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

@apoca apoca added the tech-issues The user has a technical issue about an application label Jan 10, 2025
@github-actions github-actions bot added the triage Triage is needed label Jan 10, 2025
@github-actions github-actions bot removed the triage Triage is needed label Jan 10, 2025
@github-actions github-actions bot assigned migruiz4 and unassigned javsalgar Jan 10, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
grafana in-progress tech-issues The user has a technical issue about an application
Projects
None yet
Development

No branches or pull requests

4 participants