Closed vitekzach closed 5 years ago
Hi - this error vaguely rings a bell but I’ll need to look back through some old issues to find out why. I’ll take a look sometime this morning and get back to you 🙂
RE: Disabling verification - the short answer is to set verify=False
on the underlying Session
object used by seqlog. This isn't explicitly supported at present (the Session
is not exposed) but should be pretty easy to implement.
BTW, I think Python on Windows doesn't necessarily use the same CA certificate store for SSL verification as your browser would.
It's been a while since I worked with this stuff but I think this link is still accurate:
https://stackoverflow.com/a/52961564
(not so much to override the CA certificate list file's path but see where that list file is in the first place)
Hi, thanks for the suggestion!
I am not a big fan of turning off the verification, especially since it involved editing the package.
I found another solution though - requests uses package called certifi that has a list of certificates, so all I had to do it export the relevant certificate (in my case root) in base-64 encoding and appending it to the cacert.pem file that is inside the certifi package.
Description
I am trying to log events using seq on my python application. The logging fails on certificate verification.
I do have the certificate, because GET requests work as expected (e.g. I can browse logs in seq in browser).
What I Did
When I run seq locally, it works. When I try to reach seq deployed on a server, it fails on certificate verification.
Here is the trace of the error I get:
Is there a way of turning off SSL verification?