New Install
The standard install script fails when trying to install FTL Error : Unable to get latest release location from GitHub
Pihole -up gives same error after indicating an upgrade is available
Unable to upload to Pihole …...using openssl for transmission. There was an error uploading your debug.log ….
Hello,
Just tried doing two fresh installs (to be sure it wasn't a one-time issue) and I can confirm that I'm getting the exact same error. I tried doing a pihole -r to see if it would do anything but looks like it's not changing anything.
I suppose it would be something coming from the GitHub repo where the FTL files are located, either that or there is something wrong with the install script.
Edit: pihole -up doesn't solve the problem either, I get an error saying it can't complete the update.
@anon55913113 Tried doing that on the latest Raspbian stable release since I'm running Pi-Hole on a Raspberry Pi and here's what I get from it:
Failed to enable unit: File pihole-FTL.service: No such file or directory
Either it's not the right name for the service or FTL didn't even get installed during the Pi-Hole initial installation process (which is most likely what happened).
@anon55913113 I actually managed to get FTL installed and running by using pihole -r after disabling the blocking through the admin panel.
For some reason, it seems like pihole disable didn't disable the blocking although it showed so in my terminal.
I still wonder why in the world would the needed URLs be blocked by Pi-Hole itself.
But thanks anyway! It seems like that solution is working for now although I believe it will be fixed in the future by the developers. I'd advise @kkorkky to try that solution and see if it changes anything for them as well.
Unfortunately this did not work. Remember this was an initial install that failed.
Pihole -r does not work either
Thanks for your assistance
I note that on GitHub FTL was amended some 8 hours ago. Could that be related somehow?
@kkorkky I'm not really sure about what you are talking about but I've looked at the open issues on the FTL's GitHub repo and the only thing somewhat related to the issue I could find is this issue: missing url · Issue #365 · pi-hole/FTL · GitHub
Although this issue was opened 8 days ago, if that's what you are referencing.
Did your initial install fail before you could even get the web panel and the core running or? Because mine did atleast manage to get those up and running.
This is a new install on Raspberry Pi . all Os and kernel updates applied before running the Curl Install script.
I have installed Pihole before but had to reuse the Pi for another task.
So running the vanilla install, Pihole -r or Pihole -up always gives the FTL GitHub errors . I have disable the Pihole whilst performing the Updates from the GUI.. Option DISABLE and take a custom value of 15 mins.
Try the updates and the same failure message again. I have tried a sudo reboot just as a precaution.
The GUI reports the DNS and FTL not running. Low cpu and memory usage.
I will be patient and give another try tomorrow in case some links are outdate and require to be refreshed.
Korky
I am not getting the 404 url issue displayed
@kkorkky Sorry to hear that this solution isn't working for you. I wasn't getting the the 404 URL issue either but the exact same one as yours.
Hopefully you can manage to get FTL running next try. Just if it can be of any help, here's exactly how I proceeded:
pihole -r and choose to keep the configurationIf everything went well, you should see no error at the end of the repair. It indeed seems like that the blocking is interfering with the install/update.
I think I have a native DNS issue. DNS was tested and working before the Pihole install. Now after performing an uninstall of Pihole, Sudo Reboot I have no DNS resolution of BBc.co.uk . Even changed the DNS server to be 1.1.1.1 and no luck.
Back to basics for the time being .
Thanks for all your assistance
Alright, so I tried doing the solution process once again just to be sure and it seems like that Pi-Hole doesn't even wanna disable the blocking anymore, wether I do it from the GUI or from CLI. I keep getting that same error on doing pihole -r.
@anon55913113 I get the exact same error as @kkorkky in the first post of this thread:
Error: Unable to get latest release location from GitHub
Doing a nslookup on any domain gives me:
connection timed out; no servers could be reached
I believe I'm gonna give up on getting a Pi-Hole running on my network for now and wait until a fix is released so it works on initial install. Thanks anyway!
Temporarily change nameserver in /etc/resolv.conf from 127.0.0.1 into 8.8.8.8:
sudo sed -i 's/127.0.0.1/8.8.8.8/' /etc/resolv.conf
And run repair:
pihole -r
Decided to give it a try just for the sake of it and yep, it's working with the /etc/resolv.conf fix.
Thanks a lot @deHakkelaar and @anon55913113!
Now that the FTLDNS is working, I'm assuming I just need to run sudo sed -i 's/8.8.8.8/127.0.0.1/' /etc/resolv.conf to get back to using the local DNS since it's now up and running.
I can't help but seeing a funny side to this issue, Pi-Hole not being able to insall the DNS server used to be able to install that same DNS server. Anyway, hope a fix will be released soon for new installs.
Thanks again!
Edit: Oh right. Dumb me. 
I didn't remember the file would get overwritten.
You do not have to change /etc/resolve/conf to original configuration. The repair does that for you.
If you have run pihole -r, it did that for you already:
pi@noads:~ $ cat /etc/resolv.conf
# Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8)
# DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN
nameserver 127.0.0.1
EDIT: @jfb beat me by a second 
Oh thank you man! This solved it for me! Had the same issue, DNS not running, FTL not running.
Hmmm we have all been on the same thread. I edited the resolv.conf to be my local router 192.168.1.254 and hey presto it all worked.
Now wondering how this issue came about for so may users ……….. any thoughts?
I restarted the Pi and can still resolve names
Thanks for all feedback, but as to the Root cause of this issue I am non the wiser...
cheers
Korky (retired Problem Manager !!!)
I believe nameserver in resolv.conf gets changed too quickly into 127.0.0.1 without checking if a DNS daemon is actually listening on the localhost IP (pihole-FTL failed to start for example).
Consequently, all further operations that depend on name resolution will fail.
I bet the developers will have a say about this 