Issues with Grafana v7.5.17: "If you're seeing this Grafana has failed to load its application files"

Grafana
1

Hello everyone,

I’m currently experiencing an issue with Grafana Open Source version 7.5.17 on my server. Whenever I attempt to open the visualization, I encounter the following error across multiple browsers (Edge, Firefox, Chrome), but I want to use Edge, both with HTTP and HTTPS protocols:

If you’re seeing this Grafana has failed to load its application files

The error message suggests several potential causes:

1. This could be caused by your reverse proxy settings.

2. If you host grafana under subpath make sure your grafana.ini root_url setting includes subpath. If not using a reverse proxy make sure to set serve_from_sub_path to true.

3. If you have a local dev build make sure you build frontend using: yarn start, yarn start:hot, or yarn build

4. Sometimes restarting grafana-server can help

5. Check if you are using a non-supported browser. For more information, refer to the list of supported browsers.

Has anyone else encountered this issue? Could you provide guidance on how to resolve it? Any suggestions or troubleshooting steps would be greatly appreciated.

Thank you!

2

I get this message usually when i have moved grafana to a different folder path or sub path, or i am trying to proxy grafana using a different folder, the settings to tweak to see if you can get it working are in the grafana.ini:

it’s usually a combination of root_url, serve_from_sub_path etc.

also if you are using nginx or apache etc. to proxy grafana on a sub folder or custom location, i had to do a rewrite like this:

rewrite ^/grafana/(.*) /$1 break;

3

Also checks your disk space
df -h

Could be that your system has not enough space on the disk and that causes that nginx cant buffer the js that grafana is trying to retrieve. Just remove some files to get more space or increase your main volume. You can check it if you go to your browser, open dev-tools and check if you got a partial retrive of the json. (it is indicated on the error code or if you call that file using curl it will pop a message saying that there are more bytes that can not be retrieved)