• If you are still using CentOS 7.9, it's time to convert to Alma 8 with the free centos2alma tool by Plesk or Plesk Migrator. Please let us know your experiences or concerns in this thread:
    CentOS2Alma discussion

Issue All Domains Apache2/Error 500

jackson said:
Yes, had this automatic update on our server lastnight, killed 80 websites instantly...

Ran these commands to update to Apache 2.4.49 (Which has fixed the problem for me) - for anyone who isn't tech savvy.

Code: 
sudo add-apt-repository ppa:ondrej/apache2
sudo apt install apache2
Click to expand...
I'm not tech savvy at all and this brought back my websites to life. Thanks.
 
jackson said:
Yes, had this automatic update on our server lastnight, killed 80 websites instantly...

Ran these commands to update to Apache 2.4.49 (Which has fixed the problem for me) - for anyone who isn't tech savvy.

Code: 
sudo add-apt-repository ppa:ondrej/apache2
sudo apt install apache2
Click to expand...

When I try to update Apache it just hangs there, does it take a long time? This is what I see after I run the first command:

Code: 
/etc/apache2/sites-enabled$ sudo add-apt-repository ppa:ondrej/apache2
 This branch follows latest Apache2 packages as maintained by the Debian Apache2 team with couple of compatibility patches on top.

It also includes some widely used Apache 2 modules (if you need some other feel free to send me a request).

IMPORTANT: The <foo>-backports is now required on older Ubuntu releases.

BUGS&FEATURES: This PPA now has a issue tracker: https://deb.sury.org/#bug-reporting

PLEASE READ: If you like my work and want to give me a little motivation, please consider donating: https://deb.sury.org/#donate
 More info: https://launchpad.net/~ondrej/+archive/ubuntu/apache2
Hit:1 http://ppa.launchpad.net/ondrej/apache2/ubuntu bionic InRelease
Hit:2 http://archive.ubuntu.com/ubuntu bionic InRelease
Get:3 http://archive.ubuntu.com/ubuntu bionic-updates InRelease [88.7 kB]
Get:4 http://archive.ubuntu.com/ubuntu bionic-backports InRelease [74.6 kB]
Hit:5 http://autoinstall.plesk.com/PMM_0.1.11 bionic InRelease
Hit:6 http://autoinstall.plesk.com/pool/PSA_18.0.38_6986 bionic InRelease
Hit:7 http://autoinstall.plesk.com/pool/PHP_7.2.34_150 bionic InRelease
Hit:8 http://autoinstall.plesk.com/PHP73_17 bionic InRelease
Hit:9 http://autoinstall.plesk.com/PHP74_17 bionic InRelease
Get:10 http://security.ubuntu.com/ubuntu bionic-security InRelease [88.7 kB]
Hit:11 https://download.imunify360.com/ubuntu/18.04/slot-1 bionic InRelease
Hit:12 https://download.imunify360.com/ubuntu/18.04/slot-2 bionic InRelease
Hit:13 https://download.imunify360.com/ubuntu/18.04/slot-3 bionic InRelease
Hit:14 https://download.imunify360.com/ubuntu/18.04/slot-4 bionic InRelease
Fetched 252 kB in 1s (192 kB/s)
Reading package lists...

And then when I run the second command (install) it hangs forever:

FDpf68r.png
 
jackson said:
Yes, had this automatic update on our server lastnight, killed 80 websites instantly...

Ran these commands to update to Apache 2.4.49 (Which has fixed the problem for me) - for anyone who isn't tech savvy.

Code: 
sudo add-apt-repository ppa:ondrej/apache2
sudo apt install apache2
Click to expand...

This did the trick, waiting for the fix to put ppa:eek:ndrej/apache2 back online if needed (I think it's a Plesk added ppa?)
Thanx all,
 
AntonM@Parallels said:
Based on what we know, we prepared a knowledge base article:
support.plesk.com

Website suddenly started to show 500 error: AH10292: Invalid proxy UDS filename

Applicable to: Plesk Obsidian for Linux Symptoms The website suddenly started to show 500 error: PLESK_ERROR: AH10292: Invalid proxy UDS filename (proxy:unix:///var/www/vhosts/system/example.co...
support.plesk.com support.plesk.com
Click to expand...

@AntonM@Parallels

Thank you for the clean solution - that is, solution ("work-around") number 2.

Solution number 1 ("Switch to FastCGi instead of PHP-FPM") is not really a viable option - it is a dirty work-around and will cause configuration related issues when working with Nginx, certainly when working actively with Nginx : for instance, when using Nginx as a proxy with caching functionality.

It would also have been a good suggestion to push this solution as a small and fast update by Plesk.

Could you be so kind as to make sure that any formal Plesk fix will include an automatic apt-mark unhold apache2 command?

Kind regards.......
 
trialotto said:
Could you be so kind as to make sure that any formal Plesk fix will include an automatic apt-mark unhold apache2 command?
Click to expand...
We cannot do this automatically because it can affect those who have done it previously on purpose for some reason. But we will indicate in the KB article or the release notes to remove the hold on their own after installing the update.
 
Guys, over the next few hours, we will give a more straightforward solution than the described KB article.
In addition, we are working in the ASAP mode to release an update with a fix.
 
IgorG said:
We cannot do this automatically because it can affect those who have done it previously on purpose for some reason. But we will indicate in the KB article or the release notes to remove the hold on their own after installing the update.
Click to expand...
@IgorG,

In essence, you are right - I did not think about that.

Nevertheless, I do not think that it is smart for other people to put any package on hold, whatever reason there might be.

However, from the perspective of Plesk, it does make sense to not add an automatic unhold.

Kind regards....
 
jackson said:
Yes, had this automatic update on our server lastnight, killed 80 websites instantly...

Ran these commands to update to Apache 2.4.49 (Which has fixed the problem for me) - for anyone who isn't tech savvy.

Code: 
sudo add-apt-repository ppa:ondrej/apache2
sudo apt install apache2
Click to expand...
It works, thanks!
 
IgorG said:
Guys, over the next few hours, we will give a more straightforward solution than the described KB article.
In addition, we are working in the ASAP mode to release an update with a fix.
Click to expand...
@IgorG

A release of an update with a fix would be preferred.

I am interested in what a "more straightforward solution" would be, since in any (pretty standard) Plesk instance, the current KB fix works like a charm.

I have tested some other solutions, but it all boils down to required changes on the PHP-FPM side, in particular the UDS (socket) side.

In short, I am eager (and curious) to see the progress in this matter!

Again, thanks for the proactive attitude.

Kind regards....
 
AntonM@Parallels said:
The issue occurs as well on Ubuntu 18 and Ubuntu 20 which are installing Apache update from default OS repositions. So far consider one of the following workarounds:
1. Switch to FastCGi instead of PHP-FPM
2. Downgrade Apache to previous version:
  1. Find previously installed Apache version, based on below output you may see it is "2.4.41-4ubuntu3"
    # apt-cache showpkg apache2 | tail
    2.4.41-4ubuntu3.5 - httpd-cgi (= ) httpd (= )
    2.4.41-4ubuntu3 - httpd-cgi (= ) httpd (= )
    Reverse Provides:
  2. Now downgrade Apache to previous version, replace the value for the "version" variable with the one you found on previous step:
    # export version="2.4.41-4ubuntu3"; apt-get install apache2=$version apache2-utils=$version apache2-data=$version apache2-bin=$version
  3. Put it on hold until fix is available:
    # apt-mark hold apache2
Click to expand...
That was the solution! Thanks a lot! The 2nd beer is on me!
 
Temporal solution that works for me:

Updating on file /var/www/vhosts/system/example.com/conf/httpd.conf:

SetHandler proxy:unix:///var/www/vhosts/system/example.com/php-fpm.sock|fcgi://127.0.0.1:9000

to

SetHandler proxy:unix:/var/www/vhosts/system/example.com/php-fpm.sock|fcgi://127.0.0.1:9000

and restarting apache service
 
aamche2 said:
Get Versions, choose an earlier version, 2.4.29-1ubuntu4 may not be your system so adjust the install command (below) to an earlier version that you see.
Code: 
apt list -a apache2

Downgrade version (some dependancies)
Code: 
apt-get install apache2=2.4.29-1ubuntu4 apache2-bin=2.4.29-1ubuntu4 apache2-utils=2.4.29-1ubuntu4 apache2-data=2.4.29-1ubuntu4
Click to expand...
Thanks for this, saved all of our websites.
 
You know, the other way to fix this regardless of the apache version would be to change the unix socket urls from unix:/// to unix:/ ...
 
Solution for fix all domains:

Update /opt/psa/admin/conf/templates/default/service/php_over_fpm.php file from:


Apache config: 
<IfModule mod_proxy_fcgi.c>
    <Files ~ (\.php$)>
        SetHandler proxy:<?php echo $VAR->domain->physicalHosting->fpmSocket ?>|fcgi://127.0.0.1:9000
    </Files>
</IfModule>


to


Apache config: 
<IfModule mod_proxy_fcgi.c>
    <Files ~ (\.php$)>
        SetHandler proxy:<?php echo str_replace("///","/", $VAR->domain->physicalHosting->fpmSocket) ?>|fcgi://127.0.0.1:9000
    </Files>
</IfModule>

and rebuild all webserver configuration files



and rebuild all webserver configuration files
 
Please pay your attention to the forum Note with the exclamation mark. Thanks.
 
For those using Ondrej Sury's PPA, he does seem to have pulled the fix into his repo. I can confirm that adding his repo again and updating Apache to v2.4.49 no longer presents the error. All my websites are back up and running again.
 
You must log in or register to reply here.

Similar threads

E
Issue Server Error 500 Internal Server Error
Replies
5
Views
343
Peter Debik
P
A
Question Error 500 and no logs available
Replies
8
Views
2K
Jan Bludau
Jan Bludau
K
500 internal server errore CP admin
Replies
0
Views
290
k23
K
V
500 Internal Server Error after disabling password protection - WP Toolkit
Replies
1
Views
597
Peter Debik
P
A
Issue Error 500 on POST request
Replies
1
Views
790
gustavowoltmann
gustavowoltmann
Back
Top