search

hassio-addons / addon-grafana

Grafana - Home Assistant Community Add-ons
https://addons.community
MIT License
220 stars 61 forks source link

not able to create InfluxDB data source - origin not allowed #263

Closed sql-aus-hh closed 2 years ago

sql-aus-hh commented 2 years ago

Problem/Motivation

I used Grafana as a separat docker container before, which worked great, but then i found this add-on and stopped my container. The only configuration I did was the mentioned ones in the documentations.

certfile: fullchain.pem
env_vars:
  - name: GF_AUTH_DISBALE_LOGIN_FORM
    value: 'true'
  - name: GF_AUTH_ANONYMOUS_ENABLED
    value: 'true'
  - name: GF_AUTH_ANONYMOUS_ORG_ROLE
    value: Admin
  - name: GF_SECURITY_ALLOW_EMBEDDING
    value: 'true'
keyfile: privkey.pem
plugins: []
ssl: true

But unfortunatley I am not able to add a data source "InfluxDB" with error message "Origin not allowed".

Expected behavior

Adding a normal "InfluxDB" data source

Actual behavior

error message - Origin not allowed image

Steps to reproduce

Proposed changes

Actually i don't know how to workaround, but there seems to be some new security features in the latest grafana version which causes these problems. https://community.grafana.com/t/origin-not-allowed-messages-after-upgrade-to-8-3-6/60550/12

TheDK commented 2 years ago

Which browser are you using and have you tried a different one? I am seeing the same error in a different context: https://github.com/hassio-addons/addon-grafana/issues/255

For me it's just with FireFox, using Chrome everythings fine, but might be a different problem connected to the OS (Win10) as it works just fine on FireFox on WinServer - might also be an installation / config issue on the client OS.

github-actions[bot] commented 2 years ago

There hasn't been any activity on this issue recently, so we clean up some of the older and inactive issues. Please make sure to update to the latest version and check if that solves the issue. Let us know if that works for you by leaving a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thanks!

TheDK commented 2 years ago

Problem still persists.

github-actions[bot] commented 2 years ago

There hasn't been any activity on this issue recently, so we clean up some of the older and inactive issues. Please make sure to update to the latest version and check if that solves the issue. Let us know if that works for you by leaving a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thanks!