Viewing 8 replies - 1 through 8 (of 8 total)
  • I too am having the same problem. I disabled the plugin by removing the folder via FTP and now I can log in.

    Thread Starter Anita C

    (@mymothersdaughter)

    I was able to get in, but I don’t like having that error in my dashboard. Plus it’s slowing my site down and when I reset everything, now I cannot get the API Key back. It tries but times out.

    Hello, this is not a bug in the plugin, this is more likely an issue in your server. When the plugin executes an API call to our servers it sends a HTTP request with a timeout of ninety (90) seconds, if your site is not able to send a request during this time, then the error appears.

    I can not solve this issue, but I added an option in the Settings page where you can increase the number of seconds before throw the timeout error message, you can put 300 seconds (which is five minutes) if you want, but as I said, this is an issue in your site not the plugin.

    I added this new option here 978150, the new code will be available in the next version of the plugin 1.6.9, this update includes new options in the Settings and I recommend to go and check them.

    I have the same problem, I put on a 150-second al again the same problem.
    What needs to change on the server?

    SidneySch

    (@sidneysch)

    Same problem on 2 blogs, both in subdirectories. (No problem on 3rd blog, same host, diff server.) Tho I get API error, if I go to blog I can click “Site Admin” and get in … slowly. But I can’t get out: 1) Under WP News, says: “RSS Error: WP HTTP Error: name lookup timed out”. And Dashboard, says: “Warning: An unexpected error occurred. Something may be wrong with www.ads-software.com or this server’s configuration. If you continue to have problems, please try the support forums. (WordPress could not establish a secure connection to www.ads-software.com. Please contact your server administrator.) in …path…/wp-admin/includes/plugin-install.php on line 77” I just tried to update plugin and got same warning on update.php on line 295. I’ve spent days looking up all these error codes. One blog only 2 plugins: Sucuri & Akismet. Positive it is not anything I did. Both at WP 4.0. Are errors related? Any idea what to advise the host to check on server? Thanks!

    SidneySch

    (@sidneysch)

    Though reading how so many folks’ hosts didn’t want to help, I gave up late last night and sent in a support ticket. When I woke up they’d already responded with the fix: a resolver configuration issue on the server. If you’re getting some of my symptoms above, its almost definitely a server issue. Cheers.

    Andrew Clark

    (@createwow)

    While it says “server side” issues, when I disable Sucuri-Scanner, it allows me access to the sites with no delays. Is there a patch or a fix coming soon> This is VERY detrimental to our sites.

    caseyfern

    (@caseyfern)

    I’m getting the same API issue not only when I try to log in, but also when I try to do updates.

    Sucuri: Something went wrong with an API call (send_log action): connect() timed out!

    So far the only resolution has been to disable Sucuri. My host is pointing this back at Sucuri.

    What else can I do?

Viewing 8 replies - 1 through 8 (of 8 total)
  • The topic ‘ERROR: Something went wrong with API’ is closed to new replies.