The second part of the linked bug report on the curl repo btw is about an even increased sensitivity of curl about such OpenSSL syscalls that was introduced with curl 7.67, i.e. not yet part of Debian Buster curl version: openssl: Revert to less sensitivity for SYSCALL errors · jay/curl@d741f50 · GitHub
Sad that it wasn't investigated deeper.
Yes, I tried that option also before doing update and then upgrade on a fresh install of raspbian lite os.
I will try to do a fresh installation today and see if the error repeats.
i tried once again today after installing a fresh copy of Raspbian OS lite
Immediately after installing the OS, i connected to my PC using Putty and fired up the Bash Command as you told. And once again it stopped as it had many times yesterday !!! at the same level where Downloading and Installing FTL... it stays forever
Maybe after 20-30 Minutes it says error in installing FTL.
I am really not understanding why its happening all of a sudden to me now, that too since yesterday. Before that i have reinstalled Pihole on Raspbian OS many times without any problem...
Pls anyone guide me . Without Pihole i cannot use Internet. These Ads are killing me.
Finally.... i got it working. i somehow tried to reset my Router and once again tried to install Pihole. Before i could see what has happened i could see the Login Details for Pihole Admin Page...
I had a Grin on my Face finally...
I was so pissed off....
Now i will start installing Unbound and Dnscrypt Proxy...
I also wanted to know, is there a guid to Install the latest version of Unbound to Pihole ? the one available for Pihole from Anudeep is very old version. Any Guidance to get the latest version of Unbound working would be highly appreciated.
Does dmesg report any related error message after you fired/cancelled the curl command?
Two ideas:
Reduce MTU size: ip l set dev eth0 mtu 1400 or even lower.
Try to switch to WiFi, at least to check if the network adapter or interface itself has an effect.
EDIT: Okay see you solved it while I was writing , although I don't understand what the issue was. The router reset did it?
For Unbound, the Pi-hole docs are still fine: Redirecting...
As of DNS Flag Day October 2020 edns-buffer-size: 1232 is the recommended value and new default on current Unbound versions (now available in Debian/Raspbian Buster repository), so you could set that. You can also use or compare with the configuration I'm currently working on: DietPi/.conf/dps_182/unbound.conf at 44706045d5b9747b06e253f7ea3bea0e84716aa5 · MichaIng/DietPi · GitHub
Change interface and port to 127.0.0.1 and 5335. In that case the access-control practically do not play a role. Download and uncomment root-hints as the builtin defaults from the Buster Unbound package is quite old. Taking into account defaults, the two configurations otherwise do not differ much.
yes. It somehow worked. I thought of resetting the Router, and that did the Trick.
You have mentioned about the new Unbound Configuration, can i use it instead of original in Pihole Documentation ? will it work ?
What version of Unbound are you using ? is it possible to update it to the latest nad make it work in Pihole ? i tried many times and i had error in getting it to work. Pls guide me. Thanks
The best approach is to work with the version of unbound ships with your distribution. After you get that working properly, then consider compiling your own latest version.
For Buster, the shipping version of unbound is 1.9.0, and it works fine.
Does it contain all the Security Patches ? i heard from V1.10 and above there are some serious Security Patches fixed, which are essential. So i thought it could be very useful for a noob like me who find it difficult to compile a working Version for myself. Hence i requested help from Experts here.
When adjusting interface and port as mentioned, our configuration will work, but as said it practically does not differ much from the on of the Pi-hole docs, which is not outdated or so, aside of that minimal edns-buffer-size thing, which as well won't have an effect in 99,X% of cases.
For the version, I agree with @jfb that there is no much reason to move away from the one shipped by the distribution, which is what the guide suggests as well as what we are doing at DietPi. But of course it is always possible to compile the latest version yourself from source: GitHub - NLnetLabs/unbound: Unbound is a validating, recursive, and caching DNS resolver. It might however require some more manual setup, although a systemd unit seems to be included in the upstream install step.
, although I don't understand what the issue was. The router reset did it?