Ngrok 502 bad gateway как исправить

Quite new to using any sort of Web App stuff, and I’ve been trying to slowly build a Facebook Messenger Bot. When I try to use ngrok I can’t visit the address I’m given, i.e:

ngrok http 5000

is what I’m putting in the command line, and it’s returning this:

ngrok by @inconshreveable

Session Status                online
Version                       2.1.18
Region                        United States (us)
Web Interface                 http://127.0.0.1:4040
Forwarding                    http://ea986ca5.ngrok.io -> localhost:5000
Forwarding                    https://ea986ca5.ngrok.io -> localhost:5000

Connections                   ttl     opn     rt1     rt5     p50     p90
                              0       0       0.00    0.00    0.00    0.00

But when I take the address ‘https://ea986ca5.ngrok.io’ as is required by the Facebook developer’s page, it says:

The connection to http://ea986ca5.ngrok.io was successfully tunneled to your
ngrok client, but the client failed to establish a connection to the local  
address localhost:5000.


Make sure that a web service is running on localhost:5000 and that it is a 
valid address.


The error encountered was: dial tcp [::1]:5000: connectex: No connection 
could be made because the target machine actively refused it.

Is it a problem with my local port? Thanks!

asked Nov 14, 2016 at 21:51

Just as @njzk2 should have said, if you don’t have a web server running so it cannot work. I would like to make it clearer to you, if you are still confused.

What ngrok does, is to make your local server (running on localhost) to be available to the outside world (rest of the internet). On its own, it is not a web server. So for your bot development you need to have a web server running on a defined port (which in your case is 5000). Then you can point ngrok to this port so that it will redirect requests sent to your public address to the program running on that port.
The web server will then accept and handle requests from Facebook

answered Dec 16, 2016 at 3:55

It seems that this issue has now been resolved in the latest version of ngrok: https://github.com/inconshreveable/ngrok/issues/448

Basically, what you do is to specify that you are using https like this:

ngrok http https://localhost:54321 -host-header="localhost:54321"

At least, this resolved the issue for me. Replace 54321 with your actual port number.

answered Apr 14, 2020 at 7:17

answered Feb 15, 2019 at 17:38

For me, switching the protocol from http to tls worked since I am forwarding only a secure connection. I didn’t need to rewrite the header.

Just for context, I am forwarding a connection to a running docker container on Ubuntu 16.

PS: You still access the address using https in the browser, not tls.

answered Jul 30, 2018 at 14:08

MAKE SURE SERVER LISTENS ON THE SAME PORT WHERE NGROK IS TUNNELED

In my case I was running ngrok using ‘ngrok HTTP 3002’, while my express server was running at port 5000, hence throwing BAD GATEWAY error.

I restarted ngrok on port 5000 and it worked like a charm.

answered Mar 3, 2021 at 1:04

502 gateway error occurs because ngrok not able to receive any reponse from Localhost.

The things need to be done is :

1. Start a webserver in a Port
2. Trigger ngrok command in that Port.

What I have done is

• Started a tomcat Web Server in 8080.
• Then Triggered ngrok http 8080.

It works really cool …
Try this …..
Hope it works for You .

If you just with to use ngrok to intercept incoming data, and you do not have a local webserver for whatever reason, then you can use ncat.

nc -l 5000

This will create a process that listens on port 80.

So when used in combination with

ngrok http 5000

You will no longer get the ‘502 bad gateway’ error.

answered Nov 9, 2019 at 0:14

I had to put my server ip address and works perfect!

./ngrok http [ip server]:5000

answered Aug 17, 2020 at 23:21

i had the same issue,

because, i forgot to run the localhost:3000 port, which was supposed to be running some node server.

after i run node server, then i run, ngrok http 3000, so that it will cloud that node server in ngrok for globally access in internet.

answered Feb 28, 2021 at 18:09

I have solved the issue by killing the processes. Only 4 processes are allowed.

First command top to see your streamlit processes. You will see:

PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND

Just type kill PID [PID VALUE] and re-run the cell.

answered Jul 26, 2021 at 9:58

I finally made it 😭

ngrok http 80 

and then start another service on ur localhost:80… in my case, I use these

php -S localhost:80

and for reverse shell stuffs ..

nc -nlvp 80

Your problem is now fixed. ^_^

answered Mar 5, 2022 at 11:43

Sometimes what causes this error is your firewall that is blocking the connection.
to access the firewall in windows:

1. press win +r
2. type in firewall.cpl
3. go to allow apps through windows defender
4. below tap on allow another app.
5. locate the ngrok.exe file.

This worked for me.

answered Jul 15, 2022 at 13:24

answered Feb 16 at 5:50

I found it the hard way to solve this issue.

1. Make sure you use the correct port and «then» use ngrok (eg.3000). You have to run both ngrok and node simultaneously.
2. Use correct endpoint on both code and on the Callback URL
3. The response is a big json and you have to return req.query["hub.challenge"] as an Integer/Number.

Tip: Use ngrok http 127.0.0.1:3000

answered Apr 10 at 14:26

This error can occur if you have an HTTP rule to redirect HTTP to HTTPS.

You can disable this for your developer machine or add a custom rule based on the X-Original-Host header:

I’m using the IIS rewrite plug-in and this is how I fixed it

 <rule name="Redirect to https" enabled="true" patternSyntax="ECMAScript" stopProcessing="true">
            <match url=".*" negate="false" />
            <conditions logicalGrouping="MatchAll">
              <add input="{HTTPS}" pattern="off" />

              <add input="{HTTP_X_Original_Host}" pattern="yourngrokname.ngrok.io" negate="true" />             

            </conditions>
            <action type="Redirect" url="https://{HTTP_HOST}{REQUEST_URI}" redirectType="Found" />
          </rule>

answered Sep 17, 2017 at 6:54