Ngrok: Facebook's hooks are blocked to ngrok?

Created on 21 Jun 2017  路  23Comments  路  Source: inconshreveable/ngrok

Most helpful comment

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

All 23 comments

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

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

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

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

@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

@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.

+1. this is really annoying.

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

Just ran into this issue as well.

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

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?

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>

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

@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.

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

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

+1 too... paying user

+1 ... paying user

+1 still doesn't work, returns 502 code

Still doesn't work error 502

Any updates to this one?

This is still unfixed.

Was this page helpful?
0 / 5 - 0 ratings

Related issues

owlstack picture owlstack  路  5Comments

asukiaaa picture asukiaaa  路  5Comments

shubhamk1997 picture shubhamk1997  路  5Comments

patcoll picture patcoll  路  5Comments

jabooth picture jabooth  路  5Comments