Bojan Katusic

Hi @ninablue

Yes, we will address those Deprecated warnings in the next version of the plugin.

Hi @mojamba

The Fatal Error seems to be a consequence of server or host misconfiguration, and considering haven’t received any other reports regarding it, it would appear to be an edge case.

Make sure that you are running PHP 7.4 or higher, and that both MainWP Dashboard (v4.5.1.1) and MainWP Child (v4.5.1) plugins are up to date.

If the issue persists, please open a private Help Desk ticket so we can collect some additional information & investigate further: https://mainwp.com/my-account/get-support/

Hi @akhil468

The error message is not generated by MainWP but is a generic server-related error message. And it appears that a security rule on that site is blocking the connection from the MainWP Dashboard.

1. Do you use some security plugins on your child site? If yes, can you try to temporarily disable them and see if that helps?

2. Do you use Cloudflare or any other cloud proxy firewall? If yes, can you try to whitelist your Dashboard IP or temporarily disable it to see if that helps?

3. If none of the above helps, can you please contact your host support and have them check server Firewall logs and see if there are any records of blocked requests from your dashboard?
And if possible, have them whitelist your Dashboard IP address.

Hi @wp800s

Our goal was to neatly organize all current pages into intuitive and easily accessible categories. This new navigation also sets the stage for exciting upcoming features.

Our KB for adding new items to the Navigation bar may also be of interest to you: https://kb.mainwp.com/docs/add-new-menu-entries-to-the-mainwp-dashboard-navigation/

If you have any specific suggestions, please feel free to share them on our feedback site. That way, others can vote for it, letting us know which features our users want the most.?https://feedback.mainwp.com

Hi @oceandigitals

Our Staging extension works in tandem with the WP Staging plugin, which needs to be installed on child sites, and the extensions serve as a central place from which you can control the plugin installations.

So when you create a staging site, it is being created on the child site, that is, on the customer website subdirectory.

Hi @darkpollo

It’s been some time since we heard back from you. I’ll assume that the issue has been fixed and mark the thread as resolved.

If you have any further questions, please start a new thread.

Thanks.

Thank you all for the additional information.

We have a KB that outlines necessary steps to fix the connection issue some may experience after the 4.5 update: https://kb.mainwp.com/docs/fix-the-disconnection-issue-after-upgrading-to-4-5/

If those step don’t help address your issue, please open a private Help Desk ticket so we can investigate further: https://mainwp.com/my-account/get-support/

Hi @stephenturner

Deactivating and reactivating the MainWP Child plugin indeed will usually fix the connection issue after the 4.5 update.

We have a KB that covers another method if that one should not work: https://kb.mainwp.com/docs/fix-the-disconnection-issue-after-upgrading-to-4-5/

Also, please try deactivating and reactivating the MainWP Child plugin on your child site and then reconnecting it on your Dashboard.

Thank you all for the additional information.

If you’re experiencing disconnects and you are running the latest version of the MainWP Dashboard (4.5.0.1) and the latest version of the MainWP Child plugin (4.5.0.1), please open a private Help Desk ticket so we investigate further.

Hi @momo-fr

Just to be sure I’m understanding the situation – did the disconnected child sites all have the latest MainWP Child plugin v4.5?

And the only way to reconnect them, was to deactivate and then reactivate the MainWP Child plugin, but the sites would get disconnected again when you attempted to perform an update on those sites via MainWP Dashboard?

Finally, when you downgraded the MainWP Dashboard to 4.4.3.4, did you also downgrade the MainWP Child plugin to 4.4.1.3?

And please feel free to open a private Help Desk ticket, and we will gladly look into the issues with v4.5 you were experiencing on your Dashboard.

Hi @stephenturner

Thanks for updating us regarding the scheduled server maintenance your host is performing.

While we wait for that maintenance to finish, please make sure that the affected child sites are running the latest MainWP Child version v4.5.

If the issue should persist after the server maintenance is complete, please open a private Help Desk ticket so we can investigate further.

Hi @groovyx9

Thanks for reaching out us.

We tested 1920×1080 resolution at that zoom level, and we didn’t encounter any issues.

To avoid any potential issues, take a look at our KB that covers recommended steps for upgrading to MainWP v4.5.

And please take a look at our KB that covers our new flexible widgets.

If the issue persists, please open a private Help Desk ticket so we can collect some additional information & investigate further.

Great, I’m glad to hear you got it fixed.

If you don’t mind, could you share what specifically fixed the issue? It may help other community members facing the same issue.

Hi @jennifer532

The MainWP Dashboard shows that message when it detects a response message containing keywords characteristic of the Imunify360 security suite.

Another potential complication if Cloudflare is used in addition to Imunify360.

Refer to our help article for more information about the Imunify360 connection block and the workaround for Cloudflare+Imunify360.

And please feel free to open a private Help Desk ticket, and we will verify the response message the Dashboard is receiving from the child site.