I’ve had to retype this 6 f** times because the bot is thinking I’m spamming links. I am getting a 1014 error for my domain redirection on linking from a wordpress page. I do not think it is accurately detecting this because it links to itself, and the domain is owned by the same account.
What steps have you taken to resolve the issue?
Nothing, it is a cname, pointing to the non www version of itself on the same exact account
What are the steps to reproduce the issue?
Go to the link in the comments, and you will see what I mean
I’m sorry for being short y’all, I had to entirely retype this stupid post 6 times because Cloudflare’s link spam protection is munted. I promise I had a very well spoken initial draft then it devolved to this as it has “Less than 4 links”, even though I only ever included 2.
So, on my Wordpress themes I link my site in it’s www form. But when you click on a link to it, it shows a, what seems to be, false flag of cross user reference. Go to Log In ‹ Michael Wisehart — WordPress and click the Interpixel link at the top, you will see the error.
Think is, when you go to www.interpixelstudios.com, it does indeed have a name, but it simply points to interpixelstudios.com. This domain, including michaelwisehart is all owned by my cloudflare account. Thus, I think this is a false flagging.
The issue here seems to be that you’re pointing www directly to wordpress. Reach out to WPE and make sure they have that subdomain configured as a custom hostname.
If you just want www to point to the root, a workaround would be to create a redirect rule.
I do not use WPE, I am my own hosting provider. Would this be a config that I’d address in NGINX? It should be pointing to it via the server_name directive.
Thanks for replying to this, I’ve been trying to work this out for a bit!
;; ANSWER SECTION:
www.interpixelstudios.com. 290 IN CNAME wp.wpenginepowered.com.
wp.wpenginepowered.com. 290 IN A 141.193.213.11
wp.wpenginepowered.com. 290 IN A 141.193.213.10
Can you check under the DNS tab on Cloudflare, whether the www subdomain record is pointing to your origin server correctly?