Grafana Interface not working after upgrade
trexman
60 Posts
April 24, 2020, 4:10 pmQuote from trexman on April 24, 2020, 4:10 pmHi,
we are using the Grafana Interface as you explained here: http://www.petasan.org/forums/?view=thread&id=522
But after the (online) Upgrade from 2.3.1 to 2.5.2 we get the following message if we access http://stats-server-ip:3000
If you're seeing this Grafana has failed to load its application files
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
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
Side note: The graph on the dashboard is working...
Is this just a problem on our server, or is grafana in PetaSAN 2.5.2 not usable anymore?
Thanks for you help
PS: Restart of the service grafana-server did not solve the problem.
Hi,
we are using the Grafana Interface as you explained here: http://www.petasan.org/forums/?view=thread&id=522
But after the (online) Upgrade from 2.3.1 to 2.5.2 we get the following message if we access http://stats-server-ip:3000
If you're seeing this Grafana has failed to load its application files
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
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
Side note: The graph on the dashboard is working...
Is this just a problem on our server, or is grafana in PetaSAN 2.5.2 not usable anymore?
Thanks for you help
PS: Restart of the service grafana-server did not solve the problem.
Last edited on April 24, 2020, 4:15 pm by trexman · #1
admin
2,930 Posts
April 24, 2020, 6:52 pmQuote from admin on April 24, 2020, 6:52 pmYes with 2.5, we use https and we reverse proxy, this allows accessing charts in secure way even when routed externally.
it does work on the PetaSAN dashboard, to access grafana direcly can you try:
https://ip-of-any-management-node/grafana
Yes with 2.5, we use https and we reverse proxy, this allows accessing charts in secure way even when routed externally.
it does work on the PetaSAN dashboard, to access grafana direcly can you try:
https://ip-of-any-management-node/grafana
Last edited on April 24, 2020, 6:53 pm by admin · #2
trexman
60 Posts
April 27, 2020, 3:07 pmQuote from trexman on April 27, 2020, 3:07 pmOh cool. Thanks.
Now the Grafana access works like a charm... (form every management node IP)
🙂
Oh cool. Thanks.
Now the Grafana access works like a charm... (form every management node IP)
🙂
Grafana Interface not working after upgrade
trexman
60 Posts
Quote from trexman on April 24, 2020, 4:10 pmHi,
we are using the Grafana Interface as you explained here: http://www.petasan.org/forums/?view=thread&id=522
But after the (online) Upgrade from 2.3.1 to 2.5.2 we get the following message if we access http://stats-server-ip:3000
If you're seeing this Grafana has failed to load its application files
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
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
Side note: The graph on the dashboard is working...
Is this just a problem on our server, or is grafana in PetaSAN 2.5.2 not usable anymore?
Thanks for you help
PS: Restart of the service grafana-server did not solve the problem.
Hi,
we are using the Grafana Interface as you explained here: http://www.petasan.org/forums/?view=thread&id=522
But after the (online) Upgrade from 2.3.1 to 2.5.2 we get the following message if we access http://stats-server-ip:3000
If you're seeing this Grafana has failed to load its application files
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
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
Side note: The graph on the dashboard is working...
Is this just a problem on our server, or is grafana in PetaSAN 2.5.2 not usable anymore?
Thanks for you help
PS: Restart of the service grafana-server did not solve the problem.
admin
2,930 Posts
Quote from admin on April 24, 2020, 6:52 pmYes with 2.5, we use https and we reverse proxy, this allows accessing charts in secure way even when routed externally.
it does work on the PetaSAN dashboard, to access grafana direcly can you try:
https://ip-of-any-management-node/grafana
Yes with 2.5, we use https and we reverse proxy, this allows accessing charts in secure way even when routed externally.
it does work on the PetaSAN dashboard, to access grafana direcly can you try:
https://ip-of-any-management-node/grafana
trexman
60 Posts
Quote from trexman on April 27, 2020, 3:07 pmOh cool. Thanks.
Now the Grafana access works like a charm... (form every management node IP)
🙂
Oh cool. Thanks.
Now the Grafana access works like a charm... (form every management node IP)
🙂