Bobcares

wesupport

CLIENT AREACall Us 1-800-383-5193
Bobcares

wesupport

Call Us 1-800-383-5193
Bobcares

wesupport

Call Us 1-800-383-5193

Need help?

Our experts have had an average response time of 11.7 minutes in August 2021 to fix urgent issues.

We will keep your servers stable, secure, and fast at all times for one fixed price.

ah10292 invalid proxy uds filename error

by | Oct 1, 2021

Stuck with “ah10292 invalid proxy uds filename error”? We can help you.

As part of our Server Management Services, we assist our customers with several such errors.

Today, let us see the steps followed by our Support techs to resolve it.

 

How to resolve “ah10292 invalid proxy uds filename error”?

Typical error might as shown below:

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)

Apache has been updated recently to a new version.

This issue is actually related to the latest Apache update, which change the approach in handling UDS URIs used to proxy connections from Apache to PHP-FPM.

Today, let us see the steps followed by our Support techs to resolve it:

For Ubuntu 20.04

1. Firstly, connect to the server using SSH.

2. Then, downgrade Apache to previous version:

export version="2.4.41-4ubuntu3";
apt-get install apache2=$version apache2-utils=$version apache2-data=$version apache2-bin=$version;

3. Set to “hold” package for updates:

apt-mark hold apache2

 

For Ubuntu 18.04

1. Firstly, connect to the server using SSH.

2. Then, downgrade Apache to previous version:

export version="2.4.29-1ubuntu4";
apt-get install apache2=$version apache2-utils=$version apache2-data=$version apache2-bin=$version

3. Finally, set to “hold” package for updates:

apt-mark hold apache2

 

You will now need to update Apache packages to fix the issue:

1. Firstly, login to Plesk

2. Then, click Tools and Settings from the Server Management menu.

3. Click System Updates from the Server Management section.

4. If the updates are not already listed, click Recheck Now.

5. Once the updates are detected, click Update All to install the fixes.

The issue should now resolved and your websites should back online.

[Need a hand with the fix? We are available 24*7]

 

Conclusion

In short, we saw how our Support Techs fix this filename error.

PREVENT YOUR SERVER FROM CRASHING!

Never again lose customers to poor server speed! Let us help you.

Our server experts will monitor & maintain your server 24/7 so that it remains lightning fast and secure.

GET STARTED

0 Comments

Submit a Comment

Your email address will not be published. Required fields are marked *

Categories

Tags