On October 19, 2021, we have enabled single-sign-on for our Plesk Support Center to provide a seamless login/account experience. This implies that you’ll be able to use a single account across any of our web-facing properties.
If you had already registered your account at Plesk 360 (formerly known as My Plesk) please use one for login. Otherwise please re-register it using the same email address as your existing Zendesk login (support account). It’s essential that you use the same email address on our support center to ensure that your tickets stay attached to the same account.

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

Follow

Comments

315 comments

  • Avatar
    Mitchell Musarra

    Thank you so much for providing a fast work-around to this issue!

    26
    Comment actions Permalink
  • Avatar
    BagusAs

    This bug gives me a heart attack, i thought something bad happens with my servers. Glad it solved with simple step. Thank You

    19
    Comment actions Permalink
  • Avatar
    BokLa

    OMG, same here. Woke up sweating. Thanks for the quick fix.

    6
    Comment actions Permalink
  • Avatar
    Lee Wai Hong (Edited )

    Thanks for the solution.
    https://support.plesk.com/hc/en-us/articles/4407366133906

    -1
    Comment actions Permalink
  • Avatar
    Domix Domenico Pugliese

    Is the downgrade from 2.49 to 2.41? I have 2.41 and the problem is the same. Error 500 in sites

    2
    Comment actions Permalink
  • Avatar
    Anton Maslov

    Domix Domenico Pugliese downgrade is from 2.4.41-4ubuntu3.5 to 2.4.41-4ubuntu3, if you have 2.4.49 you are using likely non-default Ubuntu repository. Make sure you downgrade to "2.4.41-4ubuntu3" specifically, as 2.4.41-4ubuntu3.5 is affected.

    0
    Comment actions Permalink
  • Avatar
    Domix Domenico Pugliese

    I Have installed version 2.4.41

    Server Built: 2021-09-23T

    can i use your solution? I don't want to make it worse

    Thanks

    0
    Comment actions Permalink
  • Avatar
    Domix Domenico Pugliese

    Thanks Very well. The your solution is ok

    0
    Comment actions Permalink
  • Avatar
    Travis Ecclestone

    Help.  Export doesn't seem to function on AWS Lightsail Ubuntu 20

     

    0
    Comment actions Permalink
  • Avatar
    Michael Luchich

    Thanks for the workaround. Is there any way updates like this can be validated in a test environment before they are pushed out? I spent a few hours working around this issue before this article was published. 

    16
    Comment actions Permalink
  • Avatar
    Jason Koning

    I totally agree - why did this happen in the first place? Just an unfortunate occurrence, or something that could be caught with a better process before being pushed?

    9
    Comment actions Permalink
  • Avatar
    Grow

    hi I'm also facing this issue, how do I do this from the plesk control panel? I have no idea how to implement this and about 8 of my sites are down

    0
    Comment actions Permalink
  • Avatar
    Michael Luchich

    Grow You need to run the commands listed in the article from the shell ( i think as root user). 

    Other work arounds that I found are to turn of the apahce proxying and use nginx (this may be problematic if you have special stuff in your .htaccess files) in Hosting/Apache & nginx Settings   , or to change the apache handler in Hosting/Hosting Settings to FAST CGI served by Apache - this will possibly reduce the performance. 

    You will need to do this for each site. Try one first.

     

    0
    Comment actions Permalink
  • Avatar
    Jason Koning

    you need to SSH to your server to run those commands, using a terminal

    2
    Comment actions Permalink
  • Avatar
    Grow

    Hey Jason, I'm a noob with CLI but fortunately I can access the terminal through my aws lightsail account. should I just key in the command given above and pray that it works?

    # apt-mark hold apache2
    # export version="2.4.41-4ubuntu3"; apt-get install apache2=$version apache2-utils=$version apache2-data=$version apache2-bin=$version
    0
    Comment actions Permalink
  • Avatar
    Tarun

    Yes this works ! 

    0
    Comment actions Permalink
  • Avatar
    Alphan Nguyen (Edited )

    Alternative Solution: Use FastCGI

    I have to manually switch to FastCGI instead of FPM for all my domains / subdomains

    Any advantages ot FastCGI ?

    8
    Comment actions Permalink
  • Avatar
    Wilko van der Ploeg

    I tried the 'quick fix' but it didn't work. Nor does switching to FastCGI. 

     

    Please provide a working solution.

    -1
    Comment actions Permalink
  • Avatar
    John Nitzsche (Edited )

    Can not find version 2.4.29-1ubuntu4 for those packages. I am on Ubuntu 18.04.6

     

    EDIT: My server hoster has its own apt-servers, where the old apache was not available. I had to add the official Ubuntu apt repo. Then I can go with the fix. The following commands are for Germany. Thanks a lot for the fix!

    sudo add-apt-repository "deb http://de.archive.ubuntu.com/ubuntu/ bionic universe multiverse"
    sudo add-apt-repository "deb http://de.archive.ubuntu.com/ubuntu/ bionic-updates universe multiverse"
    3
    Comment actions Permalink
  • Avatar
    Martin Stein Frederiksen

    Thanks a lot for this fix!!

    0
    Comment actions Permalink
  • Avatar
    Jan Eckhoff

    Solution worked, thank you! That was a hard awakening this morning ...

    1
    Comment actions Permalink
  • Avatar
    LyfeRadio

    Anton Maslov how does one Unhold the updates whenever Plesk released a fix for it? cause of course eventually i would want to update Apache i assume.

    is the command for that simply: apt-mark resume apache2 or apt-mark unhold apache2 ?

    5
    Comment actions Permalink
  • Avatar
    Carlos

    Thank you for your fast solution. It was not a good way to start the day :-)

    1
    Comment actions Permalink
  • Avatar
    Firdaus Yusoff

    What a very nice Morning...
    FastCGI help to fix my problem...for now

    1
    Comment actions Permalink
  • Avatar
    Lev Iurev

    @Michael Luchich @Jason Koning  Plesk installs Apache from official OS Ubuntu repository, once new version of Apache or any other OS related package is available on vendor's side it will be fetched during packages update. As such packages versioning is under control of OS vendor, Plesk could only react and rectify the issue on its occurrence.

     

    4
    Comment actions Permalink
  • Avatar
    Paweł Górowicz

    No need for morning coffee. Woke up and 20sites down, provided solution worked.

    Use uptime monitors ppl good luck.

    3
    Comment actions Permalink
  • Avatar
    Lev Iurev

    @LyfeRadio it should be apt-mark unhold apache2

     

    BTW The article will be updated with all the details once the fix is released from Plesk side.

    5
    Comment actions Permalink
  • Avatar
    Grow

    Still trying to figure this s*** out.

    0
    Comment actions Permalink
  • Avatar
    Lobbé Maxime

    ah well, I was going to open a ticket to solve the problem! this solved the problem of sites with errors 500

    0
    Comment actions Permalink
  • Avatar
    Kris

    This article saved my morning. Thank you for the quick workaround, Plesk.

    2
    Comment actions Permalink

Please sign in to leave a comment.

Have more questions? Submit a request