hsnww
Issue with Filament Session on Production after Deploying with Laravel Forge on DigitalOcean
Thanks for the suggestion!
I did set up access controls using Filament's built-in permissions, and I’ve also checked the
canAccessPanel setup. Everything seems to be configured correctly, as it works perfectly on the local environment. However, the issue appears only when the app is deployed on the server via Laravel Forge.
Could the canAccessPanel configuration still be a factor even though it works locally? Any specific suggestions on what I should check or adjust regarding canAccessPanel after deployment?
Also, as mentioned earlier, changing APP_ENV to local fixes the session issue, which makes me wonder if there’s something else server-specific that could be causing the problem.
Any additional thoughts or troubleshooting steps would be appreciated!6 replies