› Forums › SNAP – WordPress Plugin Forums › Facebook, "internal server error", and "admin-ajax.php"
- This topic has 10 replies, 2 voices, and was last updated 7 years, 1 month ago by walshmagger.
- AuthorPosts
- January 25, 2014 at 7:31 am #128257boah123Participant
Hi,
I use v3.1.2 of Next Scripts. I can auto tweet posts, but not to Facebook. Previous versions of Next Scripts had no problems with Facebook.
I found out that this is the error message: “Sending update to Facebook”, Failed to load resource: the server responded with a status of 500 (Internal Server Error) /wp-admin/admin-ajax.php
Any ideas how to solve this problem or how to obtain more info about it?
Thanks!
January 26, 2014 at 1:57 pm #128612You need to take a look at the http server logs for more info. Please contact your server admin or hosting provider if you don’t know how to do it.
February 3, 2014 at 3:44 pm #131167boah123ParticipantInside the logs I could not find more info. The error message in Chrome Webmaster Tools indicates that the problem originates inside jQuery v1.10.2. Possible?
February 5, 2014 at 9:00 pm #131680You need to see your server logs, not the logs from your browser.
February 6, 2014 at 12:36 pm #131908boah123ParticipantI did checked the server logs! But there is nothing to see. Are other options for me? Do you have, for example, a script to check if the server / site is plugin ready?
February 7, 2014 at 10:40 am #132130What do you mean “nothing to see”? When webserver throws “500 (Internal Server Error)” to the browser it always writes technical details about this error to the log. Those technical details contain information about the error and what file caused it.
February 8, 2014 at 11:06 am #132466boah123ParticipantSo far I can’t find a logfile with an error.
Inside this it goes wrong.
February 8, 2014 at 11:10 am #132467boah123ParticipantInside my post, I used my domain name. Could you please anonymise my second url to ‘mydomain’. TNX.
February 9, 2014 at 6:17 am #132690boah123ParticipantI’ve been able to obtain more info!
The 500 error code said:
“Invalid or no certificate authority found, using bundled information”.I’ve tried to re-authenticate and got this message:
-= This is normal technical authorization info that will dissapear (Unless you get some errors) =-Array
(
[http_request_failed] => Array
(
[0] => SSL certificate problem, verify that the CA cert is OK. Details:
error:14090086:SSL routines:SSL3_GET_SERVER_CERTIFICATE:certificate verify failed
))
-=
Array
(
[doFB] => 0
[nName] => mydomain.com
[fbAppID] => xxxxxxxxxxxxxx
[fbAppSec] => xxxxxxxxxxxxxxxxxxxxxxxxxx
[catSelEd] =>
[fbPostType] => A
[fbAttch] => 2
[fbAttchAsVid] => 0
[imgUpl] => 1
[fbMsgFormat] => %TITLE%
[fbMsgAFrmt] =>
[fbURL] => https://www.facebook.com/mydomain.com
[fbPgID] => mydomain.com
[fbAppAuthToken] => xxxxxxxxxxxxxxxxxxxx
[fbAppPageAuthToken] => xxxxxxxxxxxxxxxxxxxxx
[fbAppAuthUser] => xxxxxxxxxxxxxxxxxxxxxxxx
[catSel] => 0
[riComments] => 0
[riCommentsAA] => 0
[useFBGURLInfo] => 1
[rpstOn] => 0
[rpstDays] => 0
[rpstHrs] => 2
[rpstMins] => 0
[rpstRndMins] => 15
[rpstPostIncl] => 0
[rpstType] => 2
[rpstTimeType] => A
[rpstFromTime] =>
[rpstToTime] =>
[rpstOLDays] => 30
[rpstNWDays] => 365
[nxsCPTSeld] => a:1:{i:0;s:4:”post”;}
[rpstBtwDays] => Array
(
))
Array
(
[headers] => Array
(
[access-control-allow-origin] => *
[cache-control] => no-store
[content-type] => application/json; charset=UTF-8
[expires] => Sat, 01 Jan 2000 00:00:00 GMT
[pragma] => no-cache
[www-authenticate] => OAuth “Facebook Platform” “invalid_code” “This authorization code has been used.”
[x-fb-rev] => 1114696
[x-fb-debug] => qCht7rtw/aYImXyqxDR2vZjmSf+8UJ5kQL1ZLubG4Po=
[date] => Sun, 09 Feb 2014 11:02:54 GMT
[connection] => close
[content-length] => 97
)[body] => {“error”:{“message”:”This authorization code has been used.”,”type”:”OAuthException”,”code”:100}}
[response] => Array
(
[code] => 400
[message] => Bad Request
)[cookies] => Array
(
)[filename] =>
)After that, the test post on my Facebook page did work. I can also report to Facebook. However, the message “Sending update to Facebook” remains visible. As is the error message via Ajax in the browser (500 error).
So, on one had it is working and on the other hand it is not working how is suppose to be.
Any hints?
February 10, 2014 at 2:35 pm #133035The answer is in the FAQ – #4.4:
November 1, 2017 at 5:43 am #557103The first thing you need to know about an “Internal Server Error” is that the error can only be resolved by fixes to the Web server software. It is not a client-side problem meaning that the problem is not with our plugin. This is a ‘catch-all’ error generated by the Web server. Basically something has gone wrong, but the server can not be more specific about the error condition in its response to the client. In addition to the 500 error notified back to the client, the Web server should generate some kind of internal error log which gives more details of what went wrong. It is up to the operators of the Web server site to locate and analyse the logs which should give further information about the error.
- AuthorPosts
- You must be logged in to reply to this topic.