(self-hosted) ngrok doesn't work with certs issued by GoDaddy about ngrok HOT 6 CLOSED

This is because of issue #53. Right now, you can fix this by recompiling the ngrok client and changing this file:

https://github.com/inconshreveable/ngrok/blob/master/src/ngrok/client/tls.go

The problem is the hardcoded "ngrokd.ngrok.com". If you change this to "ngrok.mydomain.ru" it will work. I'm going to push a fix for this in the next day. It should just be a matter of passing through the hostname part of the address.

from ngrok.

I've changed "ngrokd.ngrok.com" --> "ngrok.mydomain.ru" on the client though I'm still getting the same error messages.

from ngrok.

hrmmm, okay. I'm going to take a deeper look

from ngrok.

Any change on this subject? Ran into the same problem.
Change the code as mentioned above but no luck there too.

from ngrok.

Sorry, I've been caught up in other things, I'm going to try to take a look at this tomorrow.

from ngrok.

@timvdl @vlebedev

Okay, so after looking at this more carefully, there is one issue with ngrok and one problem with your configuration:

The ngrok issue was #53, which is now fixed. You shouldn't need to modify the source code any more to change the TLS configuration because it will extract the right server name from the server_addr you pass in the configuration file.

The fix for the configuration error you're running into is mentioned in the self-hosting doc:
https://github.com/inconshreveable/ngrok/blob/master/docs/SELFHOSTING.md

Specifically, you need to specify the following in your ngrok configuration:

trust_host_root_certs: true

This instructs ngrok to use your host's root certificate authority pool to validate the TLS connections because by default, ngrok only recognizes the certificate authority for ngrok.com. Alternatively, you can recompile ngrok if you replace assets/client/tls/ngrokroot.crt with the proper root certificate, but that's more advanced.

from ngrok.