Quantcast
Channel: Active questions tagged https - Stack Overflow
Viewing all articles
Browse latest Browse all 1491

SignalR connection throws ERR_CERT_COMMON_NAME_INVALID on connection (self-signed cert)

$
0
0

I am developing an application and I am using self-signed certificate.Everything works fine until I try to connect to signalR hub.

constructor(private http: HttpClient) {  this.signalingHub = new signalR.HubConnectionBuilder()    .withUrl('https://192.168.1.105:5142/signaling', {    })    .build();}

I can't connect to hub if I am using my static IP address.Browser throws ERR_CERT_COMMON_NAME_INVALID error.however, it connects well if I write (https://localhost:5050)

I've tried to generate certificates properly, but still getting this error. Is there any configuration to say signalR to skip certificate validation?

and this is how I create my certificate

[req]default_bits = 2048distinguished_name = req_distinguished_namereq_extensions = req_extx509_extensions = v3_reqprompt = no[req_distinguished_name]countryName = AUstateOrProvinceName = NSWlocalityName = SydneyorganizationName = Self-signed certificatecommonName = 192.168.1.10[req_ext]subjectAltName = @alt_names[v3_req]basicConstraints = CA:FALSEkeyUsage = nonRepudiation, digitalSignature, keyEnciphermentsubjectAltName = @alt_names[alt_names]IP.1 = 192.168.1.10

Viewing all articles
Browse latest Browse all 1491

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>