Windows Server 2016 B2 Bucket Errors

I recently installed the Native GUI edition on a Windows Server 2016 machine. Installed just fine; however, when I go to add a B2 Bucket I get several errors:

ERROR maximum backoff reached

and

Failed to retrieve storage information

I have entered the B2 keyID in the “Account ID” field and the B2 applicationKey in the “Application key” field. Windows firewall is completely turned off and this machine sits behind the same gateway as an unRAID box on which I am also running Duplicacy using B2 buckets with no problems.

Am I missing some simple step that will fix this? Many thanks in advance.

Post the full logs, especially preceeding the failure.

This B2 telling the client it is trying too often.

Thank you for the fast response. Log contents:

18:23:17.000    Command: duplicacy -background -log -d info -repository "J:\SYS32" -storage-name gui1 "b2://jmk-SYS-BU"
18:23:18.040    Reading the environment variable DUPLICACY_GUI1_B2_ID
18:23:18.043    Reading b2_id from keychain/keyring
18:23:18.043    Reading the environment variable DUPLICACY_GUI1_B2_KEY
18:23:18.043    Reading b2_key from keychain/keyring
18:23:18.846    URL request 'https://f005.backblazeb2.com/file/jmk-SYS-BU/config' returned an error: Head https://f005.backblazeb2.com/file/jmk-SYS-BU/config: dial tcp: lookup f005.backblazeb2.com: no such host
18:23:19.846    URL request 'https://f005.backblazeb2.com/file/jmk-SYS-BU/config' returned an error: Head https://f005.backblazeb2.com/file/jmk-SYS-BU/config: dial tcp: lookup f005.backblazeb2.com: no such host
18:23:21.847    URL request 'https://f005.backblazeb2.com/file/jmk-SYS-BU/config' returned an error: Head https://f005.backblazeb2.com/file/jmk-SYS-BU/config: dial tcp: lookup f005.backblazeb2.com: no such host
18:23:25.847    URL request 'https://f005.backblazeb2.com/file/jmk-SYS-BU/config' returned an error: Head https://f005.backblazeb2.com/file/jmk-SYS-BU/config: dial tcp: lookup f005.backblazeb2.com: no such host
18:23:33.848    URL request 'https://f005.backblazeb2.com/file/jmk-SYS-BU/config' returned an error: Head https://f005.backblazeb2.com/file/jmk-SYS-BU/config: dial tcp: lookup f005.backblazeb2.com: no such host
18:23:49.848    URL request 'https://f005.backblazeb2.com/file/jmk-SYS-BU/config' returned an error: Head https://f005.backblazeb2.com/file/jmk-SYS-BU/config: dial tcp: lookup f005.backblazeb2.com: no such host
18:24:21.848    URL request 'https://f005.backblazeb2.com/file/jmk-SYS-BU/config' returned an error: Head https://f005.backblazeb2.com/file/jmk-SYS-BU/config: dial tcp: lookup f005.backblazeb2.com: no such host
18:25:25.847    URL request 'https://f005.backblazeb2.com/file/jmk-SYS-BU/config' returned an error: Head https://f005.backblazeb2.com/file/jmk-SYS-BU/config: dial tcp: lookup f005.backblazeb2.com: no such host

“No such host” usually means DNS is broken.

Can you check if you can resolve this from another machine? If yes- it’s a dns issue on your machine.

If no — it’s a Backblaze issue returning non-existent URLs. I don’t remember if f005 is a real endpoint.

Interesting. Resolves fine from two other machines on the same network. But not that machine.
Any idea how to fix that?

EDIT: so that machine is running Proton VPN, but I have it set so that only one application uses it. However, as soon as I kill Proton everything starts working. So I need to figure out how to configure Duplicacy to work with the Proton?

EDIT: so I tried different configurations in ProtonVPN and was not able to get it to work. The only time that host will resolve and/or Duplicacy can connect to B2 is after disabling ProtonVPN.

You can do a few things, depending on what that one other application is. You can run it in the container (or vm), and run proton vpn in the same container (or vm).

You can configure vpn on your gateway instead, and use traffic rules to send specific type of traffic through the tunnel. This will work well if the traffic type is well defined.

You can also avoid using Proton VPNs dns server in the first place.

But all of that is far outside of scope of this forum…

1 Like

That did the trick. Many thanks!

1 Like