We have Grafana installed on AKS cluster. The Grafana instance is exposed publicly and we also have internal URL for Grafana. The Grafana Traffic comes and hits Application Gateway that has internal IP address of the Grafana ingress as a Backendpool. But this configuration gives 403 unauthorized err…

You can have whatever (nginx, ALB, NLB, API GW, LB, reverse proxy, …) you want in front of Grafan. But Grafana must receive correct request Host header, which is matching domain configured in root_url in grafana.ini. Documentation how to achieve that for some popular reverse proxies: Run Grafana be…

Thanks for your reply! root url is pointing to our internal grafana URL, which seems to be fine, but the requests are being made on the public URL. Can you please provide your email address so that, I can be in touch with you directly?

Sorry, this is community forum: How to use the Grafana forums If you need “email support”, then I would recommend some paid Grafana Lab’s support/service, where you will have included support.

Thank you! We are using Grafana free version and its not Enterprise one. Do you do freelancing?

We tried all permutations and combinations with configuration of Grafana, but the issue still persists. The root_url is configured as the internal URL of Grafana as per grafana.ini file in the pod. But still the issue persists.

[image] raghava28041978: We tried all permutations and combinations with configuration of Grafana How many permutations and combinations is there possible? I think it is really high number.

Not many though :slight_smile: We have annotations section that has cors settings are present: nginx.ingress.kubernetes.io/enable-cors: “true” nginx.ingress.kubernetes.io/cors-allow-origin: “URLs of internet and internal facing entries”. However, in grafana.ini we dont see these cors settings not su…

[image] raghava28041978: nginx.ingress.kubernetes.io/enable-cors: “true” This is not a Grafana config. That’s K8S ingress config. But you don’t face CORS issue, so why you are configuring CORS then?

Thats right.Grafana has ingress and thats how we access it, it does not work with or without CORS. I just mentioned the kind of config we have. Also wile trying to invite users from internet facing portal we got 403 unauthorized error. But this error is persistent.

Let’s think: 1.) How many domains you can have in root_url? 2.) How many domains you need to serve?

Getting Grafana "origin not allowed" error, with 403 in HTTP archive logs

Grafana Configuration

jangaraj March 15, 2024, 6:20pm 9

This is not a Grafana config. That’s K8S ingress config. But you don’t face CORS issue, so why you are configuring CORS then?

Topic		Replies	Views
How to allow Access-Control-Allow-Origin: * for all the apis General	14	56089	May 30, 2020
Getting 403 Origin Not Allowed when logging in behind Azure Application Gateway Configuration azure	5	1344	March 19, 2025
Facing issue while Configuring Grafana behind a reverse proxy Configuration nginx , reverse-proxy	9	17211	December 26, 2023
Setup CORS policy for grafana Configuration	5	5626	December 11, 2024
Getting 403 Origin Not Allowed when logging in behind Azure Application Gateway while adding dashboard sources Configuration	1	669	December 24, 2023

Getting Grafana "origin not allowed" error, with 403 in HTTP archive logs

Related topics