skeitel

What I have is what you describe as Website C. I don’t have mysubdomain.example.com

Regarding DNS, I have not re-directed anyting manually. I just use the auto-installation script from Bluehost so I don’t know exactly how this works, sorry.

I’ll try to install BPS in the subfolder website and see how that goes then.

Thanks again

Ohhhh…that’s very interesting. So are you saying that a local BPS in the sub-installation would override the power of the BPS sitting above it at the root level? Very interesting. I am surprised.

I’ll try that then, and see if it works
Thank you

Hi
What I meant with “subdomain” is a WordPress installation within a WordPress installation that contains the other domains. They look like independent domains to the outside world, like https://www.example.com, but behind the scenes it is contained in the main wordpress install.

I was told by Bluehost that it is the BPS in the main WordPress install that is creating the problem, that’s why I am here ??

I followed your instructions.

1) deleted htaccess (renamed it actually, was too chicken to delete it, just in case. I called it .htaccess_old_bulletproof)

(note: I have a simple image on the subdirectory that’s all there is, for testing purposes)

2) I pressed both automagic buttons and refreshed the subdirectory website to check. All ok. Image showing.

3) I activated Website Root Folder .htaccess Security Mode, and refreshed the subdirectory website. THIS BROKE THE WEBSITE showing the message I detailed on my first post.

4) I deactivated this Website Root Folder .htaccess Security Mode, and reverted it to default.

5) I carefully activated one by one of the following modes, refreshing in between each. No activation of these modes broke the website.

My conclusion is that the problem is on the “Website Root Folder .htaccess Security Mode”. Only when this was activated the website broke.

What should I do to resolve this? ??

THANK YOU!

Hi,
Yes I think so, but don’t remember. I certainly did everything to have the safest settings.

Ok I’ll try what you say. Thanks for your reply!

By the way, I just noticed that the title of the webpage is different to the error it details on the text. The title of the page that shows the error is “403 forbidden”.

I don’t know if this is relevant