# \[SOLVED\] Ftldns erratic graphs in dashboard

**URL:** <https://discourse.pi-hole.net/t/solved-ftldns-erratic-graphs-in-dashboard/8709>\
**Category:** Help\
**Tags:** ftldns-beta\
**Created:** [April 8, 2018, 9:50am UTC](https://discourse.pi-hole.net/t/solved-ftldns-erratic-graphs-in-dashboard/8709 "2018-04-08T09:50:37Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![BenoitSvB](https://discourse-cdn.pi-hole.net/user_avatar/discourse.pi-hole.net/benoitsvb/32/941_2.png) [@BenoitSvB](https://discourse.pi-hole.net/u/BenoitSvB)\
**Post date:** [April 8, 2018, 9:50am UTC](https://discourse.pi-hole.net/t/solved-ftldns-erratic-graphs-in-dashboard/8709/1 "2018-04-08T09:50:38Z")

</div>

#### Please follow the below template, it will help us to help you!

## Expected Behaviour:

_nice graphs in dashboard_

## Actual Behaviour:

_some failed graphs_

 ![Screenshot_20180408-115004](https://discourse.pi-hole.net/uploads/default/original/2X/a/a02679a1b724bf5c876a64a5a7a0b9f47c93dc14.png)

## Debug Token:

_f1n30sy8sq_

---

<div class="post-metadata">

**Author:** ![DL6ER](https://discourse-cdn.pi-hole.net/user_avatar/discourse.pi-hole.net/dl6er/32/281_2.png) [@DL6ER](https://discourse.pi-hole.net/u/DL6ER)\
**Post date:** [April 8, 2018, 9:57am UTC](https://discourse.pi-hole.net/t/solved-ftldns-erratic-graphs-in-dashboard/8709/2 "2018-04-08T09:57:37Z")

</div>

I'd bet it is the typical problem of browser cache ... Please try `Ctrl + F5` as is advised to be run after each update. Not sure how you can do it o Android, but I hope there is an option for flushing the cache. Otherwise, maybe a reboot of the device helps.

---

<div class="post-metadata">

**Author:** ![BenoitSvB](https://discourse-cdn.pi-hole.net/user_avatar/discourse.pi-hole.net/benoitsvb/32/941_2.png) [@BenoitSvB](https://discourse.pi-hole.net/u/BenoitSvB)\
**Post date:** [April 8, 2018, 10:11am UTC](https://discourse.pi-hole.net/t/solved-ftldns-erratic-graphs-in-dashboard/8709/3 "2018-04-08T10:11:26Z")

</div>

Clearing the browsercache solved it! Thank you.

 ![Screenshot_20180408-120743](https://discourse.pi-hole.net/uploads/default/original/2X/c/ca1f2eac8c4a02d7118a3cb4e40bbad72f423cf9.png)

---

<div class="post-metadata">

**Author:** ![jacob.salmela](https://discourse-cdn.pi-hole.net/user_avatar/discourse.pi-hole.net/jacob.salmela/32/8_2.png) [@jacob.salmela](https://discourse.pi-hole.net/u/jacob.salmela)\
**Post date:** [April 8, 2018, 11:06am UTC](https://discourse.pi-hole.net/t/solved-ftldns-erratic-graphs-in-dashboard/8709/4 "2018-04-08T11:06:51Z")

</div>

> [@Why doesn't my Web interface load stats?](https://discourse.pi-hole.net/t/why-doesnt-my-web-interface-load-stats/7284):
>
> We often see users with broken Web interfaces after updating Pi-hole but it has also appeared during regular usage. The symptoms include: the Web interface has endless spinning indicators the Web interface looks distorted the query log is stuck on Processing none of the Web interface stats load The solution in most cases is to [flush your Web browser's cache](http://www.refreshyourcache.com/en/home/) or service pihole-FTL restart [bc732d4a5ff67fa5e11aa4e840c9631774ce8646\_1\_690x408]

---

<div class="post-metadata">

**Author:** ![BenoitSvB](https://discourse-cdn.pi-hole.net/user_avatar/discourse.pi-hole.net/benoitsvb/32/941_2.png) [@BenoitSvB](https://discourse.pi-hole.net/u/BenoitSvB)\
**Post date:** [April 8, 2018, 11:43am UTC](https://discourse.pi-hole.net/t/solved-ftldns-erratic-graphs-in-dashboard/8709/5 "2018-04-08T11:43:37Z")

</div>

systemctl restart pihole-FTL.service did not solve this issue, but clearing the browsercache did.

---

<div class="post-metadata">

**Author:** ![system](https://discourse.pi-hole.net/uploads/default/original/3X/7/c/7c8792f649eeb921c5d2b4c41564ffa873d9a2b8.png) [@system](https://discourse.pi-hole.net/u/system)\
**Post date:** [April 29, 2018, 11:43am UTC](https://discourse.pi-hole.net/t/solved-ftldns-erratic-graphs-in-dashboard/8709/6 "2018-04-29T11:43:39Z")

</div>

This topic was automatically closed 21 days after the last reply. New replies are no longer allowed.