And so
suddenly it escalated
Almost like this Leigh McClendon on Instagram: "When cats meet🤣 #catsofinstagram #cats #pets"
And so
suddenly it escalated
Almost like this Leigh McClendon on Instagram: "When cats meet🤣 #catsofinstagram #cats #pets"
I have just the perfect response for him:
Unfortunately, yes, that’s common. You’ll need to ask your question again; you could try asking if they can escalate it, second line support usually handles these better.
If the Error 500 you see on the volumes you mentioned comes only because of phpinfo(), it is unfortunately expected; volumes on PHP 8.2 experience this issue, because it seems the phpinfo() function doesn’t exist. I hope iFastNet can resolve this.
The PHP on these volumes are broken. All PHP will not work
Oh, I see! You might want to mention that in the ticket, because since phpinfo() is broken anyways, they might think it’s because of that.
Give them a script that prints basic PHP, echo "Hello, World!"; or something ![]()
Yeah, it’s broken in iFastNet’s PHP 8.2, not the regular PHP 8.2 (as far as I know).
On the VPS where my website is on there is a normal PHP 8.2 (with a working phpinfo()) at least, so I can confirm it’s a server problem on their end…
But why even remove that.

We’ll wait for your ticket escalation (or a response from iFastNet’s representative here lol), hopefully the function broke by accident and will be reactivated…
In the meantime, this can be used as an alternative:
upload a phpinfo() page and then browse to that page.
What about echo phpversion(); for broken servers where phpinfo() doesn’t work?
Follow-up just to say that phpinfo() works on vol9_5, where my new test website is!
All PHP are broken on those hosted volumes
<!DOCTYPE html>
<html>
<body>
<h1>My first PHP page</h1>
<?php
echo "Hello World!";
?>
</body>
</html>
Even running such a basic code will result in E500
Oh… They should reinstall it I guess then, though for my new test website on free hosting I had luck into getting a PHP 8.2 server that isn’t broken.
Reading the answer, you get the impression that it is better not to contact at all ![]()
The answer is in the same quality range as this one here
I remember when someone contacted them about that one of the cpanel subdomains had its SSL certificate expired.
They, in an unironic and brave attempt responded OP something like this:
Hi, please use this:
http://cpanel.rf.gd
Best regards.