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

317 comments

  • Avatar
    Krisztian Kovacs

    Hi tiziano and Grow

    please check my comment above. Those 2 steps worked for me directly from Plesk.

    br K.

    1
    Comment actions Permalink
  • Avatar
    Kim Jagstedt

    Just panicked this morning. But thanks to this solution I can breath again. Thanks!

    0
    Comment actions Permalink
  • Avatar
    Mohamed Thahir

    We are running Plesk on Lightsail. 

    Don't have access to root and not able to run this command in the SSH Terminal.

    Kindly suggest.

    0
    Comment actions Permalink
  • Avatar
    Domenico

    thanks, i hope for a solution that unlocks the updates

    0
    Comment actions Permalink
  • Avatar
    tiziano (Edited )

    @Krisztian Kovacs

    i made the changes and the homepage works but prestashop seems to unusable and give error 500 in every page. 

    0
    Comment actions Permalink
  • 1
    Comment actions Permalink
  • Avatar
    Domenico

    Mohamed Thahir tiziano run php as FastCGI

    3
    Comment actions Permalink
  • Avatar
    eocookie (Edited )

    I've just switched PHP support in Plesk (PHP version 7.4.23, run PHP as       FastCGI application served by Apache) and it works.

    1
    Comment actions Permalink
  • Avatar
    tiziano

    @Domenico

    where i have to make the changes? in prestashop? thanks

    0
    Comment actions Permalink
  • Avatar
    Krisztian Kovacs

    Hi tiziano

    yes, try FastCGI, as Domenico wrote, maybe that works better for you.

    br.

    0
    Comment actions Permalink
  • Avatar
    Coopsy

    I was woken up by several customers to advise of 500 error. As usual, I panicked and on hold to my server host to see what the issue was. I seached through the Wordpress error logs and googled the error boom this worked for me straight away. Ive got to thank the uploader but also this is a great community to be involved in and can see everyone wants to help each other which is amazing to see :)

    0
    Comment actions Permalink
  • Avatar
    Landin Informatica

    Thanks for the quick solution!

    0
    Comment actions Permalink
  • Avatar
    tiziano

    @eocookie

    i switched to fastcgi and seems to works... what is the difference between fpm and fastcgi? thanks 

    0
    Comment actions Permalink
  • Avatar
    Jérôme Dubois (Edited )

    Fix worked for me on Ubuntu 20.

    Thanks a lot but a bit disappointed...

    Please keep us informed when it will be resolved in order to unhold apache updates.

    1
    Comment actions Permalink
  • Avatar
    Johan Adriaans

    That nearly gave me a heart attack, thanks for the quick fix! Now that we rolled back our Apache and blocked future updates, will there a follow up? I am not sure everyone here understands the concequences of this fix.

    Anyone reading this, make sure to mark your calendar 1 month(?) from now. At some point you should "unhold" apache2 so it will receive updates again. I expect Plesk will update this article with a link to a follow up or at least some extra info.

    1
    Comment actions Permalink
  • Avatar
    Tsviel Zaikman (Edited )

    The command does not work for Amazon Lightsail. It seems the system do not know this command

    E: Could not open lock file /var/lib/dpkg/lock-frontend - open (13: Permission denied)
    E: Unable to acquire the dpkg frontend lock (/var/lib/dpkg/lock-frontend), are you root?

     

    Please help

    0
    Comment actions Permalink
  • Avatar
    arturrro

    Nice advise, works fine for me, thanks

    0
    Comment actions Permalink
  • Avatar
    Rob Skinn

    Thanks for the quick fix, it worked a treat. Not a great start to the morning, but relieved that it's been resolved.

    0
    Comment actions Permalink
  • Avatar
    Luis Manrique

    After apply this solution, the changes will keep in server?

    should we do anything else or this is the definitely solution¿? Thanks!

    2
    Comment actions Permalink
  • Avatar
    vanessa eley

    I have too many sites to implement the workaround to! Hoping  you can fix this issue asap! And likewise - can this be tested before being pushed out?!

    Best.

    0
    Comment actions Permalink
  • Avatar
    Lev Iurev

    @Tsviel Zaikman and all with AWS lightSail

    Just checked solution there. It works.

    If you face the error below:

    E: Could not open lock file /var/lib/dpkg/lock-frontend - open (13: Permission denied)
    E: Unable to acquire the dpkg frontend lock (/var/lib/dpkg/lock-frontend), are you root?

    Run 

    sudo su -  

    then apply solution.

    0
    Comment actions Permalink
  • Avatar
    Raffaele Troccoli

    we also have the same problem what to do?

    E: Paket apache202.4.29-1ubuntu4 kann nicht gefunden werden.
    E: Mittels des Musters »apache202.4.29-1ubuntu4« konnte kein Paket gefunden werd en.
    E: Mittels regulärem Ausdruck »apache202.4.29-1ubuntu4« konnte kein Paket gefund

    0
    Comment actions Permalink
  • Avatar
    saddam

    AH10292: Invalid proxy UDS filename (proxy:unix:///var/www/vhosts/system/itwarbazar.pk/php-fpm.sock|fcgi://127.0.0.1:9000/var/www/vhosts/itwarbazar.pk/httpdocs/index.php)

    This error is showing in log file. Kindly help me how to solve it

    0
    Comment actions Permalink
  • Avatar
    Bill (Edited )

    Bonjour,

    Pour ma part, j'ai passé en Fast CGI et cela à contourner le problème en attentant le correctif de Plesk.

    Bonne journée à tous

    0
    Comment actions Permalink
  • Avatar
    Jakob Busk

    For anyone who says it does not work. Try restarting your Web Server (Apache) in "Tools & Settings" -> Server Management and select Services Management. In here you should be able to restart it.

    1
    Comment actions Permalink
  • Avatar
    Tjerk Visser

    I used the solution for Ubuntu 18 and it worked. Thanks. Please advice here with a folow up.

    Regards Tjerk

    0
    Comment actions Permalink
  • Avatar
    Stephen Hodgkiss

    I can also confirm that implementing the resolution above for Ubuntu 20, the site came back online

    0
    Comment actions Permalink
  • Avatar
    Dan Powell

    The suggested fix for Ubuntu 18.04 didnt work. Changing from FPM to FactCGi worked for me.

    1
    Comment actions Permalink
  • Avatar
    Grow

    Krisztian Kovacs  thanks brother, luckily I had someone to help me out with this. I dont exactly know what they did but it works now. I wish your GUI based workaround was also mentioned at the top for people like me.

    As for guys like me who are on AWS Lightsail, as mentioned by @Lev Iurev the following command on your web based SSH client enables you to become a root (admin) user. After that I have no idea and I'm worried to key in anything.

    sudo su - 

    Anyway I'm glad I had someone to help me out. Managing server is not my thing. Woke up in a freaking shock and the whole day was spent on trying to fix this issue. Now got to work on my usual stuff.

    0
    Comment actions Permalink
  • Avatar
    TechTheBoy (Edited )

    Alright guys, here's the walkaround 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 :)

    6
    Comment actions Permalink

Please sign in to leave a comment.

Have more questions? Submit a request