Skip to content
This repository has been archived by the owner on Jun 3, 2024. It is now read-only.

Facebook's hooks are blocked to ngrok? #427

Closed
Ricardo-Costa opened this issue Jun 21, 2017 · 39 comments
Closed

Facebook's hooks are blocked to ngrok? #427

Ricardo-Costa opened this issue Jun 21, 2017 · 39 comments

Comments

@Ricardo-Costa
Copy link

No description provided.

@famvisualarts
Copy link

I don't know what is exactly the origin of this issue, but u can quickly switch to machinabot.com , it's free , here is how to setup it, https://medium.com/inside-machinabot/from-dev-to-live-part-1-how-to-start-testing-and-debugging-your-bot-locally-in-one-minute-74e4e334a449

@bekatom
Copy link

bekatom commented Jun 21, 2017

@farahmaamar How long are you waited for invitation? I need asap and still waiting

@famvisualarts
Copy link

I just sent you an invite right now , check your inbox!

@rohansood42
Copy link

I think there is some problem with the us server. eu works fine with facebook

@jminuscula
Copy link

@inconshreveable there's a bug open on Facebook suggesting this is on the ngrok side. Could you please give us an update about what might be going on?

https://developers.facebook.com/bugs/824028317765435/

eu.ngrok is not working for me and a lot of people either

@musaturan
Copy link

@Ricardo-Costa @btomashvili You can also use https://www.chatbotproxy.com/ to debug and proxy your requests from Facebook Messenger. Free version covers proxy, debugging and metrics. Feel free to try.

@spnkr
Copy link

spnkr commented Apr 29, 2018

+1. this is really annoying.

@ikasymov
Copy link

ikasymov commented May 10, 2018

Use for alternative beame-insta-ssl
worked with facebook degub

@lukedubber
Copy link

Just ran into this issue as well.

@SirGordon
Copy link

SirGordon commented May 25, 2018

Why is this closed? It still doesn't work.

@chasms
Copy link

chasms commented Jun 12, 2018

Using a paid account specifically for rich meta validators and they 502 on my ngrok.io subdomain. Requests don't show up in the dashboard, so looks like they are blocked on the DNS/LB/subdomain side of things. @inconshreveable can we reopen this ticket?

@jamesr2323
Copy link

This is also happening to me. Facebook retrieves this for my URL:

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN" "http://www.w3.org/TR/REC-html40/loose.dtd">
<html>
<head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head>
<body><p>kErrorAddressPrivate</p></body>
</html>

@aacook
Copy link

aacook commented Sep 5, 2018

Me too. I'm a paying user. Is there any workaround?

@phbernard
Copy link

phbernard commented Nov 15, 2018

@inconshreveable Regarding the latest messages, this issue is still pending and should be re-opened.

Apparently Facebook did its job of making sure that FB does not block ngrok. It would be great if you could give it another check on your side.

@ninofiliu
Copy link

ninofiliu commented Mar 28, 2019

This is still an issue. Facebook open graph debugger is throwing Could Not Connect To Server: Curl error 56 (RECV_ERROR)

Other services like iframely have access to my <...>.ngrok.io without any issue

@ryancwalsh
Copy link

ryancwalsh commented Mar 30, 2019

Using Localtunnel instead worked for me: https://stackoverflow.com/questions/8569892/how-to-test-open-graph-on-localhost#comment97589973_46816051

@matthewhuang-camelot
Copy link

Indeed still seems to be an issue -- this should be re-opened. I'm a paying user as well

@roynasser
Copy link

+1 too... paying user

@hempels
Copy link

hempels commented Nov 1, 2019

+1 ... paying user

@yakoveka
Copy link

yakoveka commented Nov 9, 2019

+1 still doesn't work, returns 502 code

@AO-IO
Copy link

AO-IO commented Nov 11, 2019

Still doesn't work error 502

@ryanrutan
Copy link

Any updates to this one?

@siaen
Copy link

siaen commented Jun 26, 2020

This is still unfixed.

@yepelinux
Copy link

yepelinux commented Jun 4, 2022

I've found that facebook is blocking some requests

The url https://51bc-152-168-79-85.sa.ngrok.io/whatsapp/cloud-api/webhook has been identified as malicious and/or abusive.

in response to save webhook
image

image

@hadnet
Copy link

hadnet commented Jul 27, 2022

Facebook is blocking the use o ngrok. Tried to use it for social login provider and I get this message
Screen Shot 2022-07-26 at 10 44 16 PM

@ChesterSVK
Copy link

ChesterSVK commented Aug 3, 2022

+1 Here as well, used for social login, it has been working untill today for EU servers, US is working for now

@marcoaleixo
Copy link

+1 here still blocking ngrok.

@pgiu
Copy link

pgiu commented Oct 27, 2022

Still blocked :(

@leobaldoneto
Copy link

leobaldoneto commented Nov 9, 2022

Still blocking here too.

I think Facebook's webhooks are stucking in browser warning of Ngrok.

Bellow are the instructions to bypass the browser warning, but we can't control the how Facebook send requests to Ngrok.

image

Facebook is blocking the use o ngrok. Tried to use it for social login provider and I get this message Screen Shot 2022-07-26 at 10 44 16 PM

I think Facebook is blocking because the browser warning too.

@WableSanket
Copy link

Still blocked :(

@PSilvaCVT
Copy link

PSilvaCVT commented Nov 28, 2022

https://ngrok.com/docs/integrations/whatsapp/webhooks
as per ngrok docs (don't use the hostname param if you're not on a pro plan), pass region us.
This should work.

@pflajszer
Copy link

adding a param --region us (i.e. ngrok http 7071 --region us helped me with this.

@WableSanket
Copy link

@pflajszer @PSilvaCVT
Thank you very much.
Worked for me.🙌

@bnjunge
Copy link

bnjunge commented Dec 16, 2022

@pflajszer works

@gshubham533
Copy link

I changed my ngrok region to us and now it is working fine.

Example cmd : ngrok http 8000 --region us

@deven96
Copy link

deven96 commented Jan 10, 2023

@pflajszer you saved me a ton... thanks!

@nazruld
Copy link

nazruld commented Jan 18, 2023

adding a param --region us (i.e. ngrok http 7071 --region us helped me with this.

Thanks ... its working

@jakoguta
Copy link

I changed my ngrok region to us and now it is working fine.

Example cmd : ngrok http 8000 --region us

Adding the --region us worked

@suyash-purwar
Copy link

Add --region us and it will work. Thank you very much @pflajszer

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests