Hello
I’m reading contradictory messages. To fix the CVE on PHP 7.4 it seems there is no patch. Yet it is mentioned a little earlier that the version that will be in place after the update will be 7.4.33.
But does this version fix the CVE?
Hello
I’m reading contradictory messages. To fix the CVE on PHP 7.4 it seems there is no patch. Yet it is mentioned a little earlier that the version that will be in place after the update will be 7.4.33.
But does this version fix the CVE?
Check your client area for the error logs of your web server.
This type of error can be caused by a permissions issue or a syntax error in .htaccess, among other things...
I think I've read that anything older than 8.1 will not be patched. Update, if possible, to version 8.5
My site suddenly shows an internal error, even though I haven’t changed anything for ages.
The subdomains are the same—what’s happening?
An image or HTML file displays, but a PHP one does not.
Thank you for the answer.
In fact, it hasn't even been an hour; everything was publicly visible at friends' homes.
I haven't posted ANYTHING since this morning around 10 a.m.
This “kind of error” doesn't come from me.
And I haven't changed any configurations on my two Dotclear blogs, I just posted something in one of the blogs.
And regarding the fixes to make, I don't know how.
I don't see why, within an hour, both of my blogs would crash.
I'm running PHP 8.2 / stable64.
OVH changed something.
For those who are still on older versions, the PHP community has made patches available for 7.4, but since support is no longer provided for these old versions, you will need operations that go beyond a simple update... It reminds us that it is important to follow updates as much as possible to minimize the impact ![]()
If I upgrade to a PHP version newer than my PHP 8.2, will that fix the situation?
And will it make my two blogs visible again?
Or do I have to wait for OVH to release its patch, as I understand?
( For each, hosting is essential.
I just finished a bike expedition in Sweden
of 3,007 kilometres in 41 days of riding.
And then OVH crashed my blogs!
And apparently I’m not the only one. )
Hello @Rallarros
You should already do everything possible to upgrade to PHP 8.5.
For my hosting on cluster 110, it’s already done.
I have on my sites:
![]()
You can also check the exact PHP version by installing the small script bonjour.php in the root of your site:
See in my guide the paragraph: I3- Contrôle du SSL : Avec le script bonjour.php
Good evening,
Some of my shared hosting sites have also been showing Internal Error since the update.
Only the sites that use phpcgi 8.4 are affected; if I switch to php (php-fpm) it works fine, but some functions of these sites only worked in cgi, not in fpm.
Will phpcgi be reactivated?
On the OVH cloud support >>> hosting >>> I upgraded to PHP 8.5, but there is still this "internal server error" for both of my Dotclear installations.
When searching the internet we find that OVH was hacked for 1 hour and 34 minutes. Does that have anything to do with it?
Just in case @Rallarros, have you switched the hosting to development mode?
See the paragraph in my guide: P2 - Erreur 500 - Environnement développement
Hello,
OVH distributes a software "ovhcloud-cli" primarily aimed at IT experts and professionals.
If you use ovhcloud-cli and you downloaded a version during that one‑hour‑plus window, and you installed and used it, you have been hit by a malicious thing.
If you've never heard of ovhcloud-cli, you are not affected.
Game over.
Did you check your web error logs as I suggested?
In the meantime, it seems that if you have chosen php-cgi in your PHP configuration, you should choose php-fpm or php.
Don't forget that we are facing a global problem; I think OVH has done quite well in this regard. OVH is the only hosting provider, to my knowledge, that offers as many PHP versions to its users, and has to recompile them all...
Thank you for your answers.
If I switch to php-fpm or php, is it compatible with my Dotclear?
Software incompatible with php-fpm because the configuration at OVH seems not to pass environment variables in the usual way. So I have no choice but to use php-cgi.
The error is "End of script output before headers: index.php" probably due to a lack of CGI response.
Try it, it shouldn’t break anything. Replace phpcgi in .ovhconfig with php. It’s reversible if needed.
My sites were launched on June 6, 2006, over 20 years ago—so that’s 2 × 20 years of work.
I can’t afford to try it just to see if it should.
It's reversible.
And not having maintained the sites for 20 years isn’t a valid answer. Sorry for you.
Can you show the contents of the .ovhconfig file found in the /travelblog/ subdirectory?