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

Follow

Comments

318 comments

  • Avatar
    Muhammed Faiz Seitz

    Thank you very much for the quick workaround. I was still trying to use the 1st workaround but then it updated by the time I figured out how to SSH. AWS Lightsail actually makes it quite easy. Well we live and we learn hey...

    0
    Comment actions Permalink
  • Avatar
    Johan Adriaans

    I just replaced PhysicalHosting.php, rebuilt all configs, removed the hold from apache2 and ran the updates to the version that caused all problems this morning. Looks fixed! Everything works like it should. Thanks for this permanent fix!

    1
    Comment actions Permalink
  • Avatar
    Andreas Giesen (Edited )

    //I applied the workaround, but only some of my sites came back up. Some still show the 500 error. I tried switching to FastCGI on one of those with no effect. The error shown for those sites in the log is still AH10292.... 

    Solved: For those domains I had special settings set in Plesk to include in httpd.conf which were overriding the fix. Someone mentioned changing the proxy URL (/// to /) for the domains and the "Apache and Nginx Settings" were where that needed to be changed, too... 

     

    2
    Comment actions Permalink
  • Avatar
    Johan Adriaans (Edited )

    @Nick H - The new fix needs to be run as root. If you want to use sudo, make sure you add it to the tar command:

    wget https://support.plesk.com/hc/en-us/article_attachments/4407402583954/PPPM-13232.tgz && sudo tar -xvf PPPM-13232.tgz -C /usr/local/psa/admin/plib/Template/Variable/Domain/
    1
    Comment actions Permalink
  • Avatar
    Coopsy (Edited )

    ive also just done the fix and confirm the actions above Johan Adriaans worked (so far) like a charm. many thanks

    0
    Comment actions Permalink
  • Avatar
    Chris Tierney

    Urgh, does anyone know how I can implement a fix using Plesk for Web??? I'm all at sea here.... 

    0
    Comment actions Permalink
  • Avatar
    Benjamin

    Would be great to get some official statement from Plesk regarding the issue. I understand this is maybe related to an apache2 update problem initially, but I have been blindly taking for granted that Plesk has some sort of mechanism for staging or trying out new releases before they are pushed to all the production environments. I can see the issue popping up on the Plesk forum more then a week ago: https://talk.plesk.com/threads/all-domains-apache2-error-500.362208/

    Well the user that reported it did not use the official Ubuntu packages but rather the repository of Ondrej Sury which maintains packages of PHP and Apache for Debian/Ubuntu and releases updates more frequently since it appears he also works on apache itself. He reported it to Ondrej Sury on 22nd so sure enough Ondrej fixed it directly at apache but on time for Ubuntu's new release.

    0
    Comment actions Permalink
  • Avatar
    Jose de Vega

    Benjamin Weßel,

    I cant read the new code so, have you reviewed the use of the variable $VAR->domain->physicalHosting->fpmSocket on all the sourcecode?

    For example it is been used also on /opt/psa/admin/conf/templates/default/domain/service/fpm.php (used by nginx domains not using "Proxy mode")

    fastcgi_pass "<?php echo $VAR->domain->physicalHosting->fpmSocket ?>";

    It could generate

    fastcgi_pass "unix:/var/www/vhosts/system/example.com/php-fpm.sock";
    

    instead of

    fastcgi_pass "unix:///var/www/vhosts/system/example.com/php-fpm.sock";
    

    Thanks

     

    1
    Comment actions Permalink
  • Avatar
    Jonathan Burrows

    Had this scratched my head for ages and found this page. However, I'm getting the below when running the command:


    Saving to: ‘PPPM-13232.tgz’

    PPPM-13232.tgz 100%[=================================================>] 33.40K --.-KB/s in 0.002s

    2021-09-28 12:41:24 (19.4 MB/s) - ‘PPPM-13232.tgz’ saved [34203/34203]

    PhysicalHosting.php
    tar: PhysicalHosting.php: Cannot open: File exists
    tar: Exiting with failure status due to previous errors

     

     

    1
    Comment actions Permalink
  • Avatar
    Jonathan Burrows

    Running wget command now (as of 13:47 28-09-2021) 404 not found

    wget https://support.plesk.com/hc/en-us/article_attachments/4407402583954/PPPM-13232.tgz && tar -xvf PPPM-13232.tgz -C /usr/local/psa/admin/plib/Template/Variable/Domain/
    --2021-09-28 12:46:44-- https://support.plesk.com/hc/en-us/article_attachments/4407402583954/PPPM-13232.tgz
    Resolving support.plesk.com (support.plesk.com)... 104.16.53.111, 104.16.51.111
    Connecting to support.plesk.com (support.plesk.com)|104.16.53.111|:443... connected.
    HTTP request sent, awaiting response... 404 Not Found
    2021-09-28 12:46:44 ERROR 404: Not Found.

    0
    Comment actions Permalink
  • Avatar
    Thorsten Bachner

    Why there`s a different workaround than 1 hour? I already downgraded my Apache Version and set it to hold. What to do best?

    1
    Comment actions Permalink
  • Avatar
    Alex Hofbauer

    Thank you! You saved me a lot of work!

    Workaround changing it to "Run PHP as FastCGI Application" worked also for me. But your solution is much better. Thx!

    0
    Comment actions Permalink
  • Avatar
    Jonathan Burrows (Edited )


    sudo wget https://plesk.zendesk.com/hc/article_attachments/4407403144722/PPPM-13232.tgz && sudo tar -xvf PPPM-13232.tgz -C /usr/local/psa/admin/plib/Template/Variable/Domain/

    0
    Comment actions Permalink
  • Avatar
    kiki

    Thank you so much for the quick support

     

    0
    Comment actions Permalink
  • Avatar
    Subhash Gottumukkala

    Can you explain how to do that? I'm not good at understanding these things but my website has been down for several hours.

    0
    Comment actions Permalink
  • Avatar
    Em loop

    On AWS Lightsail the wget command  throws 404

    https://plesk.zendesk.com/hc/article_attachments/4407403144722/PPPM-13232.tgz - 404

    This workaround works easily.

    sudo add-apt-repository ppa:ondrej/apache2
    sudo apt install apache2

    If asked to keep log rotation confs, answers NO

     

     

    0
    Comment actions Permalink
  • Avatar
    Johan Adriaans

    @Thorsten Bachner

    Downgrading and locking apache is not future proof. It is a temporary fix. The new version is a permanent fix.

     

    0
    Comment actions Permalink
  • Avatar
    Benjamin

    So I've just installed the new Apache2 Version from Ubuntu which has not been released officially yet and without the new workaround (to PhysicalHosting.php) this works as it should. New Version for Ubuntu 20.04 will be 2.4.41-4ubuntu3.6

    So once this releases officially and plesk updates, it will be fixed permanently.

    (I've upgraded from the downgraded apache, so it's 2.4.41-4ubuntu3.5 -> 2.4.41-4ubuntu3 -> 2.4.41-4ubuntu3.6)

    2
    Comment actions Permalink
  • Avatar
    John Phipps

    This is getting difficult to keep up with.

    For those of us that ran the downgrade and hold commands earlier, can someone clearly explain what we need to do now?

    I don't see an unhold update above nor do I understand whether we unhold apache and then manually re-run the update or wait for plesk to do it.

    It would really help to get a clear set of instructions for those who actioned the downgrade and those who didn't.

    0
    Comment actions Permalink
  • Avatar
    Gerard Korver (Edited )

    I changed everything to  select "FastCGI application served by Apache" and it all works again. Lost close to a day with a number of websites

    0
    Comment actions Permalink
  • Avatar
    Jonathan Burrows

    Just to clarify that the below worked for me:

    sudo wget https://plesk.zendesk.com/hc/article_attachments/4407403144722/PPPM-13232.tgz && sudo tar -xvf PPPM-13232.tgz -C /usr/local/psa/admin/plib/Template/Variable/Domain/

    NOTE: the sudo commands at the beginning of the line and also before the tar command.

    The second command above to reload configuration also needs the sudo command:

     sudo plesk sbin httpdmng --reconfigure-all

     

    0
    Comment actions Permalink
  • Avatar
    Nipuna Maduranga (Edited )

    Alright guys, here's the workaround if you are using Ubuntu 20.04. Im not sure about Ubuntu 18.04, but this should work.

    1) Login to your plesk dashboard

    2) Click on your domain name you would like to do these changes.

    3) Go to PHP Settings

    4) On the top of the page where it says "run PHP as" select "FastCGI application served by Apache"

    5) Scroll all the way to the bottom and click Apply and OK

    If the above method doesn't workout for you, try the next solution which is,

    1) Again, Go to PHP Settings

    2) On the top of the page where it says "run PHP as" select "FPM application served by nginx"

    3) Scroll all the way to the bottom and click Apply and OK

    4) Now, Click on Hosting and DNS

    5) Click on Apache and nginx Settings

    6) Scroll down to nginx settings

    7) Uncheck "Proxy mode"

    8) Hit Apply and OK

    Enjoy :)

    All we can do is to wait patiently until the Plesk team releases a stable fix for this issue, if you dont know what you are doing with SSH, stay away from it as it can mess things up, just a heads up, unless you really have experience with SSH and clearly know what you are doing :)

    1
    Comment actions Permalink
  • Avatar
    Dave Luscombe

    Had just started receiving calls from clients.  Thank-you for the quick fix

    0
    Comment actions Permalink
  • Avatar
    Felix Gade

    @Thorsten Bachner

    1. Remove the hold status for apache2

    # apt-mark unhold apache2

    2. Update & Upgrade

    # apt-get update & apt-get upgrade

    3. Replace the updated version of PhysicalHosting.php

    # wget https://plesk.zendesk.com/hc/article_attachments/4407403144722/PPPM-13232.tgz && tar -xvf PPPM-13232.tgz -C /usr/local/psa/admin/plib/Template/Variable/Domain/

    4. Rebuild webserver config

    # plesk sbin httpdmng --reconfigure-all

    1
    Comment actions Permalink
  • Avatar
    Daniel Gutierrez

    Thx a lot! I'm working with a DO droplet that included plesk, and the quickfix worked great. Is there a newsletter or something where I can be updated in realtime of these events?

    0
    Comment actions Permalink
  • Avatar
    John Phipps (Edited )

    Felix Gade

    Thank you for that. It all worked apart from step 3 where I got a 404

    To fix that, I ran the command again and it worked.

    Rechecked which Apache version is installed and it's back to

    2021-09-28 14:25:19 status installed apache2:amd64 2.4.41-4ubuntu3.5

    0
    Comment actions Permalink
  • Avatar
    Phil Loaiza

    @Hostworks Admin

    Is it possible that you have some websites set up with FPM and some with FastCGI? 

    0
    Comment actions Permalink
  • Avatar
    Eduardo Ortiz Ramírez

    Today we woke up to more than 35 sites down, I was lucky enough to find this post, the previous version didn't stated to run the commands as sudo but we made it work anyways. Thank you and please keep us posted.

    0
    Comment actions Permalink
  • Avatar
    mike (Edited )

    Felix Gade

    Tried the latest fix and getting this missing trait error when running

    # plesk sbin httpdmng --reconfigure-all

     

    Details: PHP Fatal error: Trait 'Template_Variable_Domain_SslTrait' not found in /opt/psa/admin/plib/Template/Variable/Domain/PhysicalHosting.php on line 48
    Curl failed: SSL peer certificate or SSH remote key was not OK

     

    Please help.

    0
    Comment actions Permalink
  • Avatar
    Kenneth Nguyen

    Please escalate the help... I got flooding server errors from the app api impacting lots of users

    [Tue Sep 28 06:34:45.715574 2021] [proxy:error] [pid 14836:tid 140299611342592] [client 47.145.99.21x:49404] AH10292: Invalid proxy UDS filename (proxy:unix:///var/www/vhosts/system/...
    [Tue Sep 28 06:34:45.850470 2021] [proxy:error] [pid 14836:tid 140299602949888] [client 47.145.99.21x:49406] AH10292: Invalid proxy UDS filename (proxy:unix:///var/www/vhosts/system/..
    [Tue Sep 28 06:34:45.974177 2021] [proxy:error] [pid 14864:tid 140299720447744] [client 47.145.99.21x:49408] AH10292: Invalid proxy UDS filename (proxy:unix:///var/www/vhosts/system/...
    [Tue Sep 28 06:34:46.158366 2021] [proxy:error] [pid 14864:tid 140299661698816] [client 47.145.99.21x:49410] AH10292: Invalid proxy UDS filename (proxy:unix:///var/www/vhosts/system/...
    [Tue Sep 28 06:34:46.529260 2021] [proxy:error] [pid 14864:tid 140299653306112] [client 47.145.99.21x:49412] AH10292: Invalid proxy UDS filename (proxy:unix:///var/www/vhosts/system/...

    0
    Comment actions Permalink

Please sign in to leave a comment.

Have more questions? Submit a request