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
I ended up resolving this personally by making sure certifi is installed and then setting SSL_CERT_FILE to point to that cert (e.g. SSL_CERT_FILE=$(python -c 'import certifi; print(certifi.where())')
What's best practice here? Is this something we should document? Have datalogistik do when it detects it's in this circumstance?
The text was updated successfully, but these errors were encountered:
I've run into an issue a few times where datalogistik is unable to access certificates on brew-installed python:
It's similer to https://stackoverflow.com/questions/42098126/mac-osx-python-ssl-sslerror-ssl-certificate-verify-failed-certificate-verify?_gl=1*11zkby9*_ga*OTcyMDU0NDQwLjE2NjM2MDYxNTY.*_ga_S812YQPLT2*MTY2MzYwNjE1Ni4xLjEuMTY2MzYwNjE3NS4wLjAuMA..
I ended up resolving this personally by making sure certifi is installed and then setting
SSL_CERT_FILE
to point to that cert (e.g.SSL_CERT_FILE=$(python -c 'import certifi; print(certifi.where())')
What's best practice here? Is this something we should document? Have datalogistik do when it detects it's in this circumstance?
The text was updated successfully, but these errors were encountered: