rockeru

It fixed itself after about a day. I then experienced the same problem a week later that lasted a couple of hours. No issues afterwards up until now.

I’m having the same problem on both of my sites and it isn’t the first time it happened. https://api.nrelate.com is returning a 500 response code. It’s an issue on their part probably, since the plugin doesn’t report any issues in the WordPress admin pannel, I even hit the reindex and it finished without issues. I hope it gets fixed soon.

I previously renamed the wp-content folder but now I tried deleting all plugins and themes but still no effect. I also deleted my whole 2nd site/wordpress installation I had in a subfolder on an addon domain, still didn’t solve anything.

Use it how? That is a blocked robots file that I’ve been getting no matter what I do for the past days. And even if I make my own file without the / at disallow and without any wordpress in the root, I still get:
User-agent: *
Disallow: /
This happens only in sub-domains on a wildcard record.

Of course it’s unchecked on all the sub-blogs. But through hours and hours of testing I’ve discovered something else.

If I delete WordPress and my robots.txt file then go in any randomsubdomain.mysite.robots.txt it always give me the wrong blocked robots.txt file even though there is no such file in the root, and there is no more WordPress to virtually make one. That leads to the conclusion that it isn’t a WordPress issue.

I’ve contacted my host and told them the problem, they didn’t figure it out yet. If anyone can give me a hint as to what can cause this in a hosting account it would be very helpful.