-
Notifications
You must be signed in to change notification settings - Fork 13
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
how I can change the value of verify_ssl? #31
Comments
Hi @gts-work, That can't be overridden right now, you'd have to run a forked copy of mux-python with the Can you give me some understanding of what you looking to achieve by disabling TLS verification? Thanks! |
Hi @geneticgenesis, I added But I still get the "MaxRetryError" error. We use letsencrypt SSL certificate |
Hey @gts-work, thanks for the reply. The best way to resolve this issue is to resolve the issues with the (likely outdated) root certificates on the underlying system. Tying yourself to a specific chain will potentially cause issues in the future if we change our certificate chain. Do you have any more details about the environment you're running in - OS, python version, etc. Thanks. |
Ubuntu 18.04.3 LTS (GNU/Linux 4.15.0-117-generic x86_64) |
Thanks @gts-work, We've tested here, please can you run Thank you. |
@geneticgenesis |
Hey @gts-work, Not currently, each video needs to be uploaded individually - product questions like this are best sent to the Mux team at Were you able to get the Python environment issues resolved? Thanks! |
No, I checked the certificate, it is valid, but I still get a certificate error. I made a fork and tuned it to the project. |
Thanks, were you able to update the truststore on the machine you're running on as I suggested? |
I checked the certificate, it is valid, but I still get a certificate error. I made a fork and tuned it to the project. |
Which certificate did you check? The verification is against the Mux server side certificate, but you need valid root certificates on your local machine, which you don't appear to have. Based on our testing, using |
Yes, I did. On the server side, everything is fine. The certificate is physically on the server, but I still got an error. |
Thanks @gts-work. I'm concerned there's an issue with your local python configuration as this wouldn't be happening otherwise. You should never need to use a custom trust store or disable TLS verification to use mux-python on the configuration you've described. I do not recommend running with verify TLS disabled as there will be security implications, running in a fork will also make it harder for you to pull in updates to the library. We've tested and verified this package works correctly on Ubuntu 18.04.3 LTS with Python 3.6.9, when using an up-to-date ca-certificates. Please can you try removing the If this doesn't work, please can you post the output of the following command:
|
Package: ca-certificates N: There is 1 additional record. Please use the '-a' switch to see it |
Hey @gts-work, Thanks, we've tested again and confirmed this package works correctly on Ubuntu 18.04.3 LTS with Python 3.6.9, when using an up-to-date ca-certificates. We've also tested a couple of containerised versions, which work correctly. Can you try running the following command for me:
Thanks. |
Hi @geneticgenesis, I am getting the exact same error and here is the result of running that command you shared. `root@localhost:~/kivilcimyolla# openssl s_client -connect api.mux.com:443 -verify_return_error -status </dev/null 2>&1
|
@geneticgenesis root@localhost:~# openssl s_client -connect api.mux.com:443 -verify_return_error -status </dev/null 2>&1 CONNECTED(00000005)
|
Inactive - closing |
I think we need to re-open this - the action item should be for us to pin a more updated version of It's hard to know what version that should be without input from the users who were having issues, but I think with a little research, we could come to an educated decision - it shouldn't be too hard to work out from what version of |
Just as an FYI: I ended up hitting this on |
mux-python/mux_python/configuration.py
Line 173 in c2df765
maybe you need to add this variable to the Configuration Constructor parameters so that it can be initialized when creating the API?
def __init__(self, host=None, ..., verify_ssl = True)
and then:
self.verify_ssl = verify_ssl
The text was updated successfully, but these errors were encountered: