- Plesk Obsidian for Linux
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:
# grep 'status installed' /var/log/dpkg.log | grep apache2:amd64
2021-09-27 12:46:57 status installed apache2:amd64 2.4.41-4ubuntu3.5
# 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
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.
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.
Same here: I had to restore the entire server this morning. First action: I've disabled the auto-update under "Tools and Settings > "Update Settings" > and uncheck all "Auto install [...]". From now i will run the updates manually.
Thanks for share
I think I will put apache updates on hold forever after this little gem ;-)
Fixed! Thanks for the quick fix ;)
Using the suggested version="2.4.41-4ubuntu3" always gave me an error about the version not being available. The solution in that case seems to first check which versions are available locally and then downgrade to that version:
This gives the information that version="2.4.29-1ubuntu4" is available and can be used:
It works for us: Ubuntu 18.04.6 LTS and Ubuntu 20.04.3 LTS, but issues like this must be prevented in first place, It seems that Plesk does not have a staging environment to test upgraded packages from distro in first place.
Such a light-minded attitude from a professional vendor?
Thanks so much for the workaround.
So will someone let us know, when this is fixed and to "undo" the workaround we just did to get the sites back online again?
initial comments on how to fix ubuntu 20.04 worked for me via terminal... I too was thinking my server had been compromised, checking history, logs, htop etc for malicious activity so glad it was a simple fix.
This is why I hate system wide updates by automatically... Oden plesk has been ok overall but even this is a reminder about scheduling updates vs assumed trust.
Oden, feature request (not the place I know) add ipset and some geoip ip sets to firewall app please, we do this manually to prevent hacks iptables+ipset with cron to add and check rules added after plesk changes adjust firewall rules to iptables. (block email ports except customers geo zone vs whole of internet etc)
After "apt-mark hold apache2" I guess some manual changes needed to unhold after plesk maintenance release?
Will you notify here all updates about this issue?
This cannot be emphasised enough:
A breaking bug like this is serious and I hope to see Plesk coming up with a statement regarding this and how they will make sure to prevent this in the future.
Thanks for the really quick fix, so glad this was at the top of Google. The two line solution for Ubunutu 20.04 worked perfectly and brought websites back online almost instantly.
FastCGI workaround worked for me.
Ubuntu 18.04.6 in Vultr
Thanks... now is time for coffee.
I just ran the command given by @Reinhold Kainhofer and looks like another server of mine still working with the new update. am I right to assume that? I'm just worried to key in the work around as I have very very (almost no knowledge) working with CLI
Thanks a lot !!
I am running plesk on 1und1 server and I face this problem today ... by executing your commands , I really get my server back....
Thank you. It worked and saved me.
thankyou for fast solution, this morning i wake up with this error....
2021-09-28 07:00:12 status installed apache2:amd64 2.4.29-1ubuntu4.17
root@plesk:~# export version="2.4.29-1ubuntu4"; apt-get install apache2=$version apache2-utils=$version apache2-data=$version apache2-bin=$version
Reading package lists... Done
Building dependency tree
Reading state information... Done
E: Version '2.4.29-1ubuntu4' for 'apache2' was not found
E: Version '2.4.29-1ubuntu4' for 'apache2-utils' was not found
E: Version '2.4.29-1ubuntu4' for 'apache2-data' was not found
E: Version '2.4.29-1ubuntu4' for 'apache2-bin' was not found
WURK you are probably using the 20.04 instructions for 18.04 server
Ubuntu 18.04 on AWS gives this error both with or without sudo for the following command:
export version="2.4.29-1ubuntu4"; apt-get install apache2=$version apache2-utils=$version apache2-data=$version apache2-bin=$version
E: Could not open lock file /var/lib/dpkg/lock-frontend - open (13: Permission d enied)
E: Unable to acquire the dpkg frontend lock (/var/lib/dpkg/lock-frontend), are y ou root?
Thanks it's working
what helped me was to (all in Plesk UI):
1. change to "FPM Application served by nginx" instead of Apache, in "PHP settings" for the domain.
2. in "Apache & nginx Settings" switched off "Proxy mode".
Now my sites are online.
I hope this helps!
Anyway the provided "solution" above is not a solution, just a workaround, I would still expect a fix with the next update.
If the workaround is not working for you, please read the previous comments before replying here.
thanks man! I'm worried to key in anything because I dont understand what the commands are doing and I'm worried I might break my server
on our website doesnt work the fix.
The following packages will be DOWNGRADED:
apache2 apache2-bin apache2-data apache2-utils
0 upgraded, 0 newly installed, 4 downgraded, 0 to remove and 4 not upgraded.
E: Packages were downgraded and -y was used without --allow-downgrades.
root@localhost:~# apt-mark hold apache2
apache2 was already set on hold.
any suggest please? thanks
Automated script to fix that problem in all Proxmox containers. Could be interesting for someone.
If, after the downgrade of Apache, you're still having trouble, it might be that your SSL settings contain +TLS1.3. The downgraded version does not support that.
Like everyone else - Thank you for the quick response to this.
Marcel Kallen Unfortunately not. So no prevail. Managed to get the most important sites up running by running PHP throuhg NGINX and disable Proxy Mode. Have a running ticket, as I have waaaaay too many Plesk servers running to answer all calls alone.
Questioning how this have happened though as all my auto updates are intentionally disabled.
Please sign in to leave a comment.