Applicable to:
- Plesk Obsidian for Linux
Symptoms
-
Websites show the following error:
CONFIG_TEXT: AH10292: Invalid proxy UDS filename (proxy:unix:///var/www/vhosts/system/example.com/php-fpm.sock|fcgi://127.0.0.1:9000/var/www/vhosts/example.com/httpdocs/public/index.php)
CONFIG_TEXT: Internal Server Error
-
Apache has been updated to a new version recently:
Ubuntu 20.04:
# grep 'status installed' /var/log/dpkg.log | grep apache2:amd64
2021-09-27 12:46:57 status installed apache2:amd64 2.4.41-4ubuntu3.5Ubuntu 18.04:
# grep 'status installed' /var/log/dpkg.log | grep apache2:amd64
2021-09-28 06:25:55 status installed apache2:amd64 2.4.29-1ubuntu4.17
Cause
This is an Apache bug which arose with Ubuntu packages update and later fixed in the following versions:
- Apache for Ubuntu 20 version 2.4.41-4ubuntu3.6.
- Apache for Ubuntu 18 version 2.4.29-1ubuntu4.18.
Plesk uses Apache packages from OS repositories and does not control their version updates.
Resolution
Update Apache packages to fix the issue:
-
Go to Tools & Settings > Server Management > System Updates and click Recheck now.
-
Once updates are detected, click Update all.
The issue should be fixed, verify that websites are back online.
-
Connect to the server using SSH.
-
Execute below command:
# sudo apt-mark unhold apache2
-
Apply steps 2-3 from the resolution.
Comments
318 comments
Great day for the Plesk tech and sales department not to communicate! Just received notice of the 10% price increase that comes into effect from January, on the very same day that all of your clients web pages goes down, at the same time :)
I ran the workaround above. I don't believe the extra step 4 was up when I ran this so I did not # runapt-mark unhold apache2
It did get my site up and running again but I now see the following error at the top of the Website & Domains screen.
@Andreas Giesen - Thanks for posting that additional workaround. I had to apply it to one of my older sites where I had some special settings in place. Switching from /// to / worked perfectly!
Please Can someone tell me how to fix the 500 error ? I don't understand what this article is indicating
@Ajcornejo
I'd contact Plesk Support. This is not something that should happen when you apply this fix.
it is not clear how to update ,
poor quality services
Thanks you so much, please keep me updated if you get a permanet solution
It worked for me.
However, when will the definitive fix come?
Thanks for addressing the issue so quickly.
it worked for digital ocean server but not working for Lightsail any fix for Lightsail
ubuntu just pushed the updates 5 minutes ago, so if you're still affected, scan for updates (Tools & Settings -> System updates -> Recheck Now) and install.
I have followed all the steps and now I can see the websites but all pages show me a 404 error
So the fixed packages for Ubuntu have landed on the primary (US?) mirror 20 Minutes ago. It will take a while to be mirrored to regional mirrors.
People who marked the apache2 package for hold have to unhold the package:
Then update the packages
Everyone who implemented the second workaround (updating PhysicalHosting.php) can just wait for the updated packages to be automatically installed by Plesk.
Everyone who hasn't done anything yet:
Or I think just "Check for Upgrades" and install upgrades via Plesk Webinterface (never used it tbh).
Again, it will take a few hours for all mirrors to mirror the new packages, so in any case you do the following:
This adds Ubuntus primary mirror to apt and you should get the new apache packages.
Upgrading apache WILL be the permanent fix.
OMG, thanks for the fast solution!!!!!!!!!
I just confirmed that the update package (Tools & Settings > System Updates > Recheck Now) and updating to the newest version fixed the problem for me allowing me to update AND unhold apache2 upgrade. So if you are uncomfortable in SSH or just do not want to do that manually, then you can run it through the update screen within Plesk now.
Thanks @Mark-Oliver Wolter for the update, as this is what I was personally waiting for, an official update to it.
Per me funziona.
Grazie!
Worked the new updates by web interface and put back PHP - FPM aplication served by apache and the site on Digital Ocean is ON.Thanks i hope it solved everthing.
Thanks for the fast solution.
Thanks! Server just updated and broke everything. Cheers.
When your customers are loosing money because of a bugs like these (e-commerces down for hours), unfortunately a simple "We are sorry" is not enough. This should never happen in an Web Server Administration Platform... Updates on so crucial components on the server should be tested before being applied on the server... Who's gonna pay our customers that losed money and who's gonna pay our customer unsatisfaction and untrust...
Thanks for the quick fix!
why in this post is not officially recommended the simpler solution to switch PHP-fpm to FastCGI? It's the simplest and faster way to temporary solve the issue, without making changes on the server by ssh, and you can do it simply unflagged a checkbox in apache-nginx Plesk's configuration panel...
La solución temporal para todos los servidores que tengo con 20.04 es cambiar de FPM nginx a FastCGI Apache, a la espera de la actualización que regulariza este problema.
Thank you! Perfect solution. Well done!
I see numerous methods in the comments on how to fix this with the Ubuntu update available. Will Plesk eventually post a detail on how to handle this once the Ubuntu update has been tested?
I ran the workaround earlier this morning and it got my site running albeit with some error messages on my Website & Domain screen. It seems like the workaround was changed from when I first ran it this morning with an additional 4th step added about unholding the apache package.
workaround worked/works but the new update doesn't work for me- so I reverted and use the workaround still
Is the fixed Apache version only for ubuntu 20.04? I'm running 18.04 and can't get the update via Tools & Settings etc.
are there any future problem if i leave the main mirror inside? could not get the updated apache yet, but with the main mirror it worked., Can i let it there?
This comment/fix from Benjamin: https://support.plesk.com/hc/en-us/articles/4407366133906/comments/4407405402386 worked for me on both Ubuntu 18.04.6 and Ubuntu 20.04.3 on DigitalOcean.
I had first done the fix with a rollback of Apache2 update and then hold updates, for me it was enough to do the following:
-----------------------------------------------------------------------------------
People who marked the apache2 package for hold have to unhold the package:
sudo apt-mark unhold apache2
Then update the packages
sudo apt update && sudo apt upgrade
-----------------------------------------------------------------------------------
please advise
my plesk licence is not active i have no access to root ,
how to sort out this problem ?????
apt-mark unhold apache2 geht nicht Super klasse
Und nun ?????????????
Please sign in to leave a comment.