Level 7
Check the session expiry time in config/session.php. Increase it.
Jul 26, 2016
8
Level 1
Session issue in Laravel 5.1
My app is built with Laravel 5.1. I have saved some data in session using the code, session(['first_name' => Auth::user()->first_name]). The value is set when user is logging in. It's working most of the times but sometimes the session value is being null. I don't know why automatically the session value is getting null. I am tired of solving this kind of weird problem. I need help.
Edited: Also the issue is more serious when user is not logged in with remember token active, the Auth::user() is also getting null for that user. And these situations are happening sometimes, not always. Don't know whether it is server problem or not.
Level 1
Thanks but it's set to 120 minutes and I am facing the problem at ongoing test so session life time is not affecting here. :-)
Level 13
Please make
'domain' => null,
in config/session.php
Level 1
domain is already set to null.
Level 23
@Shafiuzzaman are you using database session. I ran into a bug in 5.1 and 5.2 with database sessions and redirects. Taylor fixed it in 5.2.38.
https://github.com/laravel/framework/issues/9251#issuecomment-226021050
Level 1
@nolros No I am not using database session. Moreover, I think I found an issue, My project structure is something like this,
I have two code base
- Front end (base i,e, public_html)
- App (Provider directory inside public_html)
The Front end is on base directory which is public_html in server and App is inside another directory which name is Provider and that lies in base, which means full Front end is in base and full App is in Provider directory. Login system is from Front end that means I am sending credentials with query string as encrypted and in App after decryption, putting email and password in a variable and then authenticating that user. Now the problem is when I am logging in a blank session file is being created in Front end session directory with the same name which is being created in app which is in Provider directory. So there is now two different file with the same name in two different code base. So I made a custom_directory to store session in Front end and now no duplicate blank session file is being created in custom_directory. From then on I am not getting session problem till now. Lets hope this solve the problem.
Level 1
@Shafiuzzaman I have the same problem, I dont understand how you solve the problem please help me... I have these structure...
Inside de Laravel structure in public I have all of my front end that develop in angular, the laravel session configuration is the same.. but sometimes the session value is being null I don't know when, is random.....
PLEASE HELP
Level 1
@djbryanth are those values in session, you set using session or Auth values. Sometimes auth values get null, and I am finding that issue yet but this can be solved if you keep the remomber token always on that is when auth, besides your credentials you send true as the second parameter in auth. To clarify more please check the auth documentation. If your app structure is like my app then, you can use custom directory to store session of parent app which lies directly in base directory. Hope you got my points :)
Please or to participate in this conversation.