MySQLi Error 404

[jordan85]

I'm currently working on some PHP scripts and am having trouble that I haven't been able to find an answer to.

$conn = new mysqli($servername, $username, $password, $dbname);
...
echo $conn->error

Whenever I use $conn->error, I get redirected to my custom 404 page. It doesn't change the location of the page, but just basically refreshes the page and throws a 404 error. Google isn't giving any answers. Am I missing something with my hosting plan?

 

[essellar]

Yes - there are security settings in place meant to keep you from "leaking" debug info to the world; a 404 will be thrown if the response is "leaky" (a 403 if the request content is "shady").

 

[bdistler]

Yes - there are security settings in place meant to keep you from "leaking" debug info to the world; a 404 will be thrown if the response is "leaky" (a 403 if the request content is "shady").

with the new x10hosting's security mod_security hammer and no log files
we (users) now need to test our PHP/MySQL scripts on some other host to find where the error is at and what it is

 

[essellar]

You're not supposed to be doing development in a production environment, ever. It may be your playground, but it's the "real deal" for the vast majority of users of the service, and production website hosting "for the masses" is the intent of the service. Free Hosting is not, and was never intended to be, a staging area for development experiments.

 

[bdistler]

my point is - when we (users) have a issue come up with our site (account) that was working - we no longer have any information as to why it stopped working
so now we need to test our scripts on some other host to find where the issue is at - and what the issue is - before the issue can be resolved

 

[caftpx10]

I agree with the others.
Regardless if production or not, there should be information so that any issues can be identified and potentially be corrected (especially if it's a typo in the code).

Without the error being displayed, how would the issue be corrected (easily)?

An example would be a MySQL connection error of some sort (this can be due to failing to connect with the details provided, IP blocked, max connections..), as it's 'localhost,' you can't really figure out the actual issue on a different server, as the host URI is literally local ('localhost' assigned with a local IP in the hosts file).
Would it really be worth importing a database just for simple debugging rather than just looking at the error right away and sort it out?

Many hosts (paid or not) display the errors either in a log file, outside to the public (worst thing to output) or both.
Like @bdistler said, we would prefer to not use a secondary host just to hunt down the cause of the issue, small or not.