Last time I have updated the 3 components in a row, it was following a new Pi-Hole installation. Since, nothing added except Open VPN, which is not used by the way currently.
This is the first time I am attempting an upgrade over the fly.
I am running out of idea and if I would be not wrong I did not find similar issue (unless my bad...)
Thanks for your hint and I might get what is sticking me.
In fact, due some 'local restrictions', I cannot get access to rawgithub. To install Pihole, Curl method did fail as well. I succeeded with the 3rd way by cloning github repo.
It seems FTL upgrade uses Curl which will pick up stuffs on rawgithub as well. This ends most likely in Port 443 timeout, leading to the error.
Indeed using a VPN, I can access to rawgithub repo from my laptop, thus it explains why the file xxxarm7xxx that is told to be not available, it is well there. BUT, my VPN provider does not want to support Pi (indeed when it detects I am sharing it through my phone to the Pi, it will block the connection).
So, I believe by using a brand new install and following the clone Git repo way, it will work.
But if anyone could have a clue to avoid such inefficient way, I would be more than happy
Well, I have installed Pihole several times and each time I succeeed using the 3rd method (clone repo). By doing so, I had all installed successfully...
What I want to say I cannot update FTL using the upgrade process, while by cloning a brand new install, that’s ok...
Sorry to ask basic questions but why only FTL is blocked during the process...?
I have some doubts about the root cause: when I try to access the file from my laptop (with Pihole as DNS), it fails as well. After activating the VPN, I can access it (obviously my Pihole is out of the business for that part). Please note the error I am getting is https port cannot be reached. Not so sure it is a DNS issue but rather a filtering issue...
I can well get the file but afterwards I am stuck to resume the upgrade process...
About swapping the DNS in the file you suggested, if I would be not wrong:
I shall update the file with the right DNS
Then I make a Pihole -r
Then Pihole -up
At the end, if process completed, file I changed will be restored with my Pihole IP
Did I get it correctly?
After updating DNS server, Pihole features will be obviously no longer available as all my DNS requests will be processed by the specified server, right?
Well, that changing DNS will not work, I am suddenly more confident on my growing network skills :))
Well, indeed Option 1 is the one I can only use successfully. But it means a brand new install.
I was keeping this method by looking for a potential smarter way, and obviously making a back up first with teleporter.
By the way, can I just launch the process again and it will overwrite all existing files or should unstall/remove all...?
In my previous installation, as I corrupted each time the OS (well it is by practicing that we learn :)), I started always by a clean baseline.
So to complete the loop, I solved my issue by tunneling the ethernet access of my Pi though a VPN. Error access was gone. It was really the https connection that was blocked. So afterwards, FTL updated.
What I still did not understand, I have a second Pihole running in another network. I ran as well its update but without tunneling its data and it worked! Mystery...
Anyway, when there is a 443 port error, root cause is the access being filtered.
