• Resolved Sean

    (@sean-h)


    Just installed the plugin today and added 6 sites, including the mothership site. It all works as advertised, except when I initiate a backup on any of the sites, I get a pop up stating ‘Communications error – Timeout, error in contacting the remote site.’

    Funny thing though, it is contacting the remote site and the backup is running and completing, at least it appears to be.

    The mothership site is the primary domain in a cPanel shared hosting account, the other 5 are addon domains, if that is useful info.

    Like I say, it all appears to be working, except for this pop up which appears to not be true. Any ideas?

Viewing 3 replies - 1 through 3 (of 3 total)
  • Plugin Support bcrodua

    (@bcrodua)

    Hi,

    Apologies for the late reply.

    Please can you try to re-add the website to the mothership site?

    Do you still get the same error?

    Regards,
    Bryle

    Thread Starter Sean

    (@sean-h)

    Hi there,

    I’ve actually already tried that but it didn’t solve the pop up problem, which happens on multiple sites. One site gave a timeout error when looking for updates, another when trying a backup. Like I say, it shows me this ‘error’ but the process’s still complete anyway, at least they appear to. I tried putting the Wordfence WAF in ‘learning mode’ and I’ve also considered server settings to be a possible cause, but seeing as I only have 7 sites to manage it’s not worth it for me to trouble shoot this issue too much more right now.

    I have now deleted the plugin from the mothership and will see if reinstalling it and all the sites again will help, but I don’t think it will because I had a similar problem when saving posts made with the Divi theme. They saved despite a pop up saying they didn’t. However, I think that was because of the WF WAF. I tweaked the WAF and the error pop up seems to be gone, like Captain Jack Sparrow’s rum.

    With all this said, it is definitely a very useful plugin if you have a lot of sites to manage, after a bit of tweaking.

    Thread Starter Sean

    (@sean-h)

    I seem to have fixed this problem by simply increasing the timeout in the self hosted mother ship dashboard from 30 to 120 seconds.

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘Communications error – Timeout’ is closed to new replies.