Not able to connect MainWP on CloudFlare

[mahesh.punhani]

I have installed MainWP to update all my sites from a central dashboard on a subdomain of my site. But i am not able to update any of my child sites. If I pause Cloudflare, everything works fine.

I tried adding a firewall rule to skip my dashboard IP but that didn’t work either. Has anyone faced this issue? I tried searching in the forum but could not find any solution.

[epic.network]

Welcome to the Cloudflare Community.

I have MainWP running behind the Cloudflare proxy and it works with child sites that are proxied on both the same and other origin servers.

You might check your Cloudflare log to see if you can find the reason the traffic is being blocked. That may help you identify the setting you need to change.

[mahesh.punhani]

Thanks for your update but I can only see the logs in the Security->Events for custom rules. Maybe because I am using Free Plan.

Is there any other way to figure out what could be going wrong?

[CrewAlmostro]

I have the same issues. Putting a reply in here to make sure the topic doesn’t get locked because I haven’t been able to solve this and I am getting desperate.

This affects all my sites across 3 different hosts.

[CrewAlmostro]

For reference, here’s my earlier topic:

Half of my sites on MainWP can no longer connect (blocked by Cloudflare)

Hello! I currently have 34 sites that I manage through MainWP. They were all connected fine until recently, (and had been for months). Between Jan 27 and Jan 30, half of these sites were disconnected because MainWP access was suddenly blocked by something on Cloudflare’s end. However, from Jan 30 everything worked fine again. I had not made any changes. As of Feb 6, the same sites are disconnected again. Response: https://codepen.io/almostronaut/pen/JjBqdMO All 34 sites use the same…

I also found this which may be related:

I can no longer connect child sites to my MainWP dashboard if DNS Proxy is turned on

Thanks for the welcome. I’d love to put my MainWP instance back behind the Cloudflare proxy. I don’t think geoblocking the login page would affect MainWP. Would it? I don’t use Jetpack. It would be good not to need a specific rule on child sites. How would I go about creating a [quote=“epic.network, post:2, topic:417469”] self-referential rule for both IPv4 and IPv6 for the MainWP dashboard [/quote]? It doesn’t appear that I’ve ever set up restoring original visitor IPs on my servers. Th…

Both topics just died from lack of solutions…

[epic.network]

I don’t know what to to tell you. My MainWP instance runs behind Cloudflare proxy and has child sites on both the same host and other hosts. All of the sites on other hosts are also behind Cloudflare. All hosts behind Cloudflare have Authenticated Origin Pull now, though they didn’t at one point.

If Cloudflare is disrupting the connection to the child sites, you should see the action in your Cloudflare Activity Log. You should be able to devise accommodations from the log detail.

Security Events · Cloudflare Web Application Firewall (WAF) docs

[CrewAlmostro]

I set “Force IPv4 (optional)” to “Yes” (in MainWP) and that is helping.

However, I don’t know if that has any knock-on effects or will come back to bite me later.

[epic.network]

I have never enabled that setting in MainWP. Unless something is not working on your child site’s IPv6 networking, it shouldn’t be necessary.

[CrewAlmostro]

I’ve passed this information along to one of the hosts I’m using… maybe they have some insights

[mahesh.punhani]

Thanks for this update. Let me try this setting as well. By the way, as a workaround, I started using InfiniteWP instead of MainWp. everything is working fine with InfiniteWP.

[CrewAlmostro]

Did it work for you?
I hope to have some more insights to share early next week.

[mahesh.punhani]

Yes, this worked for me as well. Thank you for the solution