Unable to load "panic: page load error net::ERR_BLOCKED_BY_CLIENT

[krispayne]

Starting this morning, I am unable to load my grafana dashboard via the kiosk. I did recently update grafana yesterday, but it worked fine after that. I did notice this morning on my kiosk that raspberry pi OS was asking about labwc, but I got through all of that (at least I think) and am still using X11.

The URL works fine when I go to it in Chromium via the GUI, and other URLs work when launched via grafana-kiosk. I have no idea what I am doing wrong with this specific URL.

GrafanaKiosk Version: v1.0.7 (same problem on v1.0.8)

Raspberry Pi 4

pi@weatherdisplay:~ $ lsb_release -a
No LSB modules are available.
Distributor ID: Raspbian
Description:    Raspbian GNU/Linux 12 (bookworm)
Release:        12
Codename:       bookworm
pi@weatherdisplay:~ $

config.yml:

general:
  kiosk-mode: full
  autofit: true

target:
  login-method: local
  username: guest
  password: guest
  playlist: false
  URL: http://redacted:3000/d/acf9bcbf-e0be-43bf-a3e2-d02ee9f4182d/tempest-weather-display?orgId=1&from=now-6h&to=now&refresh=10s

pi@weatherdisplay:~ $ grafana-kiosk -c grafana-kiosk.yml
GrafanaKiosk Version: v1.0.7
2024/11/29 14:34:26 Using config from grafana-kiosk.yml
2024/11/29 14:34:26 AutoFit: true
2024/11/29 14:34:26 LXDEEnabled: false
2024/11/29 14:34:26 LXDEHome: /home/pi
2024/11/29 14:34:26 Mode: full
2024/11/29 14:34:26 WindowPosition: 0,0
2024/11/29 14:34:26 WindowSize:
2024/11/29 14:34:26 ScaleFactor: 1.0
2024/11/29 14:34:26 URL: http://redacted:3000/d/acf9bcbf-e0be-43bf-a3e2-d02ee9f4182d/tempest-weather-display?orgId=1&from=now-6h&to=now&refresh=10s
2024/11/29 14:34:26 LoginMethod: local
2024/11/29 14:34:26 Username: guest
2024/11/29 14:34:26 Password: *redacted*
2024/11/29 14:34:26 IgnoreCertificateErrors: false
2024/11/29 14:34:26 IsPlayList: false
2024/11/29 14:34:26 UseMFA: false
2024/11/29 14:34:26 Fieldname AutoLogin: false
2024/11/29 14:34:26 Fieldname Username:
2024/11/29 14:34:26 Fieldname Password:
2024/11/29 14:34:26 DISPLAY not set, autosetting to :0.0
2024/11/29 14:34:26 DISPLAY= :0.0
2024/11/29 14:34:26 XAUTHORITY not set, autosetting
2024/11/29 14:34:26 XAUTHORITY= /home/pi/.Xauthority
2024/11/29 14:34:26 method  local
2024/11/29 14:34:26 Launching local login kiosk
2024/11/29 14:34:26 Using temp dir: /tmp/chromedp-kiosk3090273426
2024/11/29 14:34:29 KioskMode: Fullscreen
2024/11/29 14:34:29 Navigating to  http://redacted:3000/d/acf9bcbf-e0be-43bf-a3e2-d02ee9f4182d/tempest-weather-display?from=now-6h&kiosk=1&orgId=1&refresh=10s&to=now&autofitpanels
2024/11/29 14:34:29 Sleeping 2000 MS before navigating to url
panic: page load error net::ERR_BLOCKED_BY_CLIENT

goroutine 1 [running]:
github.com/grafana/grafana-kiosk/pkg/kiosk.GrafanaKioskLocal(0x400015de00, 0x400011c360)
        /home/runner/work/grafana-kiosk/grafana-kiosk/pkg/kiosk/local_login.go:79 +0xd30
main.main()
        /home/runner/work/grafana-kiosk/grafana-kiosk/pkg/cmd/grafana-kiosk/main.go:223 +0xa04
pi@weatherdisplay:~ $

[krispayne]

This appears to be because I'm not running grafana behind https. Any https website I put in my config works fine, it is only http that has an issue.

[pconwell]

I'm running into this exact issue. I have old installs running v1.0.5 just fine. Upgraded a new install to v1.0.8 and now I am getting this error.

The changelogs do not document this change as far as I can find.

Is there a workaround or flag to allow http?

---

EDIT:
After a little more testing, this does not appear to be from grafana-kiosk, but possibly (?) from chromium. Installing v1.0.5 is giving the same error.

---

EDIT2:
Using debian bookworm with chromium 130.0.6723.116 did not work - regardless of grafana-kiosk version used.

However, rolling back to debian bullseye with chromium 126.0.6478.164 works, including with kiosk version v1.0.8.

I think this confirms that the issue is somewhere between chromium 126 and chromium 130.

[briangann]

will check for chromedp changes, it should work with both by default. chromium likely has a new default that needs to be overridden.

[pconwell]

@briangann for what it's worth, I spent a while trying to dig into this today but didn't make any real progress.

The closest issue I found that seems to be in the same family of problems is this: chromedp/chromedp#1525. It may not be related at all, but almost everything else I found related to ERR_BLOCKED_BY_CLIENT involved having an ad blocker installed - which does not apply here.

[briangann]

still chasing this one, it doesn't do this on chromium on darwin, but will try with a pi.