Auth Login shows 419 page expired on POST request

1. Does it work if you comment out the VerifyCsrf middleware in the Kernel.php?
2. If yes, do your sessions work properly? CSRF saves the token in the session so if they don't work it won't find the token to compare. What sessiondriver are you using?

I think this is the same as what i had on an app previously. But what i done was catch the error in the Handler.php file and then redirect back with a message.

public function render($request, Exception $e)
    {

        if ($e instanceof \Illuminate\Session\TokenMismatchException)
        {
            return redirect()
                    ->back()
                    ->withInput($request->except('password'))
                    ->with([
                        'status' => 'Oops! Your Validation Token has expired. Please try again',
                        'alert' => 'danger']);
        }   

        return parent::render($request, $e);
    }

@FTIERSCH - Hey man, yes, it does work when I comment the VerifyCsrf middleware line in the kernel.php file. I'm using the 'file' session driver. Is that possibly a starting point to find the root cause?

@SKOOBI - Sounds like a good workaround. Where do you redirect after catching the exception?

So I tried to get my app running on a Windows Environment with XAMPP and it works just fine without any changes made to the code. Could it be possible this issue is related to the way XAMPP runs on MAC OS? or permissions? I enabled the Write & Read permission to Everyone on htdocs folder but still getting this error.

Long story short... turns out that the REAL issue here is the fact I was using a virtual machine version of XAMPP which was mounting a nfs drive to my local computer... and preventing access to all files in the laravel application. Not 100% sure how the vm works or even how to tie it up with a local computer BUT I just switched to a normal desktop installation of XAMPP on my mac and then gave it some write & read permissions to the htdocs folder and boom!! all of the sudden the error went away!

I used answer from @skoobi with minor changes: -Changed variable $e for $exception, this is the current variable name. -Filter by request path "login" and method "POST" , so it wont affect all calls.