Unable to authorize after moving to new virtual machine

What is the problem you are having with rclone?

Failed to authenticate. I am migrating from an old-style jail on a FreeNAS system to a new-style jail on the same upgraded FreeNAS system. I copied the same "account" and "key" for my Backblaze B2 account. I've called my new remote "blaze" and its type is "b2". When I try to run "rclone lsd blaze:" I get:

2020/01/27 14:58:12 Failed to create file system for "blaze:": failed to authorize account: failed to authenticate: Get https://api.backblazeb2.com/b2api/v1/b2_authorize_account: x509: certificate signed by unknown authority

What is your rclone version (output from rclone version)

rclone v1.50.2` 
- os/arch: freebsd/amd64
- go version: go1.13.5

Which OS you are using and how many bits (eg Windows 7, 64 bit)

FreeBSD 11.2-STABLE amd64

Which cloud storage system are you using? (eg Google Drive)

Blaze B2

The command you were trying to run (eg rclone copy /tmp remote:tmp)

`rclone lsd blaze:`

A log from the command with the -vv flag (eg output from rclone -vv copy /tmp remote:tmp)

2020/01/27 15:11:29 DEBUG : rclone: Version "v1.50.2" starting with parameters ["rclone" "-vv" "lsd" "blaze:"]
2020/01/27 15:11:29 DEBUG : Using config file from "/root/.config/rclone/rclone.conf"
2020/01/27 15:11:29 Failed to create file system for "blaze:": failed to authorize account: failed to authenticate: Get https://api.backblazeb2.com/b2api/v1/b2_authorize_account: x509: certificate signed by unknown authority

That's usually something to do with the certificate store on the jail/OS but not sure how to troubleshoot it in a jail.

You may find this helpful:

https://rclone.org/faq/#rclone-gives-x509-failed-to-load-system-roots-and-no-roots-provided-error

Well, the link I believe allowed me to find the solution; I think it was indirectly though. I started following some of the instructions and when running the "curl" command, I found that was not installed. I then typed in "pkg install curl", which also installed "libnghttp2" and "ca_root_nss." Out of curiosity, before re-running the curl instruction, I decided to repeat the "rclone lsd blaze:" command and low & behold, it worked like it was supposed to, showing my bucket. As I had mentioned, this was a brand-new FreeBSD jail, so it is often cut-down and does not automatically install many helper programs unless specifically needed.

Great - glad you figured it out :slight_smile: I was hoping the link would give you a hint but that is all I had as I know nothing about FreeBSD jails!

So do you think pkg install ca_root_nss would be the minimal solution?

This topic was automatically closed 3 days after the last reply. New replies are no longer allowed.