-
Notifications
You must be signed in to change notification settings - Fork 155
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
[3.11.1] Error rendering template: error. You may need to build frontend assets #546
Comments
Duplicate of #545 |
Hi @koelle25 , Did you try the same?
|
I had this problem as I used a very outdated version of the grafana-image-renderer on the latest Grafana 11.3 release. Issuing |
What happened:
Tried the simple docker file here: https://github.com/grafana/grafana-image-renderer/blob/master/devenv/docker/simple/docker-compose.yaml
I could started two containers successfully, but got error when I clicked "Direct link rendered image" from Grafana UI(I didn't add any datasource, just use 'Random Walk for Grafana' for Grafana builtin data source), I couldn't be able to get the image.
No error log from the renderer, but had error logs from Grafana:
What you expected to happen:
no error log from Grafana and I can render the image
How to reproduce it (as minimally and precisely as possible):
Anything else we need to know?:
I used the similar config on my production server but I was using systemd to start grafana and render, I got the same errors as described above and additional I got error log from render service:
Failed to get browser version
my service file:
[Service]
Environment=BROWSER_TZ=Europe/Stockholm
Environment=ENABLE_METRICS=true
Environment=HTTP_HOST=0.0.0.0
Environment=HTTP_PORT=3010
Environment=RENDERING_CLUSTERING_MAX_CONCURRENCY=3
Environment=RENDERING_CLUSTERING_MODE=browser
Environment=RENDERING_MODE=clustered
Environment=RENDERING_DUMPIO=true
Environment=LOG_LEVEL=debug
ExecStart=/opt/grafana-image-renderer-3.11.1/grafana-image-renderer-3.11.1 server
Environment: (just for my production server)
The text was updated successfully, but these errors were encountered: