# Updating pi.hole trough terminal

**URL:** <https://discourse.pi-hole.net/t/updating-pi-hole-trough-terminal/15063>\
**Category:** Help\
**Created:** [December 11, 2018, 3:37pm UTC](https://discourse.pi-hole.net/t/updating-pi-hole-trough-terminal/15063 "2018-12-11T15:37:22Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![yoss](https://discourse-cdn.pi-hole.net/user_avatar/discourse.pi-hole.net/yoss/32/5698_2.png) [@yoss](https://discourse.pi-hole.net/u/yoss)\
**Post date:** [December 11, 2018, 3:37pm UTC](https://discourse.pi-hole.net/t/updating-pi-hole-trough-terminal/15063/1 "2018-12-11T15:37:23Z")

</div>

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

## Expected Behaviour:

To update

## Actual Behaviour:

I have errors and no update  
pihole -v  
Pi-hole version is v4.0 (Latest: ERROR)  
AdminLTE version is v4.0 (Latest: ERROR)  
FTL version is v4.0 (Latest: ERROR)

## Debug Token:

Can't send log

[?] Would you like to upload the log? [y/N] y  
\* Using openssl for transmission.  
[✗] There was an error uploading your debug log.

- Please try again or contact the Pi-hole team for assistance.
- A local copy of the debug log can be found at: /var/log/pihole\_debug-sanitized.log

now what error I fund in terminal

[i] Checking for updates...  
fatal: unable to access '[https://github.com/pi-hole/pi-hole.git/](https://github.com/pi-hole/pi-hole.git/)': Could not resolve host: github.com  
[i] Pi-hole Core: up to date  
fatal: unable to access '[https://github.com/pi-hole/AdminLTE.git/](https://github.com/pi-hole/AdminLTE.git/)': Could not resolve host: github.com  
[i] Web Interface: up to date  
[i] FTL: update available  
[i] FTL out of date, it will be updated by the installer.  
[✗] Downloading and Installing FTL  
Error: Unable to get latest release location from GitHub  
[✗] FTL Engine not installed

- Pinging 192.168.5.99...  
[✗] Gateway did not respond. ([Why is a default gateway important for Pi-hole?](https://discourse.pi-hole.net/t/why-is-a-default-gateway-important-for-pi-hole/3546))

I tried in terminal direct ping  
--- 192.168.5.99 ping statistics ---  
4 packets transmitted, 0 received, 100% packet loss, time 3052ms

yoss@orangepi:/etc/pihole$ ip -4 route | grep default | cut -d ' ' -f 3  
192.168.5.99  
But internet and pi.hole in browser is working normally. Only error I find in debug.log different than other errors is this

\*\*\* [DIAGNOSING]: Dashboard and block page  
[✗] Block page X-Header: X-Header does not match or could not be retrieved.  
HTTP/1.1 200 OK  
Content-type: text/html; charset=UTF-8  
Date: Tue, 11 Dec 2018 15:11:02 GMT  
Server: lighttpd/1.4.45

---

<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 12, 2018, 7:30pm UTC](https://discourse.pi-hole.net/t/updating-pi-hole-trough-terminal/15063/2 "2018-12-12T19:30:23Z")

</div>

You don't appear able to resolve external domains. What is the output of these commands?

```auto
cat /etc/resolv.conf
service pihole-FTL status
dig google.com @127.0.0.1

```

---

<div class="post-metadata">

**Author:** ![yoss](https://discourse-cdn.pi-hole.net/user_avatar/discourse.pi-hole.net/yoss/32/5698_2.png) [@yoss](https://discourse.pi-hole.net/u/yoss)\
**Post date:** [December 12, 2018, 11:39pm UTC](https://discourse.pi-hole.net/t/updating-pi-hole-trough-terminal/15063/3 "2018-12-12T23:39:27Z")

</div>

```
yoss@orangepi:~$ cat /etc/resolv.conf
Generated by NetworkManager
nameeserver 192.168.5.99

```

* * *

```
 yoss@orangepi:~$ service pihole-FTL status
pihole-FTL.service - LSB: pihole-FTL daemon
Loaded: loaded (/etc/init.d/pihole-FTL; generated)
Active: active (exited) since Tue 2018-12-11 17:41:39 CET; 1 day 6h ago
    
Docs: man:systemd-sysv-generator(8)
Tasks: 0 (limit: 1008)
CGroup: /system.slice/pihole-FTL.service

Dec 11 17:41:38 orangepi systemd[1]: Starting LSB: pihole-FTL daemon...
Dec 11 17:41:39 orangepi pihole-FTL[21107]: Not running
Dec 11 17:41:39 orangepi pihole-FTL[21107]: chown: cannot access '/etc/pihole/dh
Dec 11 17:41:39 orangepi pihole-FTL[21107]: /etc/resolvconf/update.d/libc: Warni
Dec 11 17:41:39 orangepi su[21144]: Successful su for pihole by root
Dec 11 17:41:39 orangepi su[21144]: + ??? root:pihole
Dec 11 17:41:39 orangepi su[21144]: pam_unix(su:session): session opened for use
Dec 11 17:41:39 orangepi pihole-FTL[21107]: FTL started!
Dec 11 17:41:39 orangepi su[21144]: pam_unix(su:session): session closed for use
Dec 11 17:41:39 orangepi systemd[1]: Started LSB: pihole-FTL daemon.

```

* * *

```
yoss@orangepi:~$ dig google.com @127.0.0.1

; <<>> DiG 9.11.3-1ubuntu1.3-Ubuntu <<>> google.com @127.0.0.1
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 32113
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 1452
;; QUESTION SECTION:
;google.com. IN	A

;; ANSWER SECTION:
google.com. 36	IN	A	216.58.201.110

;; Query time: 21 msec
;; SERVER: 127.0.0.1#53(127.0.0.1)
;; WHEN: Thu Dec 13 00:34:29 CET 2018
 ;; MSG SIZE rcvd: 55

```

---

<div class="post-metadata">

**Author:** ![yoss](https://discourse-cdn.pi-hole.net/user_avatar/discourse.pi-hole.net/yoss/32/5698_2.png) [@yoss](https://discourse.pi-hole.net/u/yoss)\
**Post date:** [December 13, 2018, 11:56am UTC](https://discourse.pi-hole.net/t/updating-pi-hole-trough-terminal/15063/4 "2018-12-13T11:56:25Z")

</div>

OK, I changed nameserver in resolv.conf to 1.1.1.1 and update passed with no problem.  
I was thinking that pi.hole resolve DNS addressees by himself, and oblivious I was wrong.

---

<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:** [January 3, 2019, 11:56am UTC](https://discourse.pi-hole.net/t/updating-pi-hole-trough-terminal/15063/5 "2019-01-03T11:56:29Z")

</div>

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