dvgj
Forum Replies Created
-
Hey Adam, of course, I continued experimenting, and I’ve found the reason eventually.
1. As I mentioned, I’ve changed the Cloudflare SSL encryption setting for my website from Flexible to Full (or Strict; my website supports both of them), and the error has been changed. Why did I decide to change it? I saw the “mixed content” alert when I opened the console. Therefore, changing the setting removes the reason for the fake “staging environment” error.
2. Next, I’ve just noticed the new error mentions the caching issue, and actually, this is what Cloudflare does and why it’s mainly being connected (on the Free tier, lol). So, I’ve disabled Proxying for the root A-record (just set it to DNS only), which led to disabling the Cloudflare caching, and the error disappeared.
I hope my experience will help those guys who meet the similar issue.
@adamdunnage Thanks for your input – your hints were very helpful! Is there a chance that you can recognize these reasons and add them to the plugin’s error handler?
- This reply was modified 2 years ago by dvgj.
Hey Adam, thanks for your response!
1. The Site Health information is shared via the form you provided me with.
2. Yes, there’s no difference when I perform those actions and in troubleshooting mode.
3. I’ve double-checked the Cloudflare settings, there are no specific settings (e.g. Under Attack mode or any other security configs) were applied.However, you gave me an idea, and I’ve changed the Cloudflare SSL setting from Flexible to Strict, and the error has changed. Now it’s the following:
Looks like Site Kit is unable to place or detect tags on your site. This can be caused by using certain caching or maintenance mode plugins or your site’s frontend is configured on a different host or infrastructure than your administration dashboard.Using the troubleshooting mode doesn’t make any difference.
Hope that can help, thx!