For test I would bypass it completely as it might be the problem.
Do not use AdGuard, configure 1.1.1.1 directly in your OS.
If you Google you will find quite few cases when B2 IP addresses were blocked by some “clever“ DNS solutions. Just forget about “cleverness“ for a moment:)
Then try rclone again.
Actually it is the problem:) Your DNS solution returns bogus results. 0.0.0.0 is not valid Internet IP address.
It is not rclone issue.
You can see what is real IP address behind http://f005.backblazeb2.com/ by running (it will force using specific DNS):
$ dig f005.backblazeb2.com @9.9.9.9
and this is what your DNS should return too if you want B2 to work with rclone.
Well, it looks like you’re absolutely right.
credit goes to @asdffdsa who from the start suspected DNS
I have to admit that 0.0.0.0 returned IP address is something I have never seen before. And I suspected that things should be more black and white in case of DNS. It works or not.
We all have learned something here:)
credit goes to @kapitainsky for using the word cleverness ;wink
0.0.0.0 is common with ad blocking tools.
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.