Ngrok: Ngrok Just Went Down

Created on 1 Apr 2020  ยท  73Comments  ยท  Source: inconshreveable/ngrok

Has been working fine all morning and all of a sudden it shows Internal Server Error: ERR_NGROK_802

Any thoughts?

Most helpful comment

Seems an outage is local to US region, adding region switch like --region eu makes it work.

All 73 comments

Same here, just now.

Same here.

Same here

+1

same here

Same here it fails with internal server error ERR_NGROK_802

same here ๐Ÿค”

Seems an outage is local to US region, adding region switch like --region eu makes it work.

I put this --region eu in grok command and works for me

i put the --region eu and it worked for me too

saviors ๐Ÿ™Œ

It's back up !

US region is normally now. ๐Ÿ‘

Back down for me! I was going mad lol

same any idea?

Also experiencing the same issue.

Same here thanks mksh adding -region=eu in _windows_ solved the issue

Closing this issue as normal functionality has been restored. Thank you!

seems to be happening again in US as well.

Looks like same here again. --region=eu fixed the problem

yeah, down again here too.

mine's down again too

down again

I am still seeing this aswell

Just went down, working fine earlier today, even eu region not working

down!!

Same

Please check @maxtomczyk post above ๐Ÿ‘†๐Ÿป That solved for me.
./ngrok http 3000 --region=eu

Very Very Down!

Down for me too

Specifying --region=eu should work now

but using -region =eu change a URL to URL.eu.ngrok.io

but using -region =eu change a URL to URL.eu.ngrok.io

So what?

Specifying --region=eu should work now

It's working well ๐Ÿ˜„

but using -region =eu change a URL to URL.eu.ngrok.io

So what?

i was using my ngrok url in different callbacks and i have to re-validate all of them

Looks like same issue is happening again. @davej

but using -region =eu change a URL to URL.eu.ngrok.io

So what?

i was using my ngrok url in different callbacks and i have to re-validate all of them

Try to make a variable where you will store ngrok url and use that variable in your callbacks.

but using -region =eu change a URL to URL.eu.ngrok.io

So what?

i was using my ngrok url in different callbacks and i have to re-validate all of them

Try to make a variable where you will store ngrok url and use that variable in your callbacks.

yeah I know that, i mean i have to put the new url in all platforms my system uses like
google, facebook, twilio and so on

+1

+1 Also here

+1 Also having issues, I use a hostname so unable to change regions

+1 just went down about ~5 minutes ago

+1

On Thu, Apr 2, 2020 at 6:27 PM Luca Garulli notifications@github.com
wrote:

+1 Also here

โ€”
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/inconshreveable/ngrok/issues/650#issuecomment-608123965,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ADGJVMJM2EM6M7PBHTTSYDDRKUGNPANCNFSM4LZPE2HQ
.

+1, using switch -region=eu causes error:

Failed to bind the address '1.tcp.ngrok.io:XXXXX' in region 'eu' because it is reserved
in the 'us' region.

yesterday, the system came back up in about an hour, so we'll see I guess.

+1

down for me too

+1

And I just got done saying how useful this tool was to our engineering manager. :disappointed:

down for me too

US down

Same here tried mobile hotspot, flushing DNS, restarting, reinstalling and re authentication.

Session Status                reconnecting (dial tcp 18.189.209.170:443: connect
Session Status                reconnecting (dial tcp 3.20.111.144:443: connect: 
Session Status                reconnecting (resolved tunnel.us.ngrok.com has no records)                    

edited
worked with --region eu.

+1

Same issue. Is there a way to get a notification when things go down?

Or, what's the easiest way to check status?

it's back up for me

Error not working
internal server error

ERR_NGROK_802

Try using --region eu. Outage in us.

reconnecting (internal server errorERR_NGROK_802)

It seems to be cutting in and out intermittently. I signed up for a pro account and reserved urls in eu and jp but neither are working atm

back again for me!

covid-19 infected ngrok's us region :)))

use: ngrok http 8000 --region=eu

Starting ngrok with --region=eu doesn't help if external access to the tunnel needs to be fixed URL.

If the URL needs to change, it's not useful for my application.

Or am I missing something? (simply adding that flag didn't help)

Issues connecting as well. Unfortunately cannot connect to EU region without reconfiguring because my team is running on reserved tunnels in US region.

Would appreciate some communication+status updates from the Ngrok team!

This issue was closed. Shoud a new one be opened?

@saharshjain closing without a resolution?

I already want to buy an ssl certificate((

It just happened to me now. It was working fine until about ten minutes ago.

Fixed :)

I think we came back with the same problem ...

Down again ! Was working fine till morning.
Initially before a hour i was getting the error "Target machine actively refused" and now i am getting

internal server error
ERR_NGROK_802

happening to me as well. i have tried to restart several times without success

internal server error
ERR_NGROK_802

EU Just went down I think.

ngrok start webhook
internal server error

ERR_NGROK_802

They really lack a status page, don't they? Crazy unprofessional to not have one as a dev-tool...

Up again EU

Was this page helpful?
0 / 5 - 0 ratings

Related issues

owlstack picture owlstack  ยท  5Comments

zero-master picture zero-master  ยท  6Comments

ricardopieper picture ricardopieper  ยท  3Comments

alexforever86 picture alexforever86  ยท  5Comments

jabooth picture jabooth  ยท  5Comments