B2 Cloud Credentials fail to authenticate on TrueNAS after switching to pfSense

Networking & Firewalls
1

Hi there!

My Backblaze B2 cloud credentials fail authenticate on TrueNas CORE 12. It used to work correctly but has stopped after I switched from an ISP provided router to pfSense. I then decided to test out Amazon S3 after failing to find a fix with Backblaze and ran into a similar issue.

The errors i receive in the TrueNAS GUI are when authenticating the cloud credentials are:
Backblaze:
Error: 2022/02/07 00:36:34 Failed to create file system for "remote:": failed to authorize account: failed to authenticate: Get https://api.backblazeb2.com/b2api/v1/b2_authorize_account: dial tcp: lookup [api.backblazeb2.com](http://api.backblazeb2.com) on [::1]:53: read udp [::1]:30631->[::1]:53: read: connection refused

Amazon S3:

Error: 2022/02/07 00:29:47 ERROR : : error listing: RequestError: send request failed

caused by: Get https://s3.ap-southeast-2.amazonaws.com/: dial tcp: lookup s3.ap-southeast-2.amazonaws.com on [::1]:53: read udp [::1]:31817->[::1]:53: read: connection refused

2022/02/07 00:29:47 Failed to lsjson with 2 errors: last error was: error in ListJSON: RequestError: send request failed

caused by: Get https://s3.ap-southeast-2.amazonaws.com/: dial tcp: lookup s3.ap-southeast-2.amazonaws.com on [::1]:53: read udp [::1]:31817->[::1]:53: read: connection refused

I -think- the issue is related to me not configuring something correctly in pfSense as the issue wasn’t present before switching. It’s a fresh install without any add-ons.

Couldn’t find a fix after a quick search online, however if the issue has an existing solution then I’d really appreciate being pointed in the right direction.

If any of you wonderful people need further information, I’m more than happy to provide it. If I’m being an idiot, I’m happy to be told as much, haha.

2

If the issues started when you changed to pfsense then it’s most likely that you don’t have DNS working properly on TrueNAS or you are blocking it on pfsense. Open up the terminal on TrueNAS and see if you can ping external sites and resolve DNS.

1 Like
3

Hi @LTS_Tom thanks for your advice! Pinging external sites as well as external IP Addresses wasn’t working. I entered the default gateway and some DNS servers in the TrueNAS network settings which resolved the problem.

My understanding is that the issue was caused by running pfSense in a VM on TrueNAS. As pfSense isn’t available while the server boots, I had to assign TrueNAS a static IP in the network settings from the command line, but this meant that it wasn’t assigned a default gateway and DNS servers via DHCP once the pfSense VM finally booted.

Thanks again for your help, I was very stuck on this issue and your advice lead me to a solution. It is really appreciated!

1 Like