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
    TechTheBoy

    Hey guys, if you have client's websites, dont use SSH if you dont have the knowledge to do so because one simple mistake can cause a lot of trouble in the future, intead for now, try my fix comented above as it will do all the work for you with the click of a few buttons which ofcourse you can revert back later.

    https://support.plesk.com/hc/en-us/articles/4407366133906/comments/4407394374034

    Just tryna give y'all a heads up just in case you have client websites, because trust me, it will save you both time and money other than using SSH and messing up everything.

    My best suggestion for you is to wait until the fix is official from the Plesk team and then deploy it because at that time, they will have tested everything for us to make sure its stable.

    Have fun :)

    0
    Comment actions Permalink
  • Avatar
    Peter Hader

    @Harsha K I did. But the command stopped an nothing happened. I switched Sites to FastCGI. This helped for the moment.

    0
    Comment actions Permalink
  • Avatar
    Fitz

    Hey TechTheBoy 

    Thanks so much for your reply...

    Did you mean this menu bar?

    https://www.dropbox.com/s/pev9hb9ay2yd8aj/Capture.PNG?dl=0

    If so there is no DNS section inside it...

    Fitz

    0
    Comment actions Permalink
  • Avatar
    TechTheBoy (Edited )

    @Fitz Could you send me a full screeshot of the page?

    0
    Comment actions Permalink
  • Avatar
    TechTheBoy

    Blur any domains or anything sentisitive

    0
    Comment actions Permalink
  • Avatar
    Alessio Pellegrini

    Thomas Grippaudo 

    "don't type "y" press "enter"

    I tried but i still have "Abort". 

     

    TechTheBoy 

    I tried your solution as well but doesn't work

    0
    Comment actions Permalink
  • Avatar
    TechTheBoy (Edited )

    @Fitz Its right above PHP settings in the place where you clicked PHP settings to change it

    0
    Comment actions Permalink
  • Avatar
    Henrik Sunesen

    20 of our sites where down, we made a "quick-fix" by disabling Proxy mode:

    https://www.screencast.com/t/mCqi8xM6

    It worked on all websites.

    0
    Comment actions Permalink
  • Avatar
    TechTheBoy (Edited )

    @Alessio Pellegrini But for many it did :)

    0
    Comment actions Permalink
  • Avatar
    TechTheBoy (Edited )

    @Alessio Pellegrini Maybe you have changed some other settings beforehand

    0
    Comment actions Permalink
  • Avatar
    Majid Empire

    Thank you it works :)

    0
    Comment actions Permalink
  • Avatar
    John Phipps

    Downgrading on 20.04 worked for me.

    0
    Comment actions Permalink
  • Avatar
    TechTheBoy

    @Anton Maslov How long to get an official fix?

    0
    Comment actions Permalink
  • Avatar
    Jürgen Hörmann

    TechTheBoy

    If you disable proxy mode all requests will be served by NGiNX. That means if your sites use .htaccess for redirects and other stuff, that will no longer work. It would be good to let people know this in advance.

    1
    Comment actions Permalink
  • Avatar
    Fitz

    And here is where i changed the PHP settings...

    https://www.dropbox.com/s/x6n6kpxfvmeb3p0/Screenshot.png?dl=0

    0
    Comment actions Permalink
  • Avatar
    Daniel Marques

    Just switched PHP support in Plesk (PHP version 7.4.23, run PHP as FastCGI application served by Apache) and it works in my wordpress site hosted in digital ocean.

     

    I hope plesk releases a update to handle the situation.

    1
    Comment actions Permalink
  • Avatar
    Fitz

    Daniel Marques

    I just tried you fix suggestion and it worked for me too... thanks a lot for this!

    And also TechTheBoy 

    Thanks so much for trying to help me too!!

    Fitz

    0
    Comment actions Permalink
  • Avatar
    Jo Stubbe

    What a relief!

    thx

    0
    Comment actions Permalink
  • Avatar
    Luca Maffi

    Hi...on my servers in some cases disapeared the possibility to change php from fpm to fastcgi from plesk... happens to anyone ?

    0
    Comment actions Permalink
  • Avatar
    TechTheBoy (Edited )

    @Jürgen Hörmann I've mentioned it earlier, https://support.plesk.com/hc/en-us/articles/4407366133906/comments/4407394722194

    Which is why we cant access the site dashboard if Wordfence 2FA is enabled.

    Thanks for the comment anyways :) It'll help others if they are searching for an answer on why they cant access any redirected requests.

    0
    Comment actions Permalink
  • Avatar
    Johan Adriaans

    20 of our sites where down, we made a "quick-fix" by disabling Proxy mode:

    https://www.screencast.com/t/mCqi8xM6

    It worked on all websites.

    Disabling Proxy mode will make NGINX handle all requests, this will only work if your PHP is also handled by NGINX. It also makes your sites ignore .htaccess files, so be careful with this. .htaccess file wil ONLY be parsed by Apache. You can replace the .htacces file by converting it to nginx directives.

    Any incoming request is first handled by NGINX, you can choose to handle it there and then, or forward it to Apache. PHP can be handled by both NGINX and Apache. NGINX can act as a webserver, but also as a reverse proxy. This is what you configure in your screenshot.

    The problem we face is in the communication between Apache and PHP-FPM.

    These are the moving parts:

    • NGINX - webserver and proxy, all request start here. This process is listening on port 80 (http) and 443 (https).
    • Apache - webserver, can receive request from NGINX, can parse htaccess files
    • PHP-FPM - PHP Service running and communicates with a webserver using a Unix Domain Socket (UDS), this is what Apache can't talk to now.
    • PHP-FastCGI - PHP wrapper that is fired for every request.

    Requests that fail will follow this path:

    NGINX > Apache > PHP-FPM
    ^ Here is the problem

    What you did was cut out apache:

    NGINX > PHP-FPM

    This works, but also kills any .htaccess functionality.

    Picking PHP-FastCGI should also work, but will keep your .htaccess files in-tact

    NGINX > Apache > PHP-FastCGI

     

    The best way for now is just to downgrade Apache and check this page again in a month to see what steps to take next. If you have no SSH client, there is a Plesk Plugin you could use. But BE CAREFUL IN SSH! You can destroy your server with a wrong command.

    0
    Comment actions Permalink
  • Avatar
    TechTheBoy

    @Fitz Anytime bruh :)

    0
    Comment actions Permalink
  • Avatar
    Fitz

    Thanks again TechTheBoy :)

    0
    Comment actions Permalink
  • Avatar
    TechTheBoy

    @Luca Maffi Try clearing browser cache

    0
    Comment actions Permalink
  • Avatar
    Tim Houghton

    Thanks for the quick fix! We had issues with it always Aborting despiting pressing Y/y/Yes, adding

    -y --allow-downgrades 

    solved it.

    export version="2.4.41-4ubuntu3"; apt-get install -y --allow-downgrades apache2=$version apache2-utils=$version apache2-data=$version apache2-bin=$version
    1
    Comment actions Permalink
  • Avatar
    benvee

    This is major as all of our clients' sites went 500 all of a sudden. What's embarrassing is among these a handful sites were still on cpanel vms not affected by this. Thanks for the temporary walkaround till real fix becomes available. 

    0
    Comment actions Permalink
  • Avatar
    Fitz

    TechTheBoy

    Just one last question before i go..

    You know i earlier mentioned that i changed my Apache settings to the FastCGI application served by Apache option.

    Can you foresee doing this causing me any operating issues?

    And do yo think i will i need to change this back after the official Plesk fix?

    Fitz

    1
    Comment actions Permalink
  • Avatar
    Luca Maffi

    @TechTheBoy ...no already tried... only on some domain in php curtain i see only php-fpm from nginx all others values disappear. But on the same server on other domain i see all values.....

    thanks anyway

     

    0
    Comment actions Permalink
  • Avatar
    Jose de Vega (Edited )

    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

     

    1
    Comment actions Permalink

Please sign in to leave a comment.

Have more questions? Submit a request