Bugger me with a stick,
.
Alright, so I broke the site for a bit today. I tried to configure PHP to run as a FastCGI module, i.e. not as a part of Apache, and fucked some stuff up so you could actually download .php files for a while - which is not good.
I stopped the server and tried to fix it, but couldn't get it to work, so I eventually just removed and reinstalled the webserver completely, starting from the ground up.
Followed
these instructions. Which... sorta worked.
Restarted the server, 500 / internal server errors ensued. Checked out the error log, turns out the thing ended up in a redirect loop between the public_html folder and some CGI working folder (if that makes any sense), a known issue for Wordpress installations, as is shown in one of the comments of that article. Added an exception for redirecting in the /usr/lib/cgi-bin folder which seems to have fixed that.
Sooo... now PHP scripts are handled outside of the webserver (Apache) process. Next up is diving into those settings and see if there's anything to optimize. Instead of a dozen Apache processes, there now seem to be a dozen PHP processes running. I'll see to fixxing that, and if that don't work either, I'll just order the more expensive hosting thingy.
@you guys, I removed and reinstalled some, please see to trying out stuff and see if there's anything not working properly, k thx bai.