Saturday 11 March 2017

heroku local web ssl using self signed certificate

I'm using the heroku toolbelt to start a development version of my web server locally, e.g. heroku local web. This has always worked well enough, but I recently added https encryption to all pages of my site via the heroku addon expeditedSSL and express-sslify and localhost now shows this message in chrome

This site can’t be reached

localhost unexpectedly closed the connection.

I would like to add a local, self-signed ssl certificate for use when operating in a https localhost environment. I've read a few posts about creating self signed certificates that are supposed to work with node.js servers, but no matter what I try I always see the persistent chrome message.

I suspect my problems are somewhat sourced from what heroku local web actually does in starting up the web server. How do I get a local instance of a heroku server to use self signed ssl certificate?



via GrantD71

No comments:

Post a Comment