I am changing the variable as stated when i receive this error:
`[✗] Unsupported OS detected Redirecting...
This check can be skipped by setting the environment variable PIHOLE_SKIP_OS_CHECK to true
e.g: export PIHOLE_SKIP_OS_CHECK=true
By setting this variable to true you acknowledge there may be issues with Pi-hole during or after the install
If that is the case, you can feel free to ask the community on Discourse with the Community Help category:
https://discourse.pi-hole.net/c/bugs-problems-issues/community-help/`
i then type export PIHOLE_SKIP_OS_CHECK=true and when doing echo $PIHOLE_SKIP_OS_CHECK it says it is true but i still get the error when trying to install pihole
I'm on Kali GNU/Linux Rolling, 64-bit, Gnome version 3.36.3
That seems to be something before the installer is even passed to bash.
Ubuntu 19 is unsupported, we support 16, 18 and 20. Offhand I don't see what would prevent us from supporting 19, and if we can then we'll just need to update the TXT record and you'll be able to install.
I am trying an upgrade to 20 first, will get back to you since I saw you were skipping the supported odd numbers. I use this machine as a minecraft server anyways. No big deal.
Thanks for suggestion Dan. Still, the same hang on OS. I tried re-flashing the SD card and not updating first, the pi-hole installer suggested that I update after install, (root was OK), but then same issue.
I also tried to use Diet Pi (because of option to add PI-Hole), but it failed to install.
funny note on the upgrade from ubuntu 19 to 20, it's a headless server so during the upgrade, it locked me out of local ssh. I had to temporarily open a router port to ssh into my headless server to reboot it, then I could login from a local ip number.. I probably could have went to the basement and restarted it with the power button, but what's the fun in that?
They always say this as SSH may get restarted during the upgrade. As safety measure, I run the upgrade in tmux to ensure a killed SSH connection doesn't hurt. Cutting a long story short:
In the same warning it says that it will spawn a backup SSH server which will NOT restart. I never needed it, though.
I have never seen an actual interruption of service. I upgraded my server at home as well as three servers in remote data centers from Ubuntu 16->18->20 and never had a problem.
It told me that too. It said it would spawn a backup server at port 1022. Probably should have opened that port in the firewall before doing it. I went ahead and that's where I couldn't login from a local ip address. I happen to have a game server manager on that same system and noticed I could get into it after the upgrade from outside my network by using my wan address. So for a couple of minutes I opened port 22 in my router to point to that server and I was able to ssh from my wan address. Did a reboot from there, now everything is fine.
Used to run Mint Debian and 4.4 went 5 fine by ignoring OS check. Now moved to MX Linux and need to do a fresh install, trouble is OS not supported again. Tried the suggestions above for incorporating Ignore with curl without success.