If you follow this rule.... in the case you make a configuration error on your web server, nothing too serious should be exposed.

Vistors don't download your scripts just because php-fpm died. At least not with any of the webservers i'm familiar with. Detection could likely bedone with a custom error page, i guess (disclaimer: i

(Quote)

server poweroff and not start and error :=(

Yes, it returns gateway error. But what if missconfigured?

Index is showing for everyone but no access is allowed, all files gave a 404 error... wow.

[root@swe ~]# ping -M do -s 1392 172.16.5.2PING 172.16.5.2 (172.16.5.2) 1392(1420) bytes of data.ping: local error: message too long, mtu=556

The installation process encountered an error. If the problem persists, contact support.

(Quote)

Is your store down? I get "Critical Error Could not connect to the database."

Well, the days of FreeBSD running circles around Linux might be long gone but when one looks at current benchmarks over at phoronix it's very much standing its ground. Actually one might even say it's

this link gives 500 error code!

(Quote)

(Quote)

(Quote)

You ask for status page or beautiful error page stub?

What kind of error do you get?

Error if i click order

Personally i have very little love for SysV (it's clunky and archaic with the only upsides being it's massive flexibility - it's all scripted after all - which comes with a lot of error prone work tho

(Quote)