localhost You will never be issued a proper https cert for localhost. It is strictly forbidden. Because reasons. In short: Misconfigured devices actually exist, in the wild, that wait for lookups before resolving localhost from /etc/hosts If a router defines localhost.foo.local it may cause localhost to resolve incorrectly (you’ve probably seen this class of error … Read more
Windows 10 users: Repair is only in the Control Panel, not in the Add Remove programs app. I typically run appwiz.cpl to launch the old control panel applet and run repair from there. Windows 7 and 8.1: After going to Add/Remove Programs and choosing the “Repair” option on IIS Express, the certificate has been reinstalled … Read more
You try to add certificate and expect that it will be private key – its confusion between two different things. Generally, when you create keystore (.jks) it include the private key inside. If its empty (deleted) you should generate bundle (.p12 file) from your key and certificates. In order to create new free key and … Read more
This produced a lot of output. In the middle of the output was the following: verify error:num=20:unable to get local issuer certificate verify return:0 You are missing a root certificate, and it should be specified either with -CAfile or with -CApath. However, you may encounter a handshake alert after you fix the root certificate issue. … Read more
Mount the certs onto the Docker container using -v: docker run -v /host/path/to/certs:/container/path/to/certs -d IMAGE_ID “update-ca-certificates”
The WebSocket connection starts its life with an HTTP or HTTPS handshake. When the page is accessed through HTTP, you can use WS or WSS (WebSocket secure: WS over TLS) . However, when your page is loaded through HTTPS, you can only use WSS – browsers don’t allow to “downgrade” security.
I was getting ERR_CONNECTION_RESET because my Visual Studio 2013/IIS Express configured app port number was NOT in the range :44300-:44398. (I don’t recall having to dismiss any warnings to get out of that range.) Changing the port number to something in this range is all I had to do to make it work. I noticed … Read more
Just to note that nginx has now support for Websockets on the release 1.3.13. Example of use: location /websocket/ { proxy_pass ​http://backend_host; proxy_http_version 1.1; proxy_set_header Upgrade $http_upgrade; proxy_set_header Connection “upgrade”; proxy_read_timeout 86400; } You can also check the nginx changelog and the WebSocket proxying documentation.
I was able to convert pem to crt using this: openssl x509 -outform der -in your-cert.pem -out your-cert.crt