Facebook Messenger API "URL COULD NOT BE VALIDATED"

Question

I'm trying to setup the Facebook messenger API and I'm getting this error when I attempt to add the WebHook:

The URL couldn't be validated. Callback verification failed with the following errors: curl_errno = 60; curl_error = SSL certificate problem: unable to get local issuer certificate; HTTP Status Code = 200; HTTP Message = Connection established

I've setup my NodeJS server using the code they provided in the tutorial. Here's the url: https://stackoverload.me/chatter/webhook

EDIT HERE'S THE RESOLUTION (someone wanted to see the code):

var express = require('express');

var fs = require('fs');
var https = require('https');

var app = express();
app.use(express.static('public'));

// SSL
https.createServer(
    {
        ca: fs.readFileSync(__dirname + '/server.ca'),
        key: fs.readFileSync(__dirname + '/server.key'),
        cert: fs.readFileSync(__dirname + '/server.cert')
    }
, app).listen(443, function() {
    console.log('Server is now running.');
});

// HTTP redirect to SSL
express()
    .get('*', function(req,res){
        res.redirect('https://example.com' + req.url)
    })
    .listen(80);

You’re missing an intermediate certificate in the chain, so your certificate can not be verified as genuine. https://www.sslshopper.com/ssl-checker.html#hostname=stackoverload.me has instruction on what to do. — CBroe, Apr 12 '16 at 19:48
@CBroe I am facing the same error, though I am deploying on parseapp.com, any idea? — dhaval, Apr 13 '16 at 13:55
I checked my SSL configuration from [sslshopper.com](https://www.sslshopper.com/ssl-checker.html#hostname=akillidergi.com) but I didn't see any mistake. Can you share your nodejs code? — ozgrozer, Apr 13 '16 at 19:50
Wow. Thank you man. You saved my day. There is no `ca: fs.readFileSync()` line in the nodejs documentation [page](https://nodejs.org/api/https.html#https_https_createserver_options_requestlistener) and this was the only problem. Now it works great. — ozgrozer, Apr 13 '16 at 20:22
Glad to hear :) You can thank the Namecheap support for that one haha — Jake Cross, Apr 14 '16 at 09:39

score 5 · Accepted Answer · answered Jun 23 '16 at 19:00

5

Forgot to answer this, but I found out that I added a ca file and parameter to my https server and Facebook then accepted it.

answered Jun 23 '16 at 19:00

Jake Cross

523
1
6
14

2

could you please explain more and print screen for your code.... i have the same problem – manhag Apr 24 '19 at 07:54

score 0 · Answer 2 · answered Jun 15 '17 at 06:56

0

You can use the chained certificate by the following shell:

cat www.example.com.crt bundle.crt > www.example.com.chained.crt

From http://nginx.org/en/docs/http/configuring_https_servers.html#chains

answered Jun 15 '17 at 06:56

magicpanda

66
3

Zameer Ansari · Answer 3 · 2017-09-30T15:44:50.500

Was trying to setup FB messenger webhook with a strong verify token. Somewhat like this: o\/ERviEE\/vt0|<E|\|

$o/ERviEE/vt0|<E|\| verify token set$

The same is been verified in the code:

req.query['hub.verify_token'] === 'o\/ERviEE\/vt0|<E|\|'

However, the value received from FB is: o\\/ERviEE\\/vt0|<E|\\|

$o\/ERviEE\/vt0|<E|\| verify token get$

This is strange. There seems to be no document reference as such which talks about how Facebook escapes special characters for verify tokens or alike. Not sure if this happens for other entities as well.

Conclusion: need to be a little bit cautious when using special characters for verify tokens.

Because, Facebook escapes special characters for webhooks' verify tokens.

Facebook Messenger API "URL COULD NOT BE VALIDATED"

3 Answers3

Linked