-
Notifications
You must be signed in to change notification settings - Fork 14
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ERROR: The certificate of ‘sputnik.roen.us’ is not trusted. #74
Comments
We have adapted the install to a bash-only script. |
cool thanks, worked after chmod -x But nothing happens still normal 404 pages, any idea what I did wrong? This is the install log. pihole@CIT-PIH-01:~$ sudo ./install.sh.1 To ensure compatibility, the system should be updated. Is this ok? [Y/n] y The installer will now check for and install dependencies. Is this ok? [Y/n] y [✓] git is installed. We think that your webroot is /var/www/html/ and will install there. Is this ok? [Y/n] y
You are in 'detached HEAD' state. You can look around, make experimental If you want to create a new branch to retain commits you create, you may git checkout -b HEAD is now at a34f247 beta --> master - Update functionality (#2) To complete installation, pihole-FTL.service should be restarted. Is this ok? [Y/n] y |
Is your Pi's webserver listening on port 443? |
Seems not... 😊 pihole@CIT-PIH-01:~$ ss I only ran the script didn't do anything else. What did I miss? |
If you are using lighttpd, you should configure it to listen for connections on port 443 using either a self-signed certificate or one with your Pi's fully qualified domain name. That way, if a request comes with HTTPS prepended, it will hit lighttpd and should forward it to the PiPass blockpage. Note that for websites with a cached HSTS header, you will not be able to load the page and will not be able to manually bypass the certificate error. |
root@CIT-PIH-01:~# cat wget-log
--2020-11-15 15:38:42-- https://sputnik.roen.us/pipass/scripts/install.sh
Resolving sputnik.roen.us (sputnik.roen.us)... 141.239.111.200
Connecting to sputnik.roen.us (sputnik.roen.us)|141.239.111.200|:443... connected.
ERROR: The certificate of ‘sputnik.roen.us’ is not trusted.
ERROR: The certificate of ‘sputnik.roen.us’ doesn't have a known issuer.
The certificate's owner does not match hostname ‘sputnik.roen.us’
The text was updated successfully, but these errors were encountered: