I have a python program that connects to an API using the websocket client that has always worked fine but has not been connecting this morning on my windows 10 PC. I am aware of the DST Root CA X3 certificate expiration today and was having some issues connecting to a few websites from urllib, but I have since deleted the expired certificates from the "Intermediate Certificate" store and disabled DST Root CA X3 in the trusted store. By doing this, the issues visiting sites from urllib were resolved but the websocket API one persists. The certificate this API uses is a Globalsign Root CA R1 and the weird part is that I can reach the API just fine from my chrome browser and from piesocket.com/websocket-tester# but not my local PC using the python websocket client. I am lost here and was wondering if anyone knows anything about what the issue could be and how I can solve it? 

Certificate Issues Connecting to Websocket

I am including an HTTPS guide to an embedded Linux tool. I've attempted to generate a self-signed certificate with those steps:

openssl x509 -in cert.csr -out cert.pem -req -signkey key.pem -days 1001

How to generate a self-signed SSL certificate using OpenSSL?

I can push by clone project using ssh, but it doesn't work when I clone the project with HTTPS.

server certificate verification failed. CAfile: /etc/ssl/certs/cacertificates.CRT CRL file: none

ssl-certificate

Trending Blogposts on ssl-certificate

Popular Discussions on ssl-certificate

openCertificate Issues Connecting to Websocket

2

0

0

openHow to generate a self-signed SSL certificate using OpenSSL?

2

0

0

openServer certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none

3

0

0

PRODUCTS

QUICK LINKS

LEGAL