I have a few sites that frequently disconnect from MainWP. It’s just a temporary situation, likely due to their hosting, so would like if MainWP could automatically try to reconnect to them via cron job, if possible, rather than leaving them disconnected until I log in and manually do it myself.
by default, MainWP has a built-in feature to attempt the site reconnection process once per hour.
If there are no problems with the connection, disconnected sites should be reconnected.
Thanks, but this doesn’t appear to be happening. I often log in to find 3 or 4 sites disconnected. My hosting is relatively solid. Uptime monitoring shows no outages.
Yeah, I checked with the dev team. If you are not sure that this is working for you properly, can you try to set a test by disconnecting one site and if it doesn’t work, please shoot us a ticket so we can look into it.
I’ve just disabled the child plugin on a test site, did a sync from my dashboard to disconnect the child and activated the child plugin again. Now we’ll wait…
After 4 hours, the site didn’t reconnect automatically. After that I synced my sites, installed many updates on other sites, so I was active on my MainWP dashboard. However the client site is still disconnected. So I wonder what should trigger the reconnect. It has been 7.5 hours now, but I’ll wait until tomorrow morning, before I reconnect manually.
I got in touch with the dev team and got more information about this.
The auto-reconnect feature is part of the mainwp_cronstats_action corn job that is an hourly cron job, but the reconnect function runs only once per day. I apologize for the inaccurate information in my previous post.
In addition to this update, the dev team made some small improvements for this functionality in this version. If you want, please install the version and wait for 24-48 hours to see if it works properly.
After 21 hours it’s not reconnected yet, so I’ll wait for a few more to check the “once per day” schedule.
The next step will be the modified version, although waiting 24-48 hours doesn’t sound like an improvement.
Just a quick idea: most sites that are disconnected unintentionally should be able to reconnect in a few minutes or an hour. If not there’s something seriously wrong, and the admin should be notified. After that a reconnection attempt could be made after 4-6 hours and after that daily.
These notifications could be send by mail or even better via Slack, but that might be another topic.
Their improvement is to make sure that the cron job runs properly, not more frequently. However, I do see that this feature has some space for additional improvements.
I will talk to the dev team and see what can we do.
I also agree that the Reconnect feature should run more frequently.
It’s been 41 hours now and the child hasn’t reconnected yet. So I just installed the new version. I checked the code diff, but didn’t see anything related to reconnecting disconnected child sites. Only something regarding to stats where something changed from weekly to daily, but maybe that’s also used by a function that triggers the reconnection.
I’ll keep an eye on it for at least the next 24 hours.