Error 403 with SMF?

[chroixx1]

I might be a bit of a noob, but anyone know what's up with this?

Forbidden
You don't have permission to access /index.php on this server.​

Oh, and sorry if this isn't the right place for it... I usually just post in Free Hosting, I don't get out much.

 

[fomalhaut]

Hello ! Have you permission mode 644 on your file ? You see/change that on your cPanel / File Manager (or Legacy File MAnager)

 

[bdistler]

I might be a bit of a noob, but anyone know what's up with this?

mod_security settings can throw a 403 error (Forbidden) - if it sees a "shady" request

 

[caftpx10]

What is this 'SMF' you speak of?
As pointed out by bdistler, mod_security is most likely the cause of this 403 HTTP Response.

 

[Ohso]

Nothing you can do about it apparently

 

[bdistler]

Nothing you can do about it apparently

[ Select PHP Version ] on 'cPanel x3' homepage (not x10hosting's Basic) - then [ Switch to PHP Settings ] - change the [ display_errors ] and [ log_errors ] values to "On"
be sure to click on [ Save ] AFTER you click on [ Apply ]

then maybe you will see the error that causes mod_security to throw a 403 error - in the [ error_log ] file and/or you browser when you load your site

 

[caftpx10]

[ Select PHP Version ] on 'cPanel x3' homepage (not x10hosting's Basic) - then [ Switch to PHP Settings ] - change the [ display_errors ] and [ log_errors ] values to "On"
be sure to click on [ Save ] after you click on [ Apply ]

then maybe you will see the error that causes mod_security to throw a 403 error - in the [ error_log ] file and/or you browser when you load your site

Doesn't the HTTP Responses triggered by mod_security prevent "leaky" or vulnerable scripts from running and therefore no error will be generated?

 

[chroixx1]

[ Select PHP Version ] on 'cPanel x3' homepage (not x10hosting's Basic) - then [ Switch to PHP Settings ] - change the [ display_errors ] and [ log_errors ] values to "On"
be sure to click on [ Save ] after you click on [ Apply ]

then maybe you will see the error that causes mod_security to throw a 403 error - in the [ error_log ] file and/or you browser when you load your site

Will try this, thanks.

 

[bdistler]

Doesn't the HTTP Responses triggered by mod_security prevent "leaky" or vulnerable scripts from running and therefore no error will be generated?

Event B follows Event A - so B must be the direct result of A - It is a classic fallacy in logic
the 'script' needs to make a 'leaky' request or throw some type of error - before mod_security can (will) replace the 'real' error code with a 403 or some other error code in the 'Response Headers'

 

[caftpx10]

Event B follows Event A - so B must be the direct result of A - It is a classic fallacy in logic
the 'script' needs to make a 'leaky' request or throw some type of error - before mod_security can (will) replace the 'real' error code with a 403 or some other error code in the 'Response Headers'

Makes sense. PHP code does get parse before being sent out as a result or whatever for the web server (in this case Apache) to use.