Maaz Zindani

Loading the index…

↑↓ move↵ openesc close4072 pages
Node.js, PHP and APIs

Class 'Fideloper\Proxy\TrustProxies' not found after a Laravel upgrade

ErrorClass 'Fideloper\Proxy\TrustProxies' not found

Short answer

Your app still points at the old Fideloper package, which Laravel no longer needs. Laravel ships its own Illuminate\Http\Middleware\TrustProxies. Change your middleware to extend that class, or in Laravel 11 and newer delete the file and set trusted proxies in bootstrap/app.php. Do not reinstall the old package.

  • Applies to Laravel 11, Laravel 12, PHP 8.3
  • Updated
  • By Maaz Zindani, Senior Software Engineer

Fix it fast

  1. 1Find out which cause you have

    Find every place the old class is still mentioned.

    grep -rn "Fideloper" app bootstrap config composer.json
  2. 2Match what you see, then jump to its fix

    1. 1The stack trace points at app/Http/Middleware/TrustProxies.phpapp/Http/Middleware/TrustProxies.php still extends the Fideloper classFix
    2. 2There is no App\Http\Kernel, or a leftover reference to the old middleware class in bootstrap/app.phpThe app uses the Laravel 11+ structure, where trusted proxies are set in bootstrap/app.phpFix

What does the error look like?

  • Class 'Fideloper\Proxy\TrustProxies' not found

Cause 1 of 2

app/Http/Middleware/TrustProxies.php still extends the Fideloper class

1Check

Open the file and read the line that starts with use Fideloper.

sed -n '1,15p' app/Http/Middleware/TrustProxies.php

2Fix

The Fideloper README says Laravel 5.5 and newer include this package and that you should not use it on Laravel 9. Extend the framework class instead.

use Illuminate\Http\Middleware\TrustProxies as Middleware;

3Verify

Clear caches and load any page.

php artisan optimize:clear

Confirmed by github.com

Did this fix it?

Cause 2 of 2

The app uses the Laravel 11+ structure, where trusted proxies are set in bootstrap/app.php

1Check

Search the bootstrap file for TrustProxies.

grep -n "TrustProxies\|trustProxies" bootstrap/app.php

2Fix

Remove the leftover reference and configure the proxies with the trustProxies method. Use at: '*' only when you cannot list your load balancer addresses.

->withMiddleware(function (Middleware $middleware): void {
    $middleware->trustProxies(at: '*');
})

3Verify

Request a page through the load balancer and check that generated links use https.

php artisan tinker   # then run: url('/')

Confirmed by laravel.com

Did this fix it?

How do I stop it coming back?

  • After a major Laravel upgrade, run the grep above and remove old package names from code and composer.json.
  • Do not run composer require fideloper/proxy to silence the error.
  • Keep proxy settings in one place, bootstrap/app.php on Laravel 11 and newer.

Sources

How was this page made?

I drafted this page with AI assistance from the official documents listed under Sources. Every cause above names the document that confirms it. I have not reproduced this fix on a machine of my own yet, so read it as documented guidance, not a test report. Found a mistake? Tell me.

Which stack is behind this page?

Projects of mine built on the same technologies:

Related fixes

Back end

composer require maatwebsite/excel fails to install

Composer says the package needs an older PHP than the one installed

Composer refuses maatwebsite/excel when the PHP version or a PHP extension does not match what the package and PhpSpreadsheet need.

3 causes, each with a fix

Back end

composer require laravel/horizon fails: ext-pcntl is missing

laravel/horizon v1.1.0 requires ext-pcntl * -> the requested PHP extension pcntl is missing from your system

Horizon needs the pcntl extension, and Composer refuses to install it where PHP lacks that extension.

3 causes, each with a fix

Next step

Want this handled for good?

I look after servers, apps and releases end to end. Tell me what keeps breaking.