You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As far as I can see, the issue is the b2_authorize_account request fails with error "x509: certificate signed by unknown authority", this error is wrapped in a b2err type which is treated as a transient error and the request retries indefinitely.
One option to avoid the retries would be to check for this "unknown authority" error and return it directly to the application?
The text was updated successfully, but these errors were encountered:
Added a check on the error type for a request failure and if it is an x509.UnknownAuthorityError return the error directly to the application rather than wrapping it in a b2err type, this avoids the retries.
Tested with restic and the command fails with error message "Fatal: create repository at b2:***** failed: b2.NewClient: x509: certificate signed by unknown authority".
garrmcnu
added a commit
to garrmcnu/blazer
that referenced
this issue
Oct 30, 2021
As described in restic/restic#2355, if the
ca_root_nss
package is not installed on FreeBSD therestic
command hangs indefinitelyCan reproduce on Linux by using a self-signed certificate for the root certificates
This example code also shows the issue by using an empty certificate pool for the
RootCAs
in the TLS client configurationAs far as I can see, the issue is the
b2_authorize_account
request fails with error "x509: certificate signed by unknown authority", this error is wrapped in ab2err
type which is treated as a transient error and the request retries indefinitely.One option to avoid the retries would be to check for this "unknown authority" error and return it directly to the application?
The text was updated successfully, but these errors were encountered: