500 error on FilamentPHP panel after installing Laravel Octane
After installing Laravel Octane, I randomly get a 500 Internal Server Error when interacting with the Filament admin panel (e.g. clicking on search, select, etc.).
Is there a specific configuration needed to make FilamentPHP fully compatible with Octane, or could this be a bug?
6 Replies
Check the laravel.log
I assume this happens on production?
It's not on production yet — I'm getting this error in my local development environment. I'm using Laravel Sail with Octane.
Also, nothing is being logged in
laravel.log. On the frontend, I see this error in the browser console:
That tells me there is something wrong with your .env file
Are you sure it exists?
Are the database credentials correct?
While debugging, I temporarily removed
->databaseNotificationsPolling, and the 500 errors stopped appearing randomly on the panel.
However, when I rapidly switch between select inputs inside a resource (e.g. using the Tab key), I still get a 500 error. This didn’t happen before using Octane, so it might be related to rate limiting or Octane-specific behavior.
Is there any known workaround for this?I wouldn’t recommend octane with it. I’m sure other people have success with it, but I don’t think it’s worth the trouble and isn’t meant for that this type of application imho
First: Figure out whether it's a server error or Laravel error (check the look of the exception page in the DevTools). If it's a Laravel error you should find something in the Laravel log.