When I try to access my plugins menu... my admin panel goes really slow. Plus when I try to go to the add plugin menu I get an API error and cannot add any plugins. This worked fine after the 3.3 install... but it's randomly not working now. Is this a wordpress server issue or is it an issue on my end?
[resolved] Plugin menu in admin area gives API error (16 posts)
-
xanaftp
Posted 5 months ago # -
Posted 5 months ago #Additional info: Now I can barely use the admin interface without a VERY SLOW connection. I get "RSS Error: WP HTTP Error: name lookup timed out" pretty much in every place that relates to the actual wordpress website (like wordpress blog, wordpress news, et cetera). Still getting same error for plugins.
Anyone have any info or suggestions on this problem? Please respond ASAP if possible. Thank you!
-
Try:
- switching to the Twenty Eleven theme by renaming your current theme's folder in wp-content/themes and adding "-old" to the end of the folder name using FTP or whatever file management application your host provides.- resetting the plugins folder by FTP or phpMyAdmin.
-
Posted 5 months ago #The themes thing did not work... but how do I "reset" the plugins folder?
EDIT: Okay I know what you mean by reset. I reset the plugins but that still did not work. With all plugins deactivated, I still get RSS errors and API errors.
-
Try re-uploading all files & folders - except the wp-content folder - from a fresh download of WordPress. Also check your server's error logs for any clues.
-
Posted 5 months ago #I even tried that... and nothing is showing up in apache2 or php. Still same errors.
I tried chowning to apache2 user and group and chmodding everything so the webserver and php can access it. No good.
-
It's beginning to sound like this is a server issue but I'm afraid I don't have any idea how you could even begin to troubleshoot it. :-(
-
Posted 5 months ago #It might have something to do with the new DSL modem configuration that I had to do just so outside sources could access my website. But I don't see how that would be a problem when everything else works on the network and internet.
-
Sorry but if that's the only thing that's changed, then it has to be top of the list of potential culprits.
-
Posted 5 months ago #This is a copy from another thread I thought was mine but wasn't so I accidentally posted a reply there:
I cannot fix this issue with cURL... any suggestions?
I installed Core Control on WordPress and disabled cURL. The only other transport option is PHP Streams... for some reason php fsockopen is not available even though it is enabled in php.ini .
However I HATE php streams transport... it's SLOOOWWWW! It takes almost 30 seconds to load the add new plugins page... and 30 seconds every time I search for a plugin or go to the next page.
I want my curl back!
Tried reinstalling curl, php5, php5-curl, it all did not work. Tried reconfiguring my internet router... did not work! Disabled all plugins... did not work! Replaced wp-includes and wp-admin... did not work!
By the way do not know if I mentioned this... but this problem started very randomly.
-
Posted 5 months ago #After checking settings... it's not cURL causing the problem. It's something else. ALL transports (PHP Streams, PHP fsock(), and cURL) are taking over 20 seconds to resolve an address. I do not know why... because normal http requests from my web browser are only a couple seconds. This only happens with the server.
Does anyone have any ideas?
-
I didn't see anyone mention simply deactivating all plugins, forgive the simplistic suggestion but I often find the simple things get overlooked, particularly by those with the most coding knowledge!
-
Posted 5 months ago #I don't know if I mentioned... probably it was in another thread... but I already tried that.
-
Do you have other sites installed on this hosting account? are they slow too?
Still this woudn't account for the inability to add plugns, but maybe..
-
Posted 5 months ago #I do not have other sites on this host... so I couldn't tell you.
-
Posted 5 months ago #UPDATE: I have no idea what the problem was... I was fiddling with my computer reinstalling things and resetting the local network and... now it works.
Interesting... I have no idea what the problem was. It might have been an issue with routing of the IP address.
Regardless cURL is now working and speeds are back to normal.
Thanks for the help!
Reply
You must log in to post.
