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

Follow

Comments

318 comments

  • Avatar
    Mathias

    Great day for the Plesk tech and sales department not to communicate! Just received notice of the 10% price increase that comes into effect from January, on the very same day that all of your clients web pages goes down, at the same time :)

    2
    Comment actions Permalink
  • Avatar
    Ajcornejo (Edited )

    I ran the workaround above. I don't believe the extra step 4 was up when I ran this so I did not # runapt-mark unhold apache2

    It did get my site up and running again but I now see the following error at the top of the Website & Domains screen. 

    New configuration files for the Apache web server were not created due to the errors in configuration templates: Template processing failed: file = /opt/psa/admin/conf/templates/default/domainVhost.php, error = Template_Exception: Class 'Template_Variable_Domain_PhysicalHosting' not found file: /opt/psa/admin/plib/Template/Processor.php line: 28 code: 0 Previous error: Error: Class 'Template_Variable_Domain_PhysicalHosting' not found file: /opt/psa/admin/plib/Template/Variable/Factory.php line: 20 code: 0. Detailed error descriptions were sent to you by email. Please resolve the issues and click here to generate broken configuration files once again or here to generate all configuration files. See the details in Configuration Troubleshooter

    I want to tread carefully before attempting to resolve this. How should I proceed? 

    **********Update*************

    @Johan Adriaans

    Suggested contacting support. When putting in the error message into the subject line it pulled up an article that addresses this. 

    Error in Plesk: New configuration files for the Apache web server were not created due to the errors in configuration templates – Plesk Help Center

    I'll hold off taking any action since the sites are running now and wait for the permanent fix before cleaning up artifacts. 

    0
    Comment actions Permalink
  • Avatar
    Justin MacLeod

    @Andreas Giesen  - Thanks for posting that additional workaround. I had to apply it to one of my older sites where I had some special settings in place. Switching from /// to / worked perfectly!

    0
    Comment actions Permalink
  • Avatar
    Wilfried

    Please Can someone tell me how to fix the 500 error ? I don't understand what this article is indicating

    -1
    Comment actions Permalink
  • Avatar
    Johan Adriaans

    @Ajcornejo

    I'd contact Plesk Support. This is not something that should happen when you apply this fix.

    1
    Comment actions Permalink
  • Avatar
    eamon

    it is not clear how to update , 

    0
    Comment actions Permalink
  • Avatar
    eamon

    poor quality services 

    0
    Comment actions Permalink
  • Avatar
    Lairinys Gabriela Silva

    Thanks you so much, please keep me updated if you get a permanet solution

    0
    Comment actions Permalink
  • Avatar
    Obaro Alidou K.

    It worked for me.

    However, when will the definitive fix come?

    Thanks for addressing the issue so quickly.

     

    0
    Comment actions Permalink
  • Avatar
    Jagadeesh Sandireddy

    it worked for digital ocean server but not working for Lightsail any fix for Lightsail

    0
    Comment actions Permalink
  • Avatar
    Mark-Oliver Wolter

    ubuntu just pushed the updates 5 minutes ago, so if you're still affected, scan for updates (Tools & Settings -> System updates -> Recheck Now) and install.

    5
    Comment actions Permalink
  • Avatar
    Angry Plesk User

    I have followed all the steps and now I can see the websites but all pages show me a 404 error

     
    1
    Comment actions Permalink
  • Avatar
    Benjamin

    So the fixed packages for Ubuntu have landed on the primary (US?) mirror 20 Minutes ago. It will take a while to be mirrored to regional mirrors.

    People who marked the apache2 package for hold have to unhold the package:

    sudo apt-mark unhold apache2

    Then update the packages

    sudo apt update && sudo apt upgrade

    Everyone who implemented the second workaround (updating PhysicalHosting.php) can just wait for the updated packages to be automatically installed by Plesk.

    Everyone who hasn't done anything yet:

    sudo apt update && sudo apt upgrade

    Or I think just "Check for Upgrades" and install upgrades via Plesk Webinterface (never used it tbh).

     

    Again, it will take a few hours for all mirrors to mirror the new packages, so in any case you do the following:

    sudo echo "deb http://archive.ubuntu.com/ubuntu focal-security main restricted universe multiverse" >> /etc/apt/sources.list
    sudo apt update && sudo apt upgrade

    This adds Ubuntus primary mirror to apt and you should get the new apache packages.

     

    Upgrading apache WILL be the permanent fix.

    6
    Comment actions Permalink
  • Avatar
    Victor Caudillo

    OMG, thanks for the fast solution!!!!!!!!!

    0
    Comment actions Permalink
  • Avatar
    Michael Pratt

    I just confirmed that the update package (Tools & Settings > System Updates > Recheck Now) and updating to the newest version fixed the problem for me allowing me to update AND unhold apache2 upgrade. So if you are uncomfortable in SSH or just do not want to do that manually, then you can run it through the update screen within Plesk now.

    Thanks @Mark-Oliver Wolter for the update, as this is what I was personally waiting for, an official update to it.

    2
    Comment actions Permalink
  • Avatar
    Luca Ibba

    Per me funziona.
    Grazie!

    0
    Comment actions Permalink
  • Avatar
    Daniel Marques

    Worked the new updates by web interface and put back PHP - FPM aplication served by apache and the site on Digital Ocean is ON.Thanks i hope it solved everthing.

    Thanks for the fast solution.

    1
    Comment actions Permalink
  • Avatar
    Filipe

    Thanks! Server just updated and broke everything. Cheers.

    3
    Comment actions Permalink
  • Avatar
    Simeon Petrov (Edited )

    When your customers are loosing money because of a bugs like these (e-commerces down for hours), unfortunately a simple "We are sorry" is not enough. This should never happen in an Web Server Administration Platform... Updates on so crucial components on the server should be tested before being applied on the server... Who's gonna pay our customers that losed money and who's gonna pay our customer unsatisfaction and untrust...

    9
    Comment actions Permalink
  • Avatar
    Tempesta

    Thanks for the quick fix! 

    0
    Comment actions Permalink
  • Avatar
    Nicola Boccardi

    why in this post is not officially recommended the simpler solution to switch PHP-fpm to FastCGI? It's the simplest and faster way to temporary solve the issue, without making changes on the server by ssh, and you can do it simply unflagged a checkbox in apache-nginx Plesk's configuration panel...

    2
    Comment actions Permalink
  • Avatar
    Checha

    La solución temporal para todos los servidores que tengo con 20.04 es cambiar de FPM nginx a FastCGI Apache, a la espera de la actualización que regulariza este problema.

    0
    Comment actions Permalink
  • Avatar
    Gentry Smith

    Thank you!  Perfect solution.  Well done!

    0
    Comment actions Permalink
  • Avatar
    Ajcornejo

    I see numerous methods in the comments on how to fix this with the Ubuntu update available. Will Plesk eventually post a detail on how to handle this once the Ubuntu update has been tested? 

    I ran the workaround earlier this morning and it got my site running albeit with some error messages on my Website & Domain screen. It seems like the workaround was changed from when I first ran it this morning with an additional 4th step added about unholding the apache package. 

    1
    Comment actions Permalink
  • Avatar
    Daniel Zimmermann

    workaround worked/works but the new update doesn't work for me- so I reverted and use the workaround still 

    0
    Comment actions Permalink
  • Avatar
    Daniel Baus (Edited )

    Is the fixed Apache version only for ubuntu 20.04? I'm running 18.04 and can't get the update via Tools & Settings etc.

    0
    Comment actions Permalink
  • Avatar
    Michael

    are there any future problem if i leave the main mirror inside? could not get the updated apache yet, but with the main mirror it worked., Can i let it there?

    sudo echo "deb http://archive.ubuntu.com/ubuntu focal-security main restricted universe multiverse" >> /etc/apt/sources.list 
    0
    Comment actions Permalink
  • Avatar
    Steinar Rasch

    This comment/fix from Benjamin: https://support.plesk.com/hc/en-us/articles/4407366133906/comments/4407405402386 worked for me on both Ubuntu 18.04.6 and Ubuntu 20.04.3 on DigitalOcean.

    I had first done the fix with a rollback of Apache2 update and then hold updates, for me it was enough to do the following:

    -----------------------------------------------------------------------------------

    People who marked the apache2 package for hold have to unhold the package:

    sudo apt-mark unhold apache2

    Then update the packages

    sudo apt update && sudo apt upgrade

    -----------------------------------------------------------------------------------

     

    0
    Comment actions Permalink
  • Avatar
    eamon

    please advise 

    my plesk licence is not active i have no access to root , 

    how to sort out this problem ?????

    0
    Comment actions Permalink
  • Avatar
    Manuel Wiesert

    apt-mark unhold apache2 geht nicht Super klasse 

     

    Und nun ????????????? 

    0
    Comment actions Permalink

Please sign in to leave a comment.

Have more questions? Submit a request