Leah

@takayukister
Well I certainly care. ?? CF7 has over 5 million downloads, I can’t be the only one who would appreciate something like that.

I did check the release notes before making any changes to our production environment though, thankfully. In your announcement you recommend upgrading immediately, but now I’ll have to delay updating until I’ve had time to test in our dev environment, which could take weeks, so it’s a bit of a predicament.

If not a beta release, then maybe just a blog post or something a week or so ahead of release? Just anything to give a heads up before major releases would be really helpful and save folks a lot of headaches.

Thanks for your response.

@prkspeaks

Exactly, my site is functioning perfectly other than that, as is WP Cerber itself (as in, I’m not seeing any other kinds of false positives, everything else it’s blocking looks like it should be getting blocked). No server issues, no downtime, no dips in traffic, nothing in our logs and nothing being blocked by our own server’s firewall. I never would have known there was an issue if not for the email notices from Google.

To clarify about the IP ranges, I meant that I added those to the WP Cerber Access List under WP Cerber > Dashboard > Access Lists tab.

I should mention though that I did first rule out a few other possible culprits. In my case it was WP Cerber, but if adding those IPs to the access list doesn’t solve the issue for you, you might try checking with your website’s hosting company and/or see if you might have other plugins installed that could be blocking Googlebot (Wordfence, for example).

• This reply was modified 4 years, 5 months ago by Leah.

@prkspeaks

So far so good, haven’t had a single ad disapproved since (was getting hundreds a day before). I ended up just adding all of Google’s public IP ranges to my whitelist:

64.233.160.0 – 64.233.191.255
66.102.0.0 – 66.102.15.255
66.249.64.0 – 66.249.95.255
72.14.192.0 – 72.14.255.255
74.125.0.0 – 74.125.255.255
209.85.128.0 – 209.85.255.255
216.239.32.0 – 216.239.63.255

After looking into this further, I am in fact seeing that WP Cerber is blocking several Google-owned IP addresses on our site. There are many, but these seem to be the most affected:

66.249.91.242
66.249.75.211
66.249.91.244

Because of this issue, thousands of our Google ads have been getting repeatedly disapproved for months, due to the fact that when Google attempts to crawl our site to to determine that the destination is working, it’s met with a 403 error after being blocked.

I’ve added those IPs to our whitelist, but IMO Google’s IPs shouldn’t be blocked to begin with unless specified.

Thoughts?

Ah, gotcha. Sounds like maybe multi-site won’t work for us then, unless we re-structure the way our site architecture is laid out.

The way it’s set up currently, our root domain example.com is used as our primary brand site, while the subdomain a.example.com is used for our white-label program.

The complication arises because we offer both branded and non-branded vanity URLs for our clients, and the non-branded vanity URLs rely on the wildcard to serve the content from a.example.com. That way, our onboarding team doesn’t actually do anything to “set up” the non-branded vanity URLs. You could literally type in skjdfhskdfhsgkd.example.com into the address bar right now and it would serve a.example.com (while retaining skjdfhskdfhsgkd.example.com in the address bar).

It sounds like in this case, if we want to use multi-site for subdomains while retaining the functionality of our wildcard/non-branded URLs, we’d want to put it all under a new root domain, examplewhitelabel.com or whatever. That way, we could have both multi-site installed at the root and the wildcard pointing to the root.

Hey @cknowles,

The issue for me ended up being a piece of my own code that was removing any reference to “Yoast” in HTML comments. I like to keep my comments as clean as possible, but it looks like I was stripping a necessary part out of Yoast’s new inline schema. I just removed that bit of code for the time being and it seems to have done the trick for me.

Not sue if this is the same issue you’re experiencing, but if you’re doing any comment sanitization, you might check to see if removing that fixes things.

Best of luck!

• This reply was modified 5 years, 4 months ago by Leah.

Yep, +1 here as well

It doesn’t always happen, but definitely the majority of the time.

• This reply was modified 6 years ago by Leah.

Never mind, I just realized that I was using the wrong tag on my WP All Import settings, so it wasn’t pulling in any data for the application field. ??

Hey Raul,

No problem, appreciate you taking the time to respond.

After disabling CSS processing and then JS processing, it looks like it’s one of the JS files creating the conflict.

I’ve been going through and removing them one at a time with no luck so far (there are over 50 files, crazy!), but I’ll update here if I find the culprit.

I did also ensure that Divi’s own minification was disabled, thanks. ??

Edit: Found it! Looks like this was the file creating the conflict:

/wp-content/themes/Divi/core/admin/js/react-dom.production.min.js

Excluded it and all is well. ?? Thanks again for reaching out and I hope you enjoy your holiday!

• This reply was modified 6 years, 3 months ago by Leah. Reason: Issue resolved
• This reply was modified 6 years, 3 months ago by Leah.

Hey @gonzalesc,

After doing a bit more troubleshooting, I discovered that my problem had to do with the premium version of the plugin, not the free version, and was only present on mobile.

I reached out yesterday and as I’m writing this, it looks like an update was just released for the premium plugin that resolves the issue. ??

Thanks for continuing to follow up!

Hey @timothyf, did you ever figure out what the issue was?

I’m experiencing the same thing on my site.

• This reply was modified 6 years, 4 months ago by Leah.

Ah, right! Sorry, should have mentioned that.

Thanks, I’ll go ahead and do that for now. ??

Alright, I’ve deactivated that plugin.

Are you not seeing the issue on your end?

@timersys should be cleared

I have a plugin that combines/minifies and caches our CSS/JS, which is the only caching that I’m doing on the site. I’ve gone ahead and cleared it again, so it should be fresh.

Thanks for the quick response! Here’s a link to one of the pages on our staging site where this is occurring:

https://staging.gradepotentialtutoring.com/san-luis-obispo-ca-tutoring

The popup slides in after you scroll down the page a bit. It’ll appear at the bottom left, but it should be appearing at the bottom right.

• This reply was modified 6 years, 6 months ago by Leah.