Moderator
t-p
(@t-p)
double check you have not blacklisted this word “thoughts” somewhere either via a plugin, or in the dashboard …
Hello,
403 Forbidden error is the consequence of a server refusing a request due to a lack of proper permissions So please check your file permissions.
You can also try by deactivating all plugins and then check, If that resolves the issue, reactivate each one individually until you find the cause.
If that does not resolve the issue, try switching to the default theme for your version of WordPress to rule-out a theme-specific issue (theme functions can interfere like plugins).
Also check your .htaccess file it may be corrupted, which in turn can cause a 403 Forbidden access error to appear on your WordPress site.
Yes, I already disabled all plugins and tried the default theme. Same behavior.
I don’t have any plugins that might blacklist a certain word…
I think that maybe it is only the images….
I have this line in my .htaccess file:
# http://httpd.apache.org/docs/2.0/mod/core.html#errordocument
ErrorDocument 403 "Sorry can't allow you access today"
If I remove that line, the posts and pages with the word “thoughts” in the URL now load, but the images which contain the word “thoughts” in their URL do not. And the only way to get the images to appear is if I change their name. Soooo… it appears that the images with the word “thoughts” are sending the 403, and when I have that line above in my .htaccess file, the 403 on the image causes the entire page to throw a 403… whereas without that line, the page itself loads, but the image does not…
Does any of that help?
Download your .htaccess file on your local computer and delete it from the server and then check.
If I delete the entire .htaccess file, I still get a 403 for every page that contains the word “thoughts.”
I also just discovered that it affects every domain on my VPS. I have about 10 websites, and each one has the same problem. The domains are installed in different folders.
So does this mean its a problem with the server setup?
It seems like that. You can contact with your server provider.
Turns out it was a bug with cPanel. My host figured it out, talked with cPanel, and they are pushing out an update tonight.
