# Pihole Dashboard Keeps Breaking

**URL:** <https://discourse.pi-hole.net/t/pihole-dashboard-keeps-breaking/6095>\
**Category:** Help\
**Created:** [December 22, 2017, 8:18pm UTC](https://discourse.pi-hole.net/t/pihole-dashboard-keeps-breaking/6095 "2017-12-22T20:18:28Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![Alen](https://discourse-cdn.pi-hole.net/user_avatar/discourse.pi-hole.net/alen/32/3237_2.png) [@Alen](https://discourse.pi-hole.net/u/Alen)\
**Post date:** [December 22, 2017, 8:18pm UTC](https://discourse.pi-hole.net/t/pihole-dashboard-keeps-breaking/6095/1 "2017-12-22T20:18:29Z")

</div>

The Dashboard keeps breaking when I try to scroll down, the page goes longer and longer scrolling itself back up. The Graph and the other listings stretch's.

I saw a cmd on fixing it but I don't remember what it was. I tried reinstalling it. Happens the last couple updates.

Token: eghsgculsi

I also have a schedule setup to auto update itself everyday at 4am and update the gravity list every couple of hrs. Along with the pi reboot 2 mins after updating pihole. (4:02am)

Am I doing somthing wrong? It worked for a while.

After running the sudo cmd to update confg, I get this

> [**✗**] Root user check  
> **Script called with non-root privileges**  
> The Pi-hole requires elevated privleges to install and run  
> Please check the installer for any concerns regarding this requirement  
> Make sure to download this script from a trusted source
> 
> [✓] Sudo utility check
> 
> [✓] Root user check  
> [i] Update option selected  
> [✓] Disk space check
> 
> [i] Update local cache of available packages...  
> [✓] Update local cache of available packages
> 
> [✓] Checking apt-get for upgraded packages... 1 updates available  
> [i] It is recommended to update your OS after installing the Pi-hole!
> 
> [i] Installer Dependency checks...  
> [✓] Checking for apt-utils  
> [✓] Checking for dialog  
> [✓] Checking for debconf  
> [✓] Checking for dhcpcd5  
> [✓] Checking for git  
> [✓] Checking for iproute2  
> [✓] Checking for whiptail
> 
> [✓] Check for existing repository in /etc/.pihole  
> [✓] Update repo in /etc/.pihole
> 
> [✓] Check for existing repository in /var/www/html/admin  
> [i] Update repo in /var/www/html/admin...  
> **Error: Could not update local repository. Contact support.**

and stops right there.

I created a auto send email a few months back:

/var/mail/pi

> From pi@raspberrypi Fri Dec 22 10:00:25 2017  
> Return-path: [pi@raspberrypi](mailto:pi@raspberrypi)  
> Envelope-to: pi@raspberrypi  
> Delivery-date: Fri, 22 Dec 2017 10:00:25 -0500  
> Received: from pi by raspberrypi.hsd1.md.comcast.net with local (Exim 4.89)  
> (envelope-from [pi@raspberrypi](mailto:pi@raspberrypi))  
> id \*\*\*\*\*\*\*\*\*\*\*\*\*  
> for pi@raspberrypi; Fri, 22 Dec 2017 10:00:24 -0500  
> From: root@raspberrypi (Cron Daemon)  
> To: pi@raspberrypi  
> Subject: Cron [pi@raspberrypi](mailto:pi@raspberrypi) sudo pihole -g  
> MIME-Version: 1.0  
> Content-Type: text/plain; charset=UTF-8  
> Content-Transfer-Encoding: 8bit  
> X-Cron-Env: \<SHELL=/bin/sh\>  
> X-Cron-Env: \<HOME=/home/pi\>  
> X-Cron-Env: \<PATH=/usr/bin:/bin\>  
> X-Cron-Env: \<LOGNAME=pi\>  
> Message-Id: \*\*\*\*\*\*\*\*\*\*\*\*\*@raspberrypi.hsd1.md.comcast.net  
> Date: Fri, 22 Dec 2017 10:00:24 -0500  
> Successful updating Gravity OK.

/var/mail/mail

> From root@raspberrypi Fri Dec 22 15:00:04 2017  
> Return-path: [root@raspberrypi](mailto:root@raspberrypi)  
> Envelope-to: root@raspberrypi  
> Delivery-date: Fri, 22 Dec 2017 15:00:04 -0500  
> Received: from root by raspberrypi.hsd1.md.comcast.net with local (Exim 4.89)  
> (envelope-from [root@raspberrypi](mailto:root@raspberrypi))  
> id \*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*  
> for root@raspberrypi; Fri, 22 Dec 2017 15:00:03 -0500  
> From: root@raspberrypi (Cron Daemon)  
> To: root@raspberrypi  
> Subject: Cron [root@raspberrypi](mailto:root@raspberrypi) pihole -g  
> MIME-Version: 1.0  
> Content-Type: text/plain; charset=UTF-8  
> Content-Transfer-Encoding: 8bit  
> X-Cron-Env: \<SHELL=/bin/sh\>  
> X-Cron-Env: \<HOME=/root\>  
> X-Cron-Env: \<PATH=/usr/bin:/bin\>  
> X-Cron-Env: \<LOGNAME=root\>  
> Message-Id: \*\*\*\*\*\*\*\*\*\*\*\*@raspberrypi.hsd1.md.comcast.net  
> Date: Fri, 22 Dec 2017 15:00:02 -0500
> 
> /bin/sh: 1: pihole: not found

2nd

> From root@raspberrypi Fri Dec 22 15:00:07 2017  
> Return-path: [root@raspberrypi](mailto:root@raspberrypi)  
> Envelope-to: root@raspberrypi  
> Delivery-date: Fri, 22 Dec 2017 15:00:07 -0500  
> Received: from root by raspberrypi.hsd1.md.comcast.net with local (Exim 4.89)  
> (envelope-from [root@raspberrypi](mailto:root@raspberrypi))  
> id \*\*\*\*\*\*\*\*\*\*\*\*\*\*\*  
> for root@raspberrypi; Fri, 22 Dec 2017 15:00:03 -0500  
> From: root@raspberrypi (Cron Daemon)  
> To: root@raspberrypi  
> Subject: Cron [root@raspberrypi](mailto:root@raspberrypi) pihole -up date \>\> pihole-update.log  
> MIME-Version: 1.0  
> Content-Type: text/plain; charset=UTF-8  
> Content-Transfer-Encoding: 8bit  
> X-Cron-Env: \<SHELL=/bin/sh\>  
> X-Cron-Env: \<HOME=/root\>  
> X-Cron-Env: \<PATH=/usr/bin:/bin\>  
> X-Cron-Env: \<LOGNAME=root\>  
> Message-Id: \*\*\*\*\*\*\*\*\*\*\*\*@raspberrypi.hsd1.md.comcast.net  
> Date: Fri, 22 Dec 2017 15:00:02 -0500
> 
> /bin/sh: 1: pihole: not found

Not sure how to stop the mail mail not found errors. If you could also help me with that as well, That be helpful.

---

<div class="post-metadata">

**Author:** ![Mcat12](https://discourse-cdn.pi-hole.net/user_avatar/discourse.pi-hole.net/mcat12/32/20_2.png) [@Mcat12](https://discourse.pi-hole.net/u/Mcat12)\
**Post date:** [December 23, 2017, 5:00pm UTC](https://discourse.pi-hole.net/t/pihole-dashboard-keeps-breaking/6095/2 "2017-12-23T17:00:34Z")

</div>

> [✓] Check for existing repository in /var/www/html/admin  
> [i] Update repo in /var/www/html/admin…  
> Error: Could not update local repository. Contact support.

> \*\*\* [DIAGNOSING]: Web version  
> [i] Web: v3.1 ([How do I update Pi-hole?](https://discourse.pi-hole.net/t/how-do-i-update-pi-hole/249))  
> [i] Branch: master  
> [i] Commit: v3.1-26-gd7fcc8e-dirty

You have changes in the web interface directory. Remove them (or run `sudo git reset --hard` in the directory) and try again.

---

<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:** [January 1, 2018, 11:15am UTC](https://discourse.pi-hole.net/t/pihole-dashboard-keeps-breaking/6095/3 "2018-01-01T11:15:10Z")

</div>

> [@Mcat12](#):
>
> sudo git reset --hard

This should fix it. I have also updated the FAQ to reflect this:

> [@Why does the Pi-hole installer produce the error "Unable to complete update, contact Pi-hole'?](https://discourse.pi-hole.net/t/why-does-the-pi-hole-installer-produce-the-error-unable-to-complete-update-contact-pi-hole/4159):
>
> If you try to install or update Pi-hole but run into problems, you may see a message such as: [✓] Check for existing repository in /var/www/html/admin [i] Update repo in /var/www/html/admin… Error: Could not update local repository. Contact support. Broken Or Modified Web Interface This error typically means the Web interface (or the Core) repository has been modified in some fashion. Since we use git to check for updates and keep Pi-hole up-to-date, you will need to remove your changes, cd …