Trynig to create Encrypted websockify connections

[DeliDumrul43]

Hi to all ,

#467 I read this disccusion to have knowladge then I read https://github.com/novnc/websockify-js documention page to start websockify server with wss option and I did that now I can able to start the websockify with wss option but now webadb throw a error

Executing the websockift :

After this page it gave a problem that seen below,

Error , What I am doing wrong ? Please help me out.

[DeliDumrul43]

I got same problem with my localhost when I used wss option normally it would connect If I use ws option

[DeliDumrul43]

I inspected the web page warnings and I got these ones

@yume-chan

Thanks in advance

[yume-chan]

That's from Google AD, from the copycat version you are using. My website doesn't have any tracking and AD.

[yume-chan]

Make sure you entered the correct Common Name when creating the certificate using OpenSSL, that should match the IP address you are connecting (192.168.81.25 in your case). If you created a certificate for 192.168.61.25, it won't work for localhsot. Technically one certificate can validate multiple domains using "Alternative Names", but I don't know how to add them using OpenSSL, you may Google yourself.

[DeliDumrul43]

I am sure that was the correct IP address and I tried localhost on my PC so wss option didn't work then my created .cer file is not valid.

[yume-chan]

Also make sure you installed/trusted the self-issued certificate on your current PC, usually that requires you to export the certificate into .cer format, then open and import it.

[DeliDumrul43]

I created it I didn't install and pay it to have. So my .cer file is not the valid, right ?

[yume-chan]

Not paying doesn't mean the certificate is invalid. There are free certificate issuers like Let's Encrypt, however they will only issue certificates for domain names, not IP addresses.

Your self-issued certificate is invalid because it's not from a trusted certificate issuer. Browsers trust those certificate issuers, so they also trust all certificates they issued.

But you can still trust your certificate on your own devices by adding it to the certificate store. First extract the public key using

openssl x509 -in self.pem -out self.cer

Then copy the cer file to your device running the browser, open it, and operate according to the display, or Google for your OS for detailed steps.

[DeliDumrul43]

Thanks for the information that you told I didn't know it , I am trying now