I'm sorry but i just got on here. I ran a debug on pihole before joining. I really dont know what I'm doing... I am having problem getting the admin page to open after getting pihole updated. pihole -v all shows updated except AdminLTE. (see below) Do I need to debug and send the results to you? How do I do that? Thank you for any help. I m new to this...
Pi-hole version is v6.4.3 (Latest: v6.4.3)
AdminLTE version is -1 (Latest: v6.7)
Current FTL version is v5.15
When you want help from Pi-hole team, we need to know a lot of details about your system. Instead of asking lots and lots of questions and requesting you to execute many commands, we ask for the Debug Log.
Follow these instructions:
Login into your Pi-hole's command line (using keyboard and monitor or using ssh)
Execute the command sudo pihole -d
When asked, answer "Y" to upload the log.
Post here only debug token that is generated after the upload completes.
I'm sorry that I'm new to this and have questions. Do I enter the entire string or just the last number string? Right now my pihole is locked up so I'm having difficulty getting the number string. I had to reboot it.
Everything on my pihole was very old until today. I've been having problems for a long time but recently we switched to AT&T fiber. I use my router to manage my computers and had to change all of the IP addresses. I don't think that is causing the problems but I did do a manual update on pihole. I think it updated the core but nothing else. FYI I manually broke the links in text since new user are limited to 5. Here are the errors:
pi@pi-hole:/var/log $ sudo apt update
Hit:1 http: // archive.raspberrypi.org/debian bullseye InRelease
Get:2 https ://pkg.cloudflareclient.com bullseye InRelease [2,579 B]
Hit:3 http:/ /raspbian.raspberrypi.org/raspbian bullseye InRelease
Err:2 https://pkg.cloudflareclient.com bullseye InRelease
The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 6E2DD2174FA1C3BA
Reading package lists... Done
W: GPG error: https ://pkg.cloudflareclient.com bullseye InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 6E2DD2174FA1C3BA
E: The repository 'https ://pkg.cloudflareclient.com bullseye InRelease' is not signed.
N: Updating from such a repository can't be done securely, and is therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration details.
It means your Operating System is old. You didn't update it for a long time and most of the packages are probably not upgradable.
The error messages about "The following signatures couldn't be verified because the public key is not available: NO_PUBKEY" mean the current repositories (where the updates should be found) changed their keys, but you machine never updated them.
Suggestion:
It would be a lot easier to just start over, installing a fresh Raspberry Pi OS. Then you install Pi-hole again, without issues.
Your debug log shows you are running an armv7l processor (Pi 3 or Pi 4).
Everything on your system (including the OS) seems to be at least 4 years old. Upgrading everything will be painful and you will end with an old OS. Installing a fresh OS will be a lot faster.
Also, if your intention is to use this machine only to run Pi-hole, I suggest you to install the Raspberry Pi OS Lite version (without a desktop) and then you access the machine via ssh.
I have some questions. At one point this pihole did update but stopped because of the repository and yes I have run it a long time without updating it. I had set it up as a DNS server. I don't remember how or even what I used. Is there any way you can tell me what it was?? LOL I'm old and slept many days since then. I would like to keep it as my DNS server but don't know how I would set that up again. I may have documented all of this but have no clue where it would be. Most likely I will update to the newer pihole but that isn't like when I did it before. It was an image file from pihole. Am I wrong about that?
The repository is not part of Pi-hole. It is part of the Raspberry Pi OS (operating system).
At the moment, the OS is old and broken. It will be hard to fix this, specially if you consider yourself a beginner.
My suggestion is:
Do not try to fix the broken OS. It will take a really long time and, even if everything is successfully "updated", you will still have an old OS from 4 years ago, with software updated to versions from 2 or 3 years ago. It is not worth it.
This is probably a waste of time and I can't guarantee the future Pi-hole versions will work on an old OS.
I don't understand what you are asking, but I think this is not necessary.
I saw that you moved this line of questions to a new post I used it to continue. Did you go back to the original? On that new post I will ask and respond again.
Thanks, I will probably wait until the weekend to upgrade. That will give me more time. I was able to find a backup microsd card and went ahead and booted it and fixed the ip on it. The versions of pihole apps are the same as they were this morning before I tried to upgrade with standalone installer. So at least the admin page comes up again. I'll get the sd card I have ready for the new pi os. Then I can add pihole to it.