inconshreveable
x509: certificate signed by unknown authority
Hi,
While I am trying to run the ngrok file, I am getting the error as "x509: certificate signed by unknown authority". Earlier it was working fine. Currently I am working under proxy.
Config.YML file:
region: ap console_ui: true compress_conn: false http_proxy: "http://myproxy:8080" inspect_db_size: 50000000 log_level: info log_format: json log: D:/NGROK/ngrok.log root_cas: trusted update: true update_channel: stable web_addr: localhost:4040
@inconshreveable requesting you to help on this issue
Did you self-sign your certificates? If so, you'll need to add trust_host_root_certs: false to your configuration, in addition to have built the client using your self-signed cert.
Hi
To my understanding this issue occurs when proxy blocks ngrok domain.
Regards Siddiq Rehman
On 28-Feb-2018, at 2:32 PM, Federico Angaramo [email protected] wrote:
+1
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub, or mute the thread.
The cause of this issue is as @siddiq-rehman stated, if your proxy blocks the URL, ngrok gets a response back which it doesn't expect, which is a response from the proxy with a self-signed cert.
The current version of ngrok configuration no longer has trust_host_root_certs.
It may have been updated to root_cas.
I fixed the x509 issue by setting root_cas: host.
Perhaps this could help @azaeng04
The current version of ngrok configuration no longer has
trust_host_root_certs. It may have been updated toroot_cas. I fixed the x509 issue by settingroot_cas: host. Perhaps this could help @azaeng04
where do you set this?
@FLASH-99 In the config file https://ngrok.com/docs#config-location if there isn't one there, just create one and put root_cas: host at line 1.
Hi To my understanding this issue occurs when proxy blocks ngrok domain. Regards Siddiq Rehman … On 28-Feb-2018, at 2:32 PM, Federico Angaramo @.***> wrote: +1 — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub, or mute the thread.
I have self hosted the ngrokd server on aws. still i am getting this issue. also I am getting hits via proxy public IP address but not able to connect from client to server. Any work arounds?
The current version of ngrok configuration no longer has
trust_host_root_certs. It may have been updated toroot_cas. I fixed the x509 issue by settingroot_cas: host. Perhaps this could help @azaeng04
Were you working behind the client? did u use self-signed cert? did u self host the server or using ngrok domain itself
In the yml file, change root_cas: host to root_cas: trusted
Worked for me
Latest docs for locating your ngrok.yml file: https://ngrok.com/docs/ngrok-agent/config#default-locations
None of these methods helped for me either and my ngrok version at the time was 3.1.1.
The root cause was a proxy had silently been implemented. The solution was for the proxy admin to whitelist traffic to and from ngrok.
Thank you for opening this issue! As of April 2016, the ngrok service has permanently moved to https://ngrok.com/. To join the community and file bug reports or feature enhancements for the ngrok agent, please go to https://github.com/ngrok/ngrok.
This repository is no longer actively maintained and will be archived soon to reduce confusion with the latest ngrok versions. We thank you for the continued support of ngrok and look forward to seeing you over at ngrok.com and the ngrok Community Repo.
