The GET method is not supported for route livewire/update. Supported methods: POST.
I'm working with a fresh install of Laravel and Filament. I followed the installation steps for Filament and set up a user, but when I go to login I get a 502 Bad Gateway error.
Laravel 10
PHP 8.2
Nginx 1.25.3
PostgreSQL 15
Filament 3
OS: Mac
Using valet and dbngin for local testing.
I've tried multiple times with fresh installs thinking maybe I missed a step but I keep ending in the same result. I can see the user in my DB table.
Livewire was installed with Filament.
https://flareapp.io/share/Lm89VNRP
Flare
The GET method is not supported for route livewire/update. Supported methods: POST. - The error occurred at http://filament-panel.test/livewire/update
26 Replies
Update: When using
php artisan serve to start a server and using the localhost IP, it works, but not with Valet or the valet links. Does anyone know why so I don't always have to serve it while testing? Also does anyone know if that's going to become an issue during production?I use valet for all my filament sites and have never had an issue.
Make sure you app_url is set to the appropriate valet .test domain
With Valet, I can view the main index, and view the login page, but when I submit credentials I get the bad gateway.
Never had the issue.
When I serve it I can login fine on the IP (not valet domain)
It’s always working for me with valet just fine. As long as the app_url is correct in your .env file
Assuming that's the issue then maybe
never had the issue with breeze/livewire though weird.
More than likely. If your using valet that would be something like http://directory.test
Artisan serve uses localhost, that’s why it’s working that way
Switched it in the env, even did a build and still can't login over valet
Route cache maybe?
I'm not sure how to clear that
‘php artisan route:clear`
no joy.
Something is definitely wrong in your setup though. I promise it works perfectly fine with valet. But this isn’t a filament issue. It’s a local server issue.
So maybe a valet install issue then?
All of my dev is with valet. So I know it works.
For some reason the example I showed has a trailing slash. If you copied that try removing the trailing slash.
Didn't add the trailing slash to the env
As long as filament-panel is the directory and in your valet root that looks ok to me.
Maybe try a
valet restartJust uninstalled and reinstalled valet, still no luck with it.
It seems to be like a Filament container the 502 error is inside. It's not a full page error if that makes sense.
If I click in the black border area, it takes me back to the login screen
Also even with the APP_URL being that test domain, when I serve it I can still access the IP.
Sorry, not sure. But it’s not a filament issue. It’s a server issue.
Solution
Sounds like there’s an issue with your valet setup though.
Filament will not through a bad gateway because that error occurs before app is even being served or processed.
So it not even hitting the laravel app let alone filament.
Okay thanks, I'll try over on the laravel discord then for help.