Child connection issues - (italian) Aruba servers

Hi, we currently manage about 50 sites, some of which are hosted by the Italian provider Aruba.

We subscribed to a MainWP Pro program just yesterday, installing Child on all managed sites. We encountered connection problems between Main and Child in only 3 cases, curiously on sites hosted on Aruba. In two other cases, again on Aruba servers, the problem does not occur: obviously we checked that the configurations (plugins, PHP version, etc.) were similar.

In one case we received an email reporting a technical problem with the plugin (domain Details of the error ==================== An error of E_ERROR was caused in line 1321 of the file /web/htdocs/ Error Message: Uncaught TypeError: fseek(): Argument #1 ($stream) must be of type resource, bool given in /web/htdocs/ class/class-mainwp-child-server-information.php:1321 Stack traces: #0 /web/htdocs/ fseek() #1 /web/htdocs/ MainWP\Child\MainWP_Child_Server_Information::render_last_lines () #2 /web/htdocs/ MainWP\Child\MainWP_Child_Server_Information::render_error_log () #3 /web/htdocs/ MainWP\Child\MainWP_Child_Server_Information::render_error_page () #4 /web/htdocs/ MainWP\Child\MainWP_Child_Server_Information::render_page() #5 /web/htdocs/ MainWP\Child\MainWP_Pages->render_pages() #6 /web/htdocs/ WP_Hook->apply_filters() #7 /web/htdocs/ WP_Hook->do_action() #8 /web/htdocs/ do_action() #9 {main} thrown

I ask the forum if any user has encountered the same problem.

Hi @Newdada

Welcome to the MainWP Community.

I will check with the development team what these errors might indicate.

What PHP version are you running on the affected child sites? And is it identical to the other un-affected sites on Aruba?

Please try this version of the MainWP Child plugin on the affected sites, and please let us know if that solves the error messages:

Unfortunately the attached plugin didn’t give any results.
On one of the working sites php is 7.4 and on the new one 8.0, but even downgrading to 7.3 from 8.0 the link doesn’t work. :frowning:

Solution found thanks to Aruba technical support: quite simply the address without “www” was not indicated :slight_smile:
For other sites the configuration provided for the alternative.

1 Like

Great, I’m glad you managed to resolve it.

And thank you for updating us.

This topic was automatically closed 24 hours after the last reply. New replies are no longer allowed.