Articles in this section

See more

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

Avatar
Leonid Gukhman
Updated
Follow
Plesk Obsidian for Linux

Applicable to:

  • Plesk Obsidian for Linux

Symptoms

  • Websites show the following error:

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

    CONFIG_TEXT: Internal Server Error

  • Apache has been updated to a new version recently:

    Ubuntu 20.04:

    # grep 'status installed' /var/log/dpkg.log | grep apache2:amd64
    2021-09-27 12:46:57 status installed apache2:amd64 2.4.41-4ubuntu3.5

    Ubuntu 18.04:

    # grep 'status installed' /var/log/dpkg.log | grep apache2:amd64
    2021-09-28 06:25:55 status installed apache2:amd64 2.4.29-1ubuntu4.17

Cause

This is an Apache bug which arose with Ubuntu packages update and later fixed in the following versions:

  • Apache for Ubuntu 20 version 2.4.41-4ubuntu3.6.
  • Apache for Ubuntu 18 version 2.4.29-1ubuntu4.18.

Plesk uses Apache packages from OS repositories and does not control their version updates.

Resolution

Update Apache packages to fix the issue:

  1. Log in to Plesk.

  2. Go to Tools & Settings > Server Management > System Updates and click Recheck now.

  3. Once updates are detected, click Update all.

The issue should be fixed, verify that websites are back online.

If Apache updates are not available

  1. Connect to the server using SSH.

  2. Execute below command:

    # sudo apt-mark unhold apache2

  3. Apply steps 2-3 from the resolution.

Comments

318 comments

Sort by Date Votes
  • Avatar
    Peter Claassen

    Received complaint from client about the 500 error. Looked into it last night. Tried updating but it was not availalbe.

    Thought I would be doing the alternative methods today.... but... overnight 2.4.41-4ubuntu3.6 was installed automatically! 

    Problem solved.

    So I guess they've released the update now.

    0
    Comment actions Permalink
  • Avatar
    Mathias

    Updated trough console without issues today after performing the "sudo apt-mark unhold apache2" command. Marking this issue as solved for now. 

    1
    Comment actions Permalink
  • Avatar
    Ivan Arjona

    My plesk says that all is updated but I still have the same problem.

    0
    Comment actions Permalink
  • Avatar
    Luca Brezzi

    Ubuntu 18.04.6 LTS
    Not working

    It says "All packages are up-to-date" but my Apache files are NOT updated, they're still apache2 2.4.29-1ubuntu4.17 and not .18 as it should be. I've tried executing "sudo apt-mark unhold apache2" and it says "apache2 was already not hold", which is true. I still can't see/install the latest patch, how do I get it on Plesk?

    This is what I see when looking for Apache files:

    0
    Comment actions Permalink
  • Avatar
    Steven (Edited )

    This could have been prevented. All my sites were down, and I thought my server was supposed to be solid. My ambulance bill due to heart attack will be forwarded to Plesk.

    -2
    Comment actions Permalink
  • Avatar
    Tjerk Visser

    I see so many different versions in posts.
    My Plesk runs on Ubuntu 18. Currently these files for Apache2 are running and have status up to date.

    Can anybody tell me if these are the correct files? I have the opinion "If it ain't broken, don't fix it"
    Thanks in advance.

    0
    Comment actions Permalink
  • Avatar
    Nathanaël Langlois

    Was terrifying on tuesday with many high load websites down. Thankfully your solution was simple and worked.

    Here the article now says apache has fixed this. Does this mean we should all run sudo apt-mark unhold apache2 so that apache starts updating again?

    0
    Comment actions Permalink
  • Avatar
    Peter Claassen

    With Ubuntu 20 it updates automatically. Perhaps sudo apt-mark unhold apache2 is necessary if you've put it on hold. In normal circumstances it should not be necessary, but it won't hurt. Unless you've put it on hold to avoid the bad update... then you could also wait a few weeks. But don't forget to unhold it for security reasons.

    Tjerk tells us Ubuntu 18 is not updating to the latest patch yet. Perhaps someone can confirm that?

    Then this problem is fixed partially.

    0
    Comment actions Permalink
  • Avatar
    Luca Brezzi

    Ubuntu 18.04.6 LTS is still updated to the old version .17 instead of .18. Is there any chance that Plesk fixes this issue?

    0
    Comment actions Permalink
  • Avatar
    Markus Weingärtner

    Luca Brezzi you should check your apt sources. These should point to the Ubuntu repositories. Some providers use their own repositories in the templates, which are not always up-to-date. This is not a Plesk problem

    0
    Comment actions Permalink
  • Avatar
    Luca Brezzi

    >  This is not a Plesk problem

    Well it may not be but I am stuck and I don't want to make things even worse. I hope they will update the sources soon.

    0
    Comment actions Permalink
  • Avatar
    Minh Buii (Edited )

    My new Digitalocean droplet, and Plesk just shows Fast CGI option.

    Ubuntu 20.04.3 LTS
    PHP 7.3.30 or 7.4.23 both didnt work

    Then the site works again, but it's on and off, down 1-2 hours almost every day and not as stable as usual.
    How to check what's the error and how to fix it? Thanks

    0
    Comment actions Permalink
  • Avatar
    Stephen Hodgkiss

    Nathanaël Langlois - if you put the apache2 updates on hold, then yes, you can unhold them and either issue the updates and upgrades manually or wait until the next auto upgrade happens. For myself, I did the manual option so I could immediately see the results.

    apt-mark unhold apache2
    apt-get update
    apt-get upgrade
    1
    Comment actions Permalink
  • Avatar
    Stephen Hodgkiss (Edited )

    Minh Buii - I suggest reading through the comments of others. I do recall others also had issues with DigitalOcean but they found solutions. As there is already a permanent fix for it with a further apache2 release, then there should (in theory at least) be no need to go for the temporary fix of adjusting the proxy settings.

    example DO comment https://support.plesk.com/hc/en-us/articles/4407366133906/comments/4407395692050 

    example Proxy settings comment https://support.plesk.com/hc/en-us/articles/4407366133906/comments/4407400206226 

    For the actual error itself, for me it showed in the standard error log and gave the error: AH10292, which then led me to this Plesk thread.

    0
    Comment actions Permalink
  • Avatar
    Stefan Lachmann (Edited )

    Hi,

    Same issue again this morning (19 Oct 2021)!!! Workaround by Kovac worked again:

    1. change to "FPM Application served by nginx" instead of Apache, in "PHP settings" for the domain.

    2. in "Apache & nginx Settings" switched off "Proxy mode".

    HOWEVER: It cannot be the case that the server shuts down again! Plesk needs to get updates properly and safely done! Makes sure to check the issue!

    0
    Comment actions Permalink
  • Avatar
    Pablo González-Trejo

    Hi There,

    Regarding this issue, I followed Nipuna Maduranga instructions on September 28th. 

    For reference:

    1) 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

    I went to see my packets and they are all up to date today and I imagine also Plesk latest updates.

    I tried reverting to previous setting via Plesk panels and site goes down right away if I set the proxy mode again.

    Leonid Gukhman   Please advise what to do to have a permanent solution?

    thanks

    Pablo

    0
    Comment actions Permalink
  • Avatar
    Pablo González-Trejo (Edited )

    Leonid Gukhman & Nipuna Maduranga

    Hi, I checked I am already up to date with apache2 2.4.41-4ubuntu3.8 (Ubuntu for focal-updates by Ubuntu)

    So I don't understand why I still get this Internal Server Error when I try to revert to default config.

    Any recommendations?

    thanks

    Pablo

    0
    Comment actions Permalink
  • Avatar
    Ben Hu

    Appearently for those who applied temp fix and disabled apache2 upgrade, you will have to undo this before applying future upgrade.  

    sudo apt-mark unhold apache2
    0
    Comment actions Permalink

Please sign in to leave a comment.

Have more questions? Submit a request

Related articles