Grafana “origin not allowed” after 11.0.0 update

Configuration Frontend
,
1

I have updated Grafana from version 10.5.0 to 11.0.0. When I now access Grafana via port 3000 and am logged in, no graphics are displayed. The error message “origin not allowed” appears at the top left of the graphics window. When I log out and call up the page again, no error occurs and the graphics are displayed.

I have now imported a backup of Grafana with the old version 10.5.0 and everything works perfectly.
What do I have to do after the update to 11.0.0 so that the error does not occur? Many thanks for your support!

2

Hello same problem here. don’t make the rollback if we can test something.

3

Update: Seems to work after clear cache and cookies of my browser

4

Same problem here. Clear cache and cookies didn’t work for me. Any other options?

5

Same problem for me as well. If I log out on all sessions via port 3000 and go via the web-ui of the add-on (so via port 8123) it works. Done already many suggestions as provided by ChatGPT but no luck so far. Would be great to have a working solution!

6

Same Problem here.

7

Ok i reproduce the problem only when i was logged in. When i was not logged no problem. same as @misko finally

8

There’s an issue opened Grafana does no longer accept logins but from within the UI · Issue #467 · hassio-addons/addon-grafana · GitHub

1 Like
9

As workaround we can add this to env_var. It work here.

- name: GF_SECURITY_CSRF_TRUSTED_ORIGINS
  value: <example.com>
10

In which file exactly do these variables have to be stored?

11

This is not working for me:

- name: GF_SECURITY_CSRF_TRUSTED_ORIGINS
  value: <example.com>

I still have this problem on latest grafana addon? Is there any solution?

12

the value <example.com> must be adapted to your use case. in my case i have local DNS resolution and don’t expose home assistant and grafana on internet. I’ve just inserted the local dns entry of home assistant instead of <example.com>

13

look into env_vars in the grafana add-on configuration

14

My Grafana add-on stopped working with the “origin not allowed” error, but I was able to fix the problem by adding the following to the env_vars section of the Grafana add-on configuration:

- name: GF_SECURITY_CSRF_TRUSTED_ORIGINS
  value: xxx.xxx.xxx.xxx

where value is the local IP address of my HA instance. I only access Grafana locally on my home network.
Thanks to everyone in this thread for the information required to sort this.

15

Not working for me. :frowning:

My fault, now it’s working.
Fixed it for me:

  • name: GF_SECURITY_CSRF_TRUSTED_ORIGINS
    value: homeassistant.lan
16

This did the trick for me. I use a reverse proxy, and fixed it by both setting the HA instance IP address in this variable, and the external domain I’m using. Now it works both internally, and through the proxy. Thanks!

1 Like
17

Any news here? I have the same problem. No access to my influxDB, even if I try to change my language under admin, I get the error “Origin not allowed.” Worked before like a charm.

Bildschirmfoto 2025-06-02 um 11.22.52
Bildschirmfoto 2025-06-02 um 11.22.521004×448 47.1 KB

Is this the right position, for the fix?

Bildschirmfoto 2025-06-02 um 11.27.02
Bildschirmfoto 2025-06-02 um 11.27.021074×662 34.8 KB

18

How did you use 2 domains? I’ve tried to add 2 seperated by comma but only one works

- name: GF_SECURITY_CSRF_TRUSTED_ORIGINS
  value: home.lan, monitor.home.lan