gruntjs/grunt-contrib-connect

Default SSL certificate are missing a common name

oliamb opened this issue · 2 comments

When using https protocol option, a default self-signed certificate is provided.

This certificate is missing a common name so Chrome don't trust it even if we follow the procedure in the README.

I would suggest to use localhost as common name in the default SSL certificate. What do you think?

I've been seeing this problem as well.

NET::ERR_CERT_COMMON_NAME_INVALID

This server could not prove that it is localhost; its security certificate is from 0.0.0.0. This may be caused by a misconfiguration or an attacker intercepting your connection.

Following the instructions in the note here did not help:

https://github.com/gruntjs/grunt-contrib-connect#support-for-https--http2

I had to create my own certificates for localhost.

PRs welcome to fix this.