404 Laravel admin/login on production and 404 Apache after login locally
Hello everyone,
I am using Filament V3 and everything is working fine when I use php artisan serve.
Description of the problem:
On local when using Wamp (apache), I have a 404 AFTER hitting login (console gives livewire.js?id=df3a17f2:4294 POST http://localhost/livewire/update 404 (Not Found) ) . No issue at all if using php artisan serve
On prod (heroku), I have a 404 laravel when I tried to access admin/login (console gives login:1 Failed to load resource: the server responded with a status of 404 ())
I think the two behavior may somewhat be linked and caused by Apache or Livewire but I have to admit I don't have enough knowledge to find the real cause of issue.
What I tried :
On local, the solution suggested here https://github.com/filamentphp/filament/discussions/14163 actually fixed my issue. However when I try to do something similar on prod, I have a Target class [livewire] does not exist.
On prod, what I tried so far (you can find my code here :https://stackoverflow.com/questions/79751719/404-on-admin-login-page-for-laravel-filament ) :
- configure htaccess
- add a procfile
- canAccessPanels is implemented in my User Model
- the route admin/login is present in the routes list
- clearing cache
- filament upgrade, and the other recommendations of the help page
many thanks for you help
I am using Filament V3 and everything is working fine when I use php artisan serve.
Description of the problem:
On local when using Wamp (apache), I have a 404 AFTER hitting login (console gives livewire.js?id=df3a17f2:4294 POST http://localhost/livewire/update 404 (Not Found) ) . No issue at all if using php artisan serve
On prod (heroku), I have a 404 laravel when I tried to access admin/login (console gives login:1 Failed to load resource: the server responded with a status of 404 ())
I think the two behavior may somewhat be linked and caused by Apache or Livewire but I have to admit I don't have enough knowledge to find the real cause of issue.
What I tried :
On local, the solution suggested here https://github.com/filamentphp/filament/discussions/14163 actually fixed my issue. However when I try to do something similar on prod, I have a Target class [livewire] does not exist.
On prod, what I tried so far (you can find my code here :https://stackoverflow.com/questions/79751719/404-on-admin-login-page-for-laravel-filament ) :
- configure htaccess
- add a procfile
- canAccessPanels is implemented in my User Model
- the route admin/login is present in the routes list
- clearing cache
- filament upgrade, and the other recommendations of the help page
many thanks for you help
GitHub
Package Panel builder Package Version 3.2 How can we help you? Hello Filament team, I'm experiencing an issue with the installation of Filament on my Laravel project. Despite following the inst...
Stack Overflow
I am using Filament 3. I can access the admin login page on my local project but not the production server (Heroku).
What I tried so far :
configure htaccess
add a procfile
canAccessPanels is
What I tried so far :
configure htaccess
add a procfile
canAccessPanels is
