"Internal Server Error" with all PHP pages

[#1]

I was just looking PHP.ini in the hosting.plus.net Control Panel and since restoring the PHP.ini to the default settings using the link in the PHP Manager section, all of the PHP pages on my site return "500 Internal Server Error", e.g.
http://ccgi.virnuls.plus.com/interactive/wall.php

There's an office hours phone number in the Control Panel, but is there any other way to access support, e.g. via e-mail?

[#2]

but is there any other way to access support, e.g. via e-mail? -No.

[#3]

It now seems to be all pages.

[#4]

---

@virnuls wrote:

I was just looking PHP.ini in the hosting.plus.net Control Panel and since restoring the PHP.ini to the default settings using the link in the PHP Manager section, all of the PHP pages on my site return "500 Internal Server Error"

---

---

@virnuls wrote:
It now seems to be all pages.

---

I have used php on ccgi (sadly no longer as had to move main site to enable https addresses) but dim recall that php.ini wasn't used because that was governed at *server* level (ie not something individual sites had control over).

Just looked at the https://www.php.net/manual/en/configuration.file.php page of the PHP manual, which says

'The configuration file (php.ini) is read when PHP starts up'

and then

'The Apache web server changes the directory to root at startup, causing PHP to attempt to read php.ini from the root filesystem if it exists.' 

... which would seem to confirm that might indeed be the case.

You'd need someone here with a more in-depth knowledge of php/ccgi to verify that one way or the other.

In the meantime, do you by any chance have a copy of the php.ini file before it was changed to the 'default' setting (?)  Restoring it to whatever it said initially might re-enable your pages.

Perversely of course, if changing the php.ini file *does* have such an effect, that would indicate that individual sites can run php.ini files rather than such settings being governed only at (apache) server level.

.

[#5]

Thanks for responding.

I did download a copy of php.ini (there's a button to do that), but it was empty.  I tried putting it back, but no joy.

My guess is that the Control Panel php.ini thing is broken, because clicking the link to reset the file to its default settings appears to write four lines into php.ini (if you use the "view" option), but if you then download the file, it's empty.

I'll call the helpline when it opens.

[#6]

---

@virnuls wrote:

I'll call the helpline when it opens.

---

Thank you for the update

Does sound like something might be broken, not sure who would look after such things these days, given it's a 'legacy' service.

Hopefully CS will create a ticket and refer this to the right team for action - if not, try posting back here and we can try flagging people who might have some idea how to get this fixed.

.

[#7]

Hi @virnuls thank you for taking my call this afternoon, this has now been raised to our NetOps team and I will contact you back once they notify me to have addressed the issue with Webspace.