Binance certificate
See original GitHub issueCalling method for binance raises certificate_verify_error e.g.
ccxt.binance().fetch_ticker('BTC/USDT')
raises [SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed (_ssl.c:748)
Headers: {‘User-Agent’: ‘ccxt/1.7.110 (+https://github.com/kroitor/ccxt) Python/3.6.2’, ‘Accept-Encoding’: ‘gzip, deflate’}
Issue Analytics
- State:
- Created 6 years ago
- Comments:7 (7 by maintainers)
Top Results From Across the Web
Blockchain For Everyone - Binance Academy
... from Binance Academy's standard-setting, interactive educational programs. Receive your NFT certificate after you finish the courses and complete quizzes.
Read more >Complete Binance Academy's Free Crypto Beginner Course ...
Complete Binance Academy's Free Crypto Beginner Course for an NFT Certificate · Binance Academy has just launched its first free online course!
Read more >Binance Academy: Learn All About Blockchain & Cryptocurrency
Interested in learning about blockchain, cryptocurrency, security, technology, or following along with tutorials? Binance Academy has all that and more!
Read more >How to Get Started With Binance Academy Courses
This NFT is a certificate showing that you have successfully completed a study track at Binance Academy. There will be different collections ...
Read more >Earn A Binance NFT Certificate, Mattel Launches A Hot ...
Binance To Give NFT-based Certificates As It Launches Free Crypto Courses - On Nov 17, Binance published free courses for its millions of ......
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
I get the same SSL errors on my linux box when using the python embedded in LibreOffice 5.3. Yet the system python works OK. Something to do with them using different versions of OpenSSL I think. Easy workaround was to add
ssl._create_default_https_context = ssl._create_unverified_context
somewhere early in the code before attempting any urllib calls. The workaround came from stackoverflow. Probably there are security implications to it but if you just want the public (no apikey) stuff to work with the least amount of f***ing around then it’s an easy win.
@walkjivefly it’s better to find and launch that install script to copy their bundled certificates to your LibreOffice environment, or configure LibreOffice somehow, otherwise you will indeed loose security with private calls. I’m not very familiar with LibreOffice, but if there’s a built-in terminal there, you can probably install those certificates inside it. Otherwise there should be an option in their preferences or configs. My 2 cents.