CODEWITHSUNDEEP
facebookhttpauthenticationinternal
David Runyon
David Runyon

Reputation: 33

HTTP 500 error when logging in facebook on web or mobile

I have been getting this error message the past 36 hours. Facebook support has not been any help at all when it comes to resolving this issue. I've cleared my cookies and cache multiple times. I've tried from multiple machines as well as my phone. Still no luck on logging in. Is it an error on my part or are they doing maintenance? Please assist, I did not want to have to post here but I have no more options...

The website cannot display the page HTTP 500
Most likely causes: •The website is under maintenance. •The website has a programming error.

What you can try: Refresh the page. 

 Go back to the previous page. 

 More information

This error (HTTP 500 Internal Server Error) means that the website you are visiting had a server problem which prevented the webpage from displaying.

For more information about HTTP errors, see Help.

Upvotes: 3

Views: 9511

Answers (2)

Chris Moschini
Chris Moschini

Reputation: 37957

Had the same problem. It appeared to be caused by this:

https://developers.facebook.com/docs/facebook-login/login-flow-for-web/v2.1#asking-for-permissions

Apps that ask for more than public_profile, email and user_friends must be reviewed by Facebook before they can be made available to the general public.

We were asking for more than the default, so I presume the 500 is caused by this lack of review.

It appears it can also happen if you haven't made your App public and try to login to it as anyone but you (the account that created the App).

Upvotes: 1

theabraham
theabraham

Reputation: 16370

It's probably something on their end. Responses with a 5xx status code are used when the server is aware it has erred in some way. More specifically, the 500 error has the following definition:

500 Internal Server Error:
The server encountered an unexpected condition which prevented it from 
fulfilling the request.

If the response had a 4xx status code, then the fault would lie on you. For example, if you made a request to a resource that doesn't exist, then you'd get a 404 response. As it stands now, something is wrong with their server.

Upvotes: 1

Related Questions