0

I have no problems of this sort during development but after pushing to production, keep getting the error message "The page has expired due to inactivity".

I tried clearing cache and all that...

composer dump-autoload && php artisan optimize && php artisan cache:clear && php artisan config:clear && php artisan route:clear && php artisan view:clear

But it doesn't seem to help

The quick fix right now is turn off one of the application servers, but both of them running causes the page expired error. And as previously noted, this only happens in production after every push

anabeto93
  • 265
  • 3
  • 9
  • `APP_DEBUG=true` set this in your .env and check – Sapnesh Naik Dec 04 '17 at 12:49
  • 3
    Possible duplicate of ["The page has expired due to inactivity" - Laravel 5.5](https://stackoverflow.com/questions/46141705/the-page-has-expired-due-to-inactivity-laravel-5-5) – Chay22 Dec 04 '17 at 13:00
  • I just did and it is still showing the same error. But I would like to add that this usually happens after I do a git push to production. – anabeto93 Dec 04 '17 at 13:34

1 Answers1

0

Do you have the application key set in the .env file?

Try running php artisan key:generate

Also: Do you have some sort of error log from the server itself? Maybe you get more info from that.

Nieck
  • 1,576
  • 3
  • 17
  • 41