Please follow the below template, it will help us to help you!
Expected Behaviour:
Expected clean upgrade to latest version
Actual Behaviour:
_Ended with following message:
" Unable to complete update, please contact Pi-hole Support"
Debug Token:
-----head of pihole.log------
Aug 8 00:00:04 dnsmasq[737]: 46363 127.0.0.1/57182 query[PTR] 1.1.168.192.in-addr.arpa from 127.0.0.1
Aug 8 00:00:04 dnsmasq[737]: 46363 127.0.0.1/57182 forwarded 1.1.168.192.in-addr.arpa to 8.8.8.8
Aug 8 00:00:04 dnsmasq[737]: 46364 127.0.0.1/57170 query[PTR] 4.4.8.8.in-addr.arpa from 127.0.0.1
Aug 8 00:00:04 dnsmasq[737]: 46364 127.0.0.1/57170 forwarded 4.4.8.8.in-addr.arpa to 8.8.8.8
Aug 8 00:00:04 dnsmasq[737]: 46364 127.0.0.1/57170 reply 8.8.4.4 is google-public-dns-b.google.com
Aug 8 00:00:04 dnsmasq[737]: 46365 127.0.0.1/42821 query[PTR] 8.8.8.8.in-addr.arpa from 127.0.0.1
Aug 8 00:00:04 dnsmasq[737]: 46365 127.0.0.1/42821 forwarded 8.8.8.8.in-addr.arpa to 8.8.8.8
Aug 8 00:00:04 dnsmasq[737]: 46365 127.0.0.1/42821 reply 8.8.8.8 is google-public-dns-a.google.com
Aug 8 00:00:04 dnsmasq[737]: 46366 127.0.0.1/60549 query[PTR] 130.1.168.192.in-addr.arpa from 127.0.0.1
Aug 8 00:00:04 dnsmasq[737]: 46366 127.0.0.1/60549 forwarded 130.1.168.192.in-addr.arpa to 8.8.8.8
Aug 8 00:00:04 dnsmasq[737]: 46367 127.0.0.1/41056 query[PTR] 105.1.168.192.in-addr.arpa from 127.0.0.1
Aug 8 00:00:04 dnsmasq[737]: 46367 127.0.0.1/41056 forwarded 105.1.168.192.in-addr.arpa to 8.8.8.8
Aug 8 00:00:05 dnsmasq[737]: 46368 127.0.0.1/33349 query[PTR] 1.1.168.192.in-addr.arpa from 127.0.0.1
Aug 8 00:00:05 dnsmasq[737]: 46368 127.0.0.1/33349 forwarded 1.1.168.192.in-addr.arpa to 8.8.8.8
Aug 8 00:00:05 dnsmasq[737]: 46369 127.0.0.1/44739 query[PTR] 130.1.168.192.in-addr.arpa from 127.0.0.1
Aug 8 00:00:05 dnsmasq[737]: 46369 127.0.0.1/44739 forwarded 130.1.168.192.in-addr.arpa to 8.8.8.8
Aug 8 00:00:05 dnsmasq[737]: 46370 127.0.0.1/46004 query[PTR] 105.1.168.192.in-addr.arpa from 127.0.0.1
Aug 8 00:00:05 dnsmasq[737]: 46370 127.0.0.1/46004 forwarded 105.1.168.192.in-addr.arpa to 8.8.8.8
Aug 8 00:00:42 dnsmasq[737]: 46371 192.168.1.1/34336 query[A] api-global.netflix.com from 192.168.1.1
Aug 8 00:00:42 dnsmasq[737]: 46371 192.168.1.1/34336 cached api-global.netflix.com is
Post a token here for the developers to have a look:
You didnt post allot of info but I suspect you might have run into the same issue I experienced while updating to V4 today.
Edit the file "/etc/resolv.conf", replace the "127.0.0.1" or ":::1" address with that of for example google's DNS server "8.8.8.8"
and run the upgrade again "pihole -up".
After the upgrade, you'll notice the resolv.conf file has reverted back to using 127.0.0.1 as nameserver.
I ran DEBUG from web interface: Ended with the following:- No Token that I can find!?
[✓] ** FINISHED DEBUGGING! **
* The debug log can be uploaded to tricorder.pi-hole.net for sharing with developers only.
* For more information, see: https://pi-hole.net/2016/11/07/crack-our-medical-tricorder-win-a-raspberry-pi-3/
* If available, we'll use openssl to upload the log, otherwise it will fall back to netcat.
[i] Debug script running in automated mode
* 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
I need some very basic help here. i'm using Metro Putty to access my R. Pi, i.e SSH. I will need a CLI editor to edit the file. Being completely dumb in Rasbian (or any UNIX)
