Update not working

Help
1

Hi,
why not working update?

pi@raspberrypi:~ $ sudo su
root@raspberrypi:/home/pi# pihole -up
::: Checking for updates...
fatal: unable to access 'GitHub - pi-hole/pi-hole: A black hole for Internet advertisements': Failed to connect to github.com port 443: Connection refused
fatal: Upstream branch 'refs/heads/master' not stored as a remote-tracking branch
::: Error: Remote revision could not be obtained, ask Pi-hole support.
::: Additional debugging output:
On branch master
nothing to commit, working directory clean
root@raspberrypi:/home/pi#

2

Run pihole -d for a debug token.

3

Hi,
here is my token: i5uk2dv1n4

4

What is the output of

cd /etc/.pihole/
git status
5

Is the package "ca-certificates" installed ?

dpkg -s ca-certificates

If not, run below one to install and try again:

sudo apt install ca-certificates

6

pi@raspberrypi:~ $ cd /etc/.pihole/
pi@raspberrypi:/etc/.pihole $ git status
On branch master
nothing to commit, working directory clean

7

Hi,
yes: see:

pi@raspberrypi:/etc/.pihole $ dpkg -s ca-certificates
Package: ca-certificates
Status: install ok installed
Priority: optional
Section: misc
Installed-Size: 367
Maintainer: Michael Shuler michael@pbandjelly.org
Architecture: all
Multi-Arch: foreign
Version: 20141019+deb8u3
Depends: openssl (>= 1.0.0), debconf (>= 0.5) | debconf-2.0
Breaks: ca-certificates-java (<< 20121112+nmu1)
Enhances: openssl
Description: Common CA certificates
.......

8

NEW error:

pi@raspberrypi:~ $ pihole -up
::: Checking for updates...
fatal: Upstream branch 'refs/heads/master' not stored as a remote-tracking branch
::: Error: Remote revision could not be obtained, ask Pi-hole support.
::: Additional debugging output:
On branch master
nothing to commit, working directory clean
pi@raspberrypi:~ $

9

Seems you've got a very old version dated from 2014 : "Version: 20141019+deb8u3".
Mine is currently : "Version: 20161130".

If you update your distro with below, what version of "ca-certificates" is displayed after ?

sudo apt update
sudo apt upgrade
sudo reboot

10

Yes I see. But the strange thing is that I have two identical experiences and installation on the table, and I just do not have to update it.

11

after update system

pi@DNS-SERVER:~ $ sudo su
root@DNS-SERVER:/home/pi# dpkg -s ca-certificates
Package: ca-certificates
Status: install ok installed
Priority: optional
Section: misc
Installed-Size: 367
Maintainer: Michael Shuler michael@pbandjelly.org
Architecture: all
Multi-Arch: foreign
Version: 20141019+deb8u3
Depends: openssl (>= 1.0.0), debconf (>= 0.5) | debconf-2.0
Breaks: ca-certificates-java (<< 20121112+nmu1)
Enhances: openssl
Description: Common CA certificates

root@DNS-SERVER:/home/pi# sudo apt install ca-certificates
Reading package lists... Done
Building dependency tree
Reading state information... Done
ca-certificates is already the newest version. :flushed:
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.

i dont know:-(

12

Could try adding the stretch source, and then updating

13

Lets not do that yet though Stretch is close to stable release :wink:

@Ondrej ,
I believe your certs are fine and something else is going on causing that error "Failed to connect to github.com port 443:".
Do you still experience this error ?

Is anything displayed if doing below one ?

echo | openssl s_client -connect github.com:443

And is date/time displayed correct ?

date

And whats output for:

traceroute github.com | tail -1

*Could run last one without the "tail" bit but dont post results here!

14

Time is ok:

pi@raspberrypi:~ $ sudo su
root@raspberrypi:/home/pi# date
Tue 30 May 17:55:05 CEST 2017

root@raspberrypi:/home/pi# echo | openssl s_client -connect github.com:443
CONNECTED(00000003)

root@raspberrypi:/home/pi# traceroute github.com | tail -1
17 192.30.253.112 (192.30.253.112) 132.916 ms 131.027 ms 132.056 ms

15

"Failed to connect to github.com port 443:".
Do you still experience this error ?