Getting "The POST method is not supported for route admin/login. Supported methods: GET, HEAD." after deploying my Filament app

[SouhailBouaouiss]

Package

Panel builder

Package Version

v3.0.0

How can we help you?

I've recently deployed my Filament application to a server, but I'm encountering an error message stating 'The POST method is not supported for route admin/login. Supported methods: GET, HEAD.' This issue seems to occur only on the server, as the application functions correctly in my local development environment. I've verified that the 'admin/login' route exists and is configured correctly in my routes file, and I've confirmed that the form method is set to 'POST'. Despite these checks, the error persists. I'm seeking assistance from the community to troubleshoot and resolve this issue. Any insights or suggestions would be greatly appreciated. Thank you in advance for your help!

[leandrocfe]

Can you see the login page?

[AminAhadian]

I have same problem. I can see login page but show password button doesn't work and when I try to login i get this error.
The POST method is not supported for route admin/login. Supported methods: GET, HEAD.

[Fadelaliyafasya]

same problem with me

[aimonext]

.

[techwizzy]

this a .htaccess issue , try this in your root folder :


Options -MultiViews -Indexes

RewriteEngine On

# Handle Authorization Header
RewriteCond %{HTTP:Authorization} .
RewriteRule .* - [E=HTTP_AUTHORIZATION:%{HTTP:Authorization}]

# Redirect Trailing Slashes If Not A Folder...
RewriteCond %{REQUEST_FILENAME} !-d
RewriteCond %{REQUEST_URI} (.+)/$
RewriteRule ^ %1 [L,R=301]

# Remove public URL from the path
RewriteCond %{REQUEST_URI} !^/public/
RewriteRule ^(.*)$ /public/$1 [L,QSA]

# Send Requests To Front Controller...
RewriteCond %{REQUEST_FILENAME} !-d
RewriteCond %{REQUEST_FILENAME} !-f
RewriteRule ^ index.php [L]

[Erickhrs]

thankss

[cTapuk]

try this php artisan vendor:publish --force --tag=livewire:assets

[Piyush289kumar]

@dave-laye is just add location / { try_files $uri $uri/ /index.php?$query_string; } this
and save and redo again previous code and save and issue solve

[ArafatBareHouteneAziz]

php artisan vendor:publish --force --tag=livewire:assets

i love you

[radistyano]

thanks broooo

[RahimRh33]

انت معلم

[verybigelephants]

exactly this happened on my new vps server managed via laravel forge deploy "button". when i manually deployed my apps before it never happened. i wonder at what point the laravel forge deploy script fails

[habibtalib]

Hi, I have same issue too..

[waqarpixel]

try this php artisan vendor:publish --force --tag=livewire:assets

[redfieldchristabel]

@waqarpixel way is the best.

[bbbbobs]

Tested this on new install (laravel 10.10, filament v3) with the same issue - password not obscured and no POST method.

...I set all my repos to auto update to minor version too and I can't login to any of them now.

Edit: note, im using codespace on php:8.2.14-cli-bookworm.

[gagelafleur]

Having the same issue with laravel 10.48 and filament 3.2.

Everything works correctly when php artisan serve is running, but when that process is stopped the login form no longer works.

Running php artisan vendor:publish --force --tag=livewire:assets fixes the issue of the password not being obscured and the error message of The POST method is not supported for route admin/login. Supported methods: GET, HEAD. no longer shows, but I get Not Found. The requested URL was not found on this server. instead.

[rohansn28]

Hello @gagelafleur,
i just face the same issue in my project and looking for answer. I have same problem like yours when i pushed my laravel project on server and now not able to login, getting 404 page error.
tried this also php artisan vendor:publish --force --tag=livewire:assets but not fixing problem, can you share your solution if you find any. it wolud be very helpful since im new to laravel filament

[gagelafleur]

I'm guessing that you've got the application set up outside of the root directory if you're getting a 404 after login. If that's the case, you'll need to follow these instructions to get it working: https://livewire.laravel.com/docs/installation#configuring-livewires-update-endpoint

Those aren't 100% clear about it, but essentially you'll need to add the Livewire::setUpdateRoute call to the boot method of your app/Providers/AppServiceProvider.php and give it the path to your application.

[mdaushi]

I have the same issue too

anyone can help?

[mdaushi]

I found a solution. in my case The POST method is not supported for route admin/login occurred because the liveware/liveware.js file was not found. that's why I reinstalled the liveware and bundled the liveware manually.

you can see the details here: https://livewire.laravel.com/docs/installation#manually-bundling-livewire-and-alpine

hopefully it can help @SouhailBouaouiss

[muath-ye]

This is issue may occur because the cache, try with private browser.

[tahinuralam]

Delete the config file from bootstrap folder

[poynet]

Thanks !! Same problem has resolved by this : delete files in bootstrap/cache folder

[tahinuralam]

This is the easiest way

[gagelafleur]

After some digging it seems php artisan vendor:publish --force --tag=livewire:assets does fix the issue. The issues I had after that was due to the livewire update endpoint not being correct. If you're not running the app out of the root directory of the domain, you need to follow the instructions here to update the endpoint path: https://livewire.laravel.com/docs/installation#configuring-livewires-update-endpoint

[eae-omeyer]

Same problem here running on latest laravel 11 (sail + php 8.3 + octane) in conjunction with filament v3.2.69 and internachi modules v2.2.0. The login form looks strange - the password field shows only plaintext and the spinner on the submit button rotates permanently. No errors in the browser console tab, network tab looks also good. After pressing the submit button, the form gets sent via POST, resulting in the known error message. Looks like livewire/alpine is not working correctly somehow.

EDIT: Solved. It was my own fault as I disabled the automatic livewire asset injection before I started playing with filament. After reverting the livewire config back to "inject_assets = true" it works as expected.

[tahinuralam]

Bootstrap/cache/config.php

[rezabtuhin]

Thank you
It solved my issue.

[AminAhadian]

Same issue but solutions not working for me.
My Laravel app installs fine locally and on previous servers but fails on the new one. I’ve tried standard fixes—could this be due to missing PHP extensions or Laravel/PHP version mismatches? The server meets basic requirements, but I suspect a configuration difference.

[AminAhadian]

Same issue but solutions not working for me. My Laravel app installs fine locally and on previous servers but fails on the new one. I’ve tried standard fixes—could this be due to missing PHP extensions or Laravel/PHP version mismatches? The server meets basic requirements, but I suspect a configuration difference.

I solved my problem.
First run php artisan vendor:publish --force --tag=livewire:assets. Second in AppServiceProvider::boot():

Livewire::setScriptRoute(function ($handle) {
    return Route::get('/vendor/livewire/livewire.js', $handle);
});

[hasan-aftab]

Thanks brother @eae-omeyer, setting it to true resolve my problem

[ghostzero]

Idk if it helps, but I am getting this error using Safari. Using other browsers like chrome did not trigger the issue.

[jj63systems]

Same for me too. Currently trying to gat to the bottom of why this seemingly very significant safari error doesn't happen in chrome!

[tahinuralam]

https://t.me/filament_community Please come on Telegram official group

…

On Sat, May 11, 2024, 2:00 PM rohansn28 ***@***.***> wrote: Hello @gagelafleur <https://github.com/gagelafleur>, i just face the same issue in my project and looking for answer. I have same problem like yours when i pushed my laravel project on server and now not able to login, getting 404 page error. tried this also php artisan vendor:publish --force --tag=livewire:assets but not fixing problem, can you share your solution if you find any. it wolud be very helpful since im new to laravel filament — Reply to this email directly, view it on GitHub <#11481 (reply in thread)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ALVXJJF54EVIEE3TCXR227DZBXFZVAVCNFSM6AAAAABDPSOBMGVHI2DSMVQWIX3LMV43SRDJONRXK43TNFXW4Q3PNVWWK3TUHM4TGOJTGQ3TS> . You are receiving this because you commented.Message ID: ***@***.***>

[0xelsherif]

any one have the answer???

[tahinuralam]

Not config folder
It's config file
Bootstrap/cache/config.php

[0xelsherif]

@tahinuralam not working buddy

[0xelsherif]

It's working fine when I use php artisan serve but when I upload in cpanel or working on local host like xammp same errors popup can any one guide me step by step how to upload the project in shared host cpanel, thanks again

[daom89]

Try this commands:

composer dump-autoload
php artisan config:cache
php artisan route:cache
php artisan view:cache
php artisan vendor:publish --force --tag=livewire:assets
php artisan filament:assets
php artisan filament:cache-components

This works for me

[vedatkurtay]

Try this commands:

composer dump-autoload php artisan config:cache php artisan route:cache php artisan view:cache php artisan vendor:publish --force --tag=livewire:assets php artisan filament:assets php artisan filament:cache-components

This works for me

That commands work for me, thx. 🙏

[jeferssonbonilla1995]

I have the same problem, has anyone already found the solution?

[anoshiri]

I believe this is a livewire path issue. I had the same issue, then I realised that livewire.js was not loaded. Livewire.js loads from /vendor/livewire/livewire.js. This could be a problem if you're hosting in a sub-directory (like https://domain.com/development/project).

Solution 1:
To get around this, you will have to host on a subdomain like https://project.domain.com

Solution 2:
You will have to modify the livewire package. Personally, I'm not particularly eager to change a local copy of a package. I will work on a fix and make a pull request.

[jj63systems]

In Safari I see in the developer tools console

I assume this is significant though - and I don't see this in the console within Chrome.

Odd!

[youcefkacemDev]

you can fix that by changing the inject_assets to true in livewire.php config file
also i the published the livewire javaScript files in the public folder using the command bellow
by the way am using docker

artisan vendor:publish --force --tag=livewire:assets

[binaryfire]

In my case the problem was spatie/laravel-blade-comments. They say it's compatible with Livewire but it was causing all sorts of issues for me. Sharing this here in case it helps someone else. If none of the solutions mentioned in this thread work, I suggest taking a look at your package list.

[isa-fares]

I found a solution.
Solved add in routes/web.php adapting the name to your project:

use Livewire\Livewire;

Livewire::setScriptRoute(function ($handle) {
return Route::get('/AA_hosteleria/public/livewire/livewire.js', $handle);
});

Livewire::setUpdateRoute(function ($handle) {
return Route::post('/AA_hosteleria/public/livewire/update', $handle);
});

[Erickhrs]

Guys, I resolved it by following these steps on a shared host (Hostinger):

1. Zip all my Laravel files (with Filament) and upload them to the host directory.
2. Update the database information in the .env file.
3. Add the .htaccess file:

RewriteEngine On

# Handle Authorization Header
RewriteCond %{HTTP:Authorization} .
RewriteRule .* - [E=HTTP_AUTHORIZATION:%{HTTP:Authorization}]

# Redirect Trailing Slashes If Not A Folder...
RewriteCond %{REQUEST_FILENAME} !-d
RewriteCond %{REQUEST_URI} (.+)/$
RewriteRule ^ %1 [L,R=301]

# Remove public URL from the path
RewriteCond %{REQUEST_URI} !^/public/
RewriteRule ^(.*)$ /public/$1 [L,QSA]

# Send Requests To Front Controller...
RewriteCond %{REQUEST_FILENAME} !-d
RewriteCond %{REQUEST_FILENAME} !-f
RewriteRule ^ index.php [L]

4. Access the host via SSH and run in the laravel directory:

composer --version

If the version is < 2.0, run the following commands:

php -r "copy('https://getcomposer.org/installer', 'composer-setup.php');"
php -r "if (hash_file('sha384', 'composer-setup.php') === 'dac665fdc30fdd8ec78b38b9800061b4150413ff2e3b6f88543c636f7cd84f6db9189d43a81e5503cda447da73c7e5b6') { echo 'Installer verified'; } else { echo 'Installer corrupt'; unlink('composer-setup.php'); } echo PHP_EOL;"
php composer-setup.php
php -r "unlink('composer-setup.php');"

(This will create a .phar file)

5. Run the following commands:

php artisan key:generate
php artisan migrate
./composer.phar install

If it still doesn’t work, try:

./composer.phar dump-autoload

This will either resolve the issue or indicate what the problem is.

In my case, the problem was:

[u369742331@br-asc-web1845 public_html]$ ./composer.phar dump-autoload
Generating optimized autoload files
Class App\Http\Controllers\Api\QuestionsController located in ./app/Http/Controllers/api/QuestionsController.php does not comply with PSR-4 autoloading standard (rule: App\ => ./app). Skipping.
Class App\Models\Answer located in ./app/Models/answer.php does not comply with PSR-4 autoloading standard (rule: App\ => ./app). Skipping.
Class App\Models\Question located in ./app/Models/question.php does not comply with PSR-4 autoloading standard (rule: App\ => ./app). Skipping.
Class App\Models\Comment located in ./app/Models/comment.php does not comply with PSR-4 autoloading standard (rule: App\ => ./app). Skipping.
> Illuminate\Foundation\ComposerScripts::postAutoloadDump
> @php artisan package:discover --ansi

So basically, what you need to do is fix all the file or folder names that don’t follow the PSR-4 standard. After fixing them, run ./composer.phar dump-autoload again. It needs to run until all errors are resolved.

Tip: If you don’t understand what is PSR-4, paste the error into ChatGPT. It will tell you which folders and files names need fixing.

[MadJack1906]

I encountered this issue today, for context the codebase I'm working on was from laravel 9 and I migrated it to 10 (where I also installed filament in that version).

So I checked my app.js file and code below was missing so I added them. This worked on my case, I'm not sure if it will work on others.

import {
    Livewire,
    Alpine,
} from '../../vendor/livewire/livewire/dist/livewire.esm'

Alpine.plugin(Tooltip)

Livewire.start()

[mojgit]

If it helps, here's another discussion that helped me to solve this issue:

livewire/livewire#242 (comment)

[firdavsDev]

same problem with me