Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Callback Verification Failed #40

Open
atindersaini opened this issue Nov 7, 2016 · 6 comments
Open

Callback Verification Failed #40

atindersaini opened this issue Nov 7, 2016 · 6 comments

Comments

@atindersaini
Copy link

Hey Jerry,

I am getting the below error even though my heroku app is accessible. Please help!

The URL couldn't be validated. Callback verification failed with the following errors: HTTP Status Code = 502; HTTP Message = Bad Gateway

Thanks.

@AustinTing
Copy link

My partner and I used this tutorial, and he succeeded but I failed.

We are trying figuring out what is going on....

@marquavious
Copy link

@AustinTing any clue as to what is going on?

@AustinTing
Copy link

@marquavious we think that there is weird in heroku. We followed the tutorial and created three heroku projects but two projects slept(ZZZ icon in heroku console). Those which slept projects are not accessible. If you can link heroku project by your browser directly, you will have high opportunity success in Facebook. But sometime fails even if use the same heroku link(Facebook accepted before)

@joseignazuleta
Copy link

Hi guys, I had the same problem following the tutorial and the problem was that when you create the Procfile with the sentence "web : node index.js" Heroku try to execute ": node index.js". That causes the app to crash.
Simply remove the : from the file and it will work.

@5aharsh
Copy link

5aharsh commented Dec 27, 2016

I was facing the same problem. Later I found that some how my Procfile was having .txt as extension. I removed it, added, commited, pushed and it worked like a charm. Content inside Procfile is web: node index.js

@luizcartolano2
Copy link

anyone knows how to fix this "Bad Gateway" error?

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

No branches or pull requests

6 participants