New on LowEndTalk? Please Register and read our Community Rules.
All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.
All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.
Comments
But in public forum we can discuss things like that? Or it is so stupid that it is deemed taboo?
It's so stupid, that everyone will ask you to re-install.
Nobody in their right mind would have time or interest to ask you to post your PHP configs, and system infos and webserver configs. then debug them for free, and give you directions and commands to fix them.
Why would anyone waste their time when this will be fixed by default by re-installing and then copying over the folder structure to www root.
Everyone here can see that it works, and then it doesen't work, so it's probly week worth of work trying to find the cause in some big system that likely has another service which takes over the webserver.
Not to mention, you posted a hypothetical question.
If you need technical advice, start the thread with all info you have available.
Such things could be:
Hardware
OS
Webserver
PHP type/version/handler
Config files (Webserver/PHP)
error logs/crashlogs/System logs
Yes, this thread is hypothetical. So, please post your hypothetocal solution.
Test your configuration at dev environment before deploying on prod
And re-install.
@Levi, I think OWASP CRS for ModSecurity WAF has a rule that deals with your concern.
Finally! Thank you my man.
Well, yeah but shutting down the whole box (for added security) is more funny
I can create a configuration that will output the text of a PHP file when FPM fails. However, it's difficult to envision how this could happen unintentionally. Regardless, the following command can be used to stop Nginx if PHP code is detected:
This actually happened to me a decade back on a wordpress site. I was running apache+php (custom ppa) on ubuntu 14.04 or something. Not sure what happened, I think php or apache got automatically upgraded to a newer release and the apache config got reset. all the *.php were getting served as raw files. However there was no damage since the mysql database was locked to localhost.
Since then I have moved on to nginx+php-fpm. Now whenever something like this happens, usually nginx returns http 5xx instead of serving php files as raw text files. I also sometimes test by intentionally removing php-fpm to check what happens to prevent shit like this.
TL;DR your apache/web server config is most likely misconfigured.
Oh my God. It's a problem with posting a command.
Sorry for that.
I'll try in this way:
https://prnt.sc/OHLkyr8a9CWJ
I think you should've not do the screenshot of the single CLI line, better post it as text.
Most likely blocked by Cloudflare thing and not allowed to post as plaintext... but yeah, fallback to screenshot rather than some paste service is meh.
Yes, it's blocked by Cloudflare and not allowed to post(((