Interruzione parzialeshare-external
I am not able update the callback url in webhook configurations
1

While update the call back url, I am getting the error like this:

"The callback URL or verify token couldn't be validated. Please verify the provided information or try again later".

Wharm
Chiesta circa 6 mesi fa
Risposta selezionata
1

Try to debug it on your end first (check your logs and so on) and provide more information than just the error message afterwards.

28 maggio alle ore 01:17
Lars
Wharm

Hi Lars, we are getting the error message like

'The URL couldn't be validated. Callback verification failed with the following errors: curl_errno = 35; curl_error = OpenSSL SSL_connect: SSL_ERROR_SYSCALL in connection to domain:port ; HTTP Status Code = 200; HTTP Message = Connection established'.

30 maggio alle ore 03:28
Lars

… on your end. Also try to search for the Curl error, which is most likely related to a SSL config issue on your end.

30 maggio alle ore 03:35
Wharm

SSL is working fine, it is provided by 'GO DADDY'

30 maggio alle ore 03:41
Lars

Debug it on your end

30 maggio alle ore 03:46
Karlus

I'm facing the same error and also using ngrok...

12 giugno alle ore 01:50
Miamie

same here, no official communication on why ngrok is blocked

13 giugno alle ore 00:21
Bruno

Same here. I am configuring a webhook for the first time. I managed to create the Ngrok free URL, and I can access it through the browser. However, "verify and save" on the Meta for Developers website has no effect and gives this error. There is no other information. I am guessing it is some security issue that doesn't even try to access the URL at ngrok-free . app.

13 giugno alle ore 05:47
Lars

ngrok-free . app is blocked by FB, so don't use it.

13 giugno alle ore 05:48
Oduyemi

I'm having the same issue with webhook, even apps deployed on Glitch, vercel is returning the same error which was not so few months ago.

I'm sure this is n update bug, I hope Facebook support will look into this

26 giugno alle ore 02:41
Oduyemi

So i was able to resolve it using port forwarding feature on VS code, i forwarded the port and changed the visibility to public

26 giugno alle ore 05:31
Luv

same issue

24 settembre alle ore 04:00