Discovered the source of the problem. The target site has been completely removed from the server. The only workaround I’ve found is to update each site individually. So, if a site in the list has actually gone away, that breaks the UpdraftCentral Dashboard.
This is not resolved. This continues to be a problem (bug).
If a target site has been deleted, Updraft Central fails to handle that error condition and locks up the Dashboard. The latest update to Updraft Central did not fix the problem.
Apparently, I will have to uninstall Updraft Central and then reconfigure the 40 websites with a fresh install of Updraft Central.
Hi @pwforaker
Apologies for the late reply.
I believe you have a UpdraftCentral subscription? If so, can you please open a ticket using this form – https://updraftplus.com/paid-support-requests/.
Please include screenshots or any error message you are seeing so we can investigate further on the issue.
Thanks,
Bryle
Hello Bryle,
Turns out I don’t have a paid subscription for UpdraftCentral, just UpdraftPlus. So, hopefully, you can respond here.
Turns out you cannot simply uninstall UpdraftCentral and install it again. That does not clear the database, so the offending site is still in the list of sites.
The only way around this problem I’ve found is to install UpdraftCentral on a completely different site and start over. Or, delete tables in the MySQL database and hope I don’t break anything else.
— Paul
Hi Paul,
Apologies for the late reply.
Glad you were able to find a workaround.
Also, have you tried using a different browser see if you get the same issue? Could you also let us know which version of UpdraftCentral are you using please? Is the self-install or the UpdraftCentral Cloud?
Regards,
Bryle
This is still happening for sites that no longer have WP installations. I have to remember to first remove the site from UpdraftCentral before archiving it.
UpdraftCentral version: 0.8.14
https://aricaschool.org/sponsors
WP/5.5.3 PHP/7.3.23 MySQL/5.5.5 Curl/7.73.0
Also, tonight I encountered three sites that stopped the update process, and I had to reinstall their keys. I’m wondering what would cause that.
From my point of view, the solution is a modification of UpdraftCentral to handle errors without blocking the process. If one site fails to respond properly, UpdraftCentral should simply flag it and continue through the list of sites. Why kill the whole process for one unresponsive site?
Thanks for considering that as a feature request (really, it’s a bug).
Now I have a site I cannot remove from the list. Instead, I get the dark screen over the window.
And, when I refreshed the page and clicked the ? button for support, that dark screen appeared again, locking up the page.
This is still a problem. The latest issue involves 22 sites that I had to move to a different server. Before moving the databases, I figured I’d remove all the sites from UpdraftCentral and then reconnect them after the new databases are up. But, it won’t let me remove a site: dark screen over the window, locked page.
What happens if you use a different web browser? Perhaps an extension in your web browser is getting involved.
