The POST method is not supported for route login. Supported methods: GET, HEAD.

Hi guys! I am deploying a Laravel FilamanetPHP app in my VPS and after I login in show me this error. What should I do? Please any solution?
Solution:
The problem with me was with the VPS itself it wasn't configure right after I reinstalled from the beginning now is working ok. Please check if your VPS is installed correctly.
Jump to solution
15 Replies
vijay_khanal
vijay_khanal10mo ago
Same error after deploy. Did you solve this?
abdullafahem
abdullafahemOP10mo ago
No! I don't know why because the route on Filament are not in routes file are in vendor and I don't know why
developer
developer10mo ago
whats your filament version?
abdullafahem
abdullafahemOP10mo ago
"filament/filament": "^3.2",
vijay_khanal
vijay_khanal10mo ago
Any update regarding this issue? Did you solve this?
jaykeeb
jaykeeb10mo ago
same error using v3.2.28, only happen after deploy, not in local
Tieme
Tieme10mo ago
Did you clear all route cache?
stanwarri
stanwarri10mo ago
I'm currently experiencing this problem after I updated to the latest version of Filament today. Have tried route:cache & route:clear, still no positive outcome. Has anyone been able to find a solution to this? BTW, this only happens in production @Abdulla Fahem Did you find a solution?
Solution
abdullafahem
abdullafahem10mo ago
The problem with me was with the VPS itself it wasn't configure right after I reinstalled from the beginning now is working ok. Please check if your VPS is installed correctly.
stanwarri
stanwarri10mo ago
I'm actually using DO via Laravel Forge for deployment. I believe Forge handles all that, and this isn't actually my first deployment
abdullafahem
abdullafahemOP10mo ago
I use hostinger VPS KVM2 Ubuntu 22.04 LTS and it was the first time in hostinger to deploy an app. As usual via Laravel Forge should work I don't know.
bruce_lee2765
bruce_lee276510mo ago
Same error after deploy. Did you solve this? Who has a solution to this problem?
feedoms
feedoms9mo ago
any solution ?
stanwarri
stanwarri9mo ago
It was my Nginx configuration that was causing the issue. You may start by looking into that first
rich06
rich069mo ago
Is there a fix for this? I upgraded to Filament v3.2.44 and now I cannot log in anymore to the admin panel... Edit: I fixed this for my installation by re-publishing the Livewire assets . I also added the following to composer.json in the scripts/post-autoload-dump section:- @php artisan vendor:publish --force --tag=livewire:assets --ansi`
Want results from more Discord servers?
Add your server