Class App\Http\Controllers\Auth\Request does not exist. Laravel 5.3

Class App\Http\Controllers\Auth\Request does not exist. Laravel 5.3

  1. Blog
  2. 15 November 2026
  3. 3 min read

Stefan Bogdanescu

Founder & Senior Architect

Class App\Http\Controllers\Auth\Request does not exist. Laravel 5.3

When upgrading or refactoring authentication controllers in Laravel 5.3, you will frequently encounter the Class App\Http\Controllers\Auth\Request does not exist error. This specific exception usually appears after clicking a password reset link, even if the email sending logic works perfectly. The root cause is almost always a misunderstanding of how the ResetPasswordController handles form data and validation in that specific version.

In your ResetPasswordController, you are extending Illuminate\Foundation\Auth\ResetsPasswords. This trait provides several helper methods, including reset(), which is critical for the reset flow. However, the implementation details have changed between Laravel versions, and relying on the full implementation of the reset() method without adjusting the route definition can lead to this exact error.

The issue lies in how you are defining your routes versus how the trait expects them to be named. In Laravel 5.3, the ResetsPasswords trait looks for a specific route signature when handling the reset form request. If you manually define the route using 'ResetPasswordController@reset', the controller attempts to bind the incoming HTTP request to its own internal logic.

When you call $this->credentials($request) inside the reset() method, the trait expects the input to be validated against a specific set of rules defined in the controller's constructor or a dedicated method. If your BaseController does not define these validation rules explicitly for the reset action, Laravel might attempt to infer them incorrectly or try to access a class that doesn't match the expected namespace signature during the binding process.

The error message Class App\Http\Controllers\Auth\Request does not exist suggests that the framework is failing to resolve the $request object correctly within the context of your custom controller setup. This often happens when the route definition does not align with the method signature expected by the trait's internal calls.

To resolve this, you should ensure your routes match the standard Laravel 5.3 authentication scaffolding expectations. Instead of manually mapping every single action in a group if you are using the ResetsPasswords trait, consider removing the custom route definitions for the reset flow and relying on the default routes generated by the trait.

You can do this by clearing your old routes and ensuring your routes/web.php (or app/routes.php depending on your setup) includes the standard Auth::routes() helper call, which Laravel 5.3 provides out of the box:

use Illuminate\Support\Facades\Route;

Route::get('/forgot-password', 'ForgotPasswordController@showLinkRequestForm');
Route::post('/email/verification-notification', 'VerificationController@send');
// ... other standard auth routes

If you must stick with your custom route group, ensure that the method name passed to the route matches exactly what the trait's reset() method expects. The reset() method in the trait is designed to handle the POST request for password resetting. If you are overriding this method but not calling the parent implementation correctly, or if you are naming the route differently than the default scaffold, Laravel might get confused about the request binding.

Specifically, check your ResetPasswordController. You are overriding reset(), which is correct, but ensure that when you call $this->credentials($request), the $request object is valid and fully populated. The error implies a namespace resolution failure, which can happen if the controller isn't being instantiated in the expected context.

Finally, verify that your BaseController does not interfere with the trait's methods. Traits inject methods directly into the class; extending BaseController should be fine, but ensure no conflicts exist in the __construct() method regarding middleware or property initialization that might alter how the request is bound. In Laravel 5.3, strict namespace adherence and matching route names to controller methods are crucial when using built-in traits like ResetsPasswords.

Our network