I get this error as well. It seems there’s a problem with WordPress Plugins database or something.
I am no longer seeing this issue. It seems to have been resolved.
In my case, it’s not resolved. I can’t access plugin websites neither… they show “502 Bad Gateway” error.
-
This reply was modified 5 years, 10 months ago by
bertuz.
Same error not working for me either
Actually, I am again seeing this error. Sorry for the confusion.
I also experienced the same thing
Same thing happening with me.
I noticed this problem after restoring one of my backups using UpdraftPlus Plugin, so I don’t know if it was just a coincidence or its actually the restoration that ruined it.
Although the restoration went smoothly without any errors so I don’t know if that was the case.
I have fixed the issue with mine. This is how I fixed it.
So what I did before the problem started to occur was I was doing backup & restore stuff with UpdraftPlus plugin. I was testing out to see If I could restore one of the backups, which happened smoothly for the most part, but there was one time where I saw an restoration failure and it suggested me to delete old directories. So I did that.
Anyways now when I went into my SFTP, inside wp-content folder, I saw some duplicate folders.
Folders example:
language
language-old
logs
logs-old
mu-plugins
mu-plugins-old
mu-plugins-old-old (yes there was a third one)
themes
themes-old
uploads
uploads-old
updraft
As you can see there were duplicates, so I removed all the ones that had “old” in it, like language-old, themes-old etc.
However at the moment I am unable to remove mu-plugins-old-old due to permission reason BUT I was able to delete mu-plugins-old (I don’t know whats going on there really).
So all the duplicates are deleted except for mu-plugins-old-old.
But now I am not getting the “An unexpected error occurred. Something may be wrong with WordPress.org or this server’s configuration. If you continue to have problems, please try the support forums” error and can now search the plugins normally.
Hope this fixes it for others, if not then I’m sorry you might have a different problem than me.
Goodluck
-
This reply was modified 5 years, 10 months ago by
prak786.
-
This reply was modified 5 years, 10 months ago by
prak786.
-
This reply was modified 5 years, 10 months ago by
prak786.
Problem is solved now. It seems it was only a WordPress Plugins database timely error.
yes, the problem is fixed now. Also as a workaround – it was possible to download a plugin zip file from the database and manually upload and activate it.
Going to mark this as resolved now.