The page has expired due to inactivity.

I assume you are using the default file session driver? Are session files being created in /storage/framework/sessions?

When you say the forms aren't working, do you just mean when you submit, or are there other issues? Are they visually ok?

Hi @successdav Please check this link.

https://laracasts.com/discuss/channels/laravel/the-page-has-expired-due-to-inactivity-please-refresh-and-try-again

Hope it helps!.

@mahaveer @cronix I have followed the link and have tried all of the solutions none is working.

@cronix the program generate session files stored on storage/framework/sessions and the form displays correction, they is nothing wrong with the view, the error shows up only when I try to submit. and it was not like this when I pushed to github, everything was fine until I git clone from git home, run composer install, composer update and & npm install.

HERE IS MY .env file

APP_NAME=Laravel
APP_ENV=local
APP_KEY=base64:ml13JDTO5637p0jDOS0hTCETUE5fPZkx8R6eS7KT/ZQ=
APP_DEBUG=true
APP_URL=http://localhost

LOG_CHANNEL=stack

DB_CONNECTION=mysql
DB_HOST=127.0.0.1
DB_PORT=3306
DB_DATABASE=success
DB_USERNAME=homestead
DB_PASSWORD=secret

BROADCAST_DRIVER=log
CACHE_DRIVER=file
QUEUE_CONNECTION=sync
SESSION_DRIVER=file
SESSION_LIFETIME=120

REDIS_HOST=127.0.0.1
REDIS_PASSWORD=null
REDIS_PORT=6379

MAIL_DRIVER=smtp
MAIL_HOST=smtp.mailtrap.io
MAIL_PORT=2525
MAIL_USERNAME=9cc551d5e49890
MAIL_PASSWORD=3682dd5ccbc0cf
MAIL_ENCRYPTION=null

AWS_ACCESS_KEY_ID=
AWS_SECRET_ACCESS_KEY=
AWS_DEFAULT_REGION=us-east-zz1
AWS_BUCKET=

PUSHER_APP_ID=
PUSHER_APP_KEY=
PUSHER_APP_SECRET=
PUSHER_APP_CLUSTER=mt1

MIX_PUSHER_APP_KEY="${PUSHER_APP_KEY}"
MIX_PUSHER_APP_CLUSTER="${PUSHER_APP_CLUSTER}"

AND on the config Session.php I have

*/

    'domain' => env('SESSION_DOMAIN', null),

    /*

Try with below commands,

    composer update --no-scripts      

and have you set config\app.php as like below,

   'debug' => env('APP_DEBUG', true),

and check your config\session.php too

@munazzil I have updated the files but still same error. but on chrome network console here is the request headers. it returns 419.

Request URL: http://stechmax.test/login Request Method: POST Status Code: 419 unknown status Remote Address: 192.168.10.10:80 Referrer Policy: no-referrer-when-downgrade

APP_URL=http://localhost

try changing that to the name of your actual host. It looks like it should be http://stechmax.test?

thank you

Thank you? please which solution actually worked for you?

Is your session signed with your old key? Can you invalidate your session (are you always remembered?)

Have you include this in your home.blade.php?

   <script src="https://cdn.jsdelivr.net/npm/[email protected]/dist/vue.js"></script>

and run below commands as well,

   npm run dev
   npm run watch

clear your browser cookies or try incognito mode?

I think I will remove the entire node_modules folder and rerun npm install if no customization on any module...

Hello Everyone, Thanks all for your time. The problem was from the upgrade, when I run composer update, it updated my laravel from 5.6 to 5.6.30. After googling the 419 status code, it landed me on this page https://laravel.com/docs/5.6/upgrade and all I needed to do was to add this line of code to

protected static $serialize = true;

And this error has been fixed. now am unto the next error, the composer update just messed up my project leaving me with series of bugs. Once again thanks.