Boto S3 - Boto [SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed while connecting to S3 #20147
Unanswered
cmdrrobin
asked this question in
Help Wanted!
Replies: 1 comment 1 reply
-
I haven't tried but it sounds like this might be a bug with AWS SDK. See here: aws/aws-cli#9016 Does it work if you replace the cacert.pem file inside the certifi lib? Obviously that's not a scalable solution but it might work in a pinch. |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
When using S3 storage solution for Netbox and a custom CA, it gives an error message when trying to upload a script.
Boto [SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed while connecting to S3
We use the Netbox Helm chart, for deploying Netbox into our environment. With storage backend
storages.backends.s3.S3Storage
, we have add the optionsendpoint_url
,use_ssl
,bucket_name
, andverify
. Also added extra environment variables (extraEnvs
) to de deployment, to includeREQUESTS_CA_BUNDLE
,SSL_CERT_FILE
and evenAWS_CA_BUNDLE
. Unfortunately this doesn't work for Boto.As far as I know Boto uses certifi, for SSL support.
Is there a way to point certifi to the local CA file, (in my case
/etc/ssl/certs/ca-certificates.crt
), or does anybody know how to fix this?Currently running Netbox v4.3.6.
Beta Was this translation helpful? Give feedback.
All reactions