I wanted to reach out to the community to see if others are experiencing similar issues since upgrading to MainWP v6.
Since our migration, managing maintenance across our 230+ websites has become significantly more difficult. In particular, the manual sync process appears to be unreliable and extremely slow, which is impacting our team’s ability to perform routine updates efficiently.
We have already opened a support ticket and have been in contact with the MainWP team for about a week. While they are actively investigating, we have not yet received a resolution. Prior to this, version 5 was running smoothly for us without these issues.
I’m curious to know:
Are other agencies experiencing similar performance or sync issues with v6?
If so, have you found any temporary workarounds or solutions?
We rely heavily on MainWP for our operations, so understanding whether this is an isolated case or a broader issue would really help us determine next steps.
I’m managing 330+ sites at the moment and have been using the 5.5/6.0 early releases in production since they became available. They are faster overall than 5.4.
The only thing I needed to do was disabling network activity (site changes) that I don’t need, because it generated so much data, that my databases blew up. You can change that at /wp-admin/admin.php?page=SettingsInsights
For the rest it might be a conflict with an old extension or a non-MainWP plugin. But I’m sure you’ve done your basic debugging and are looking in to that further with support.
Thank you for your feedback and the link to the settings, I already unchecked a lot but we want to keep track some of them. Our main issue is the manual sync that is not working…
Then I would think about security, checking the logs, browser console and maybe query monitor. But as a WP Expert, I’d guess you’ve done a lot of that already, so it wouldn’t be useful to throw all the ideas on the table, if support is already working on it.
If you have specific information or leads somebody might be able to help better. We can’t say anything about why “it’s not working”.
We tried everything we could think of before contacting the support and yes, we do have error in the console but only Error 503 which means that we don’t have any resources available! And it is only happening on manual sync or updates. The auto daily updates works fine as we can see new updates available in the dashboard… We have the same install, similar numbers of sites as we had with 5.4.
A 503 is not limited resources (like an overloaded server), but a security issue. It might be a firewall blocking the requests or maybe a rate limiting.
Doe the 503 happen if you sync only 1 site? Or a few? Are the sites all on the same server or network? Do they all use Cloudflare, ModSecurity or something like that? It might also be rate limiting. You should try to whitelist the IP of your dashboard. Do you see the request in the child site’s access log? It might help to figure out where the request is blocked.
You right, in my mind I was thinking 500 as that exactly the error we see after a few minutes on the site itself. I don’t think it is a firewall issue with child but maybe with the main dashboard so I asked our hosting provider to take a look as V6 may have a different log print. Again, it was fine with 5.4.
I already reduce the rate limite from 12 to 4, since for the rest…
Thanks for the input.
Well, it was not a firewall issue but really a resources issues, we had to add CPu and Memory to have it running properly… So definitely v6 is requesting more power! Thanks @josklever for the feedback.
That’s strange. I don’t recognize that. I’m running my dashboard on my own dedicated server together with 150+ client sites and I didn’t see an increase of the load after the update from 5.4 to 6.0. So that might be dependent on how the resources are managed/capped for the dashboard site.
I was surprise too! I didn’t think that resources will be the issue as between 5.4 to 6 we may add 5 or 6 clients but here we go, problem solved with extra resources.
WordPress® is a registered trademark of the WordPress Foundation, and WooCommerce® is a registered trademark of WooCommerce, Inc. MainWP is an independent product and is not affiliated, associated, or endorsed by the WordPress Foundation, WooCommerce, Inc., or Automattic Inc., except where noted under the Jetpack® API and Trademark License Agreement. All product names, logos, and brands are property of their respective owners and are used for identification purposes only.
