404 Not Found, but route exist in Laravel 5.4

Question

I'm using PhpStorm. I can run and open the index.php, but when I want to press submit button (post sign in), its display 404 not found.

Web server Apache 2.4 running on Windows 10.

This is my home

This is my route

I think you should probably go through the documentation of Laravel. Go through it https://laravel.com/docs/5.4/installation — VijayRana, May 01 '17 at 06:32
What is the URL that you see in the browser's address bar when this page does not work? — LazyOne, May 01 '17 at 08:42
You should include exact error and code of the form you try to submit — Marcin Nabiałek, May 01 '17 at 08:48
another thing even though it looks not to be that here : if you have a route defined like /planning/{weeknumber} and then another like /planning/day, you can't reach the /planning/day unless you declare it before the other, because 'day' will be passed as a variable to the 1st route, and you might get a 404, depending on how your controller manages it. — Emmanuel BRUNO, Mar 06 '19 at 14:22
Can you provide more information? Which route is the form sent to? — Nico Haase, May 10 '19 at 14:41

score 63 · Answer 1 · answered Oct 14 '18 at 12:41

63

I'm not entirely sure why all the down-votes, especially since this is a common issue and the cause can be hidden for someone new to the Laravel environment. I know this is an old post, but I add it here for future newbies.

The first thing I suggest trying is running php artisan route:list from the command line (from your project root directory). This will list all the routes that Laravel can register and if there are any errors, usually they will show up here.

The second thing I suggest is to ensure that the URL matches route. I can't tell you how many times I've tried to figure out why my route was returning a 404 simply because my form was posting to something like /insertStudent when my route was defined as /admin/insertStudent

The third thing I suggest is to ensure the method you are calling exists. Are your methods really called postSignIn and postInsertStudent and not simply SignIn and InsertStudent? Keep in mind that both the URL and method names are case sensitive and should match where you define the route, the URL that is being called, and the method that is receiving the request.

Finally if all that checks out, one last thing I might suggest you try is running php artisan route:clear. This resets the route cache.

answered Oct 14 '18 at 12:41

ChronoFish

2,758
3
22
34

i copy existing directory to new, also run `php artisan route:clear` but still page not found at new directory but on old directory page is found. any idea ? – zukijuki Jun 28 '19 at 10:34
@anunixercoder, I suggest starting a new question being very specific about what you've tried and what error you're seeing. As mentioned, run php artisan route:list - you won't see what you want through the browser until route:list runs successfully with the expected output. – ChronoFish Jul 10 '19 at 18:53
Only other point to suggest is to ensure you are not using "$" in your routes. I tried using /users/edit_project_access/{$userId}/{$projectId} which also gave me a 404. Check that your URLs dont have $ signs as such: /users/edit_project_access/{userId}/{projectId} – Christoff X Nov 24 '20 at 12:41
1

May I suggest to add `check route ordering` ? That was what I did wrong – M at Mar 05 '21 at 07:39
1

Upvote for being patient and understanding – Qudratxo'ja Musayev May 04 '21 at 09:11

Ruberandinda Patience · Answer 2 · 2020-03-03T08:35:00.687

18

Please Make you have Apache configured with the following information

in /path/to/apache2/installation/conf/httpd.conf

Add the following information

<Directory "path/to/laravel/project/public">
    Allowoverride All
</Directory>

.htaccess file located in public folder make sure that it has the following

<IfModule mod_rewrite.c>
    <IfModule mod_negotiation.c>
       Options -MultiViews
   </IfModule>
   Options +FollowSymlinks
   RewriteEngine On

   # Redirect Trailing Slashes...
   RewriteRule ^(.*)/$ /$1 [L,R=301]

   # Handle Front Controller...
   RewriteCond %{REQUEST_FILENAME} !-d
   RewriteCond %{REQUEST_FILENAME} !-f
   RewriteRule ^ index.php [L]
</IfModule>

Remember to enable mod_rewrite module

sudo a2enmod rewrite

edited Mar 03 '20 at 08:35

answered Sep 09 '17 at 13:20

Ruberandinda Patience

2,075
2
13
16

Can you explain that further? I don't think that `/etc/apache2/apache2.conf` is present on Windows. Additionally, which parts are needed and why? Keep in mind that others should be able to learn from your answer – Nico Haase May 10 '19 at 14:43
1

It took me ages to finally find this answer that helped. – Daniel Katz Jan 22 '20 at 23:28

score 13 · Answer 3 · answered Jan 21 '20 at 11:19

try

php artisan route:clear
php artisan route:cache

and then type this and see whether your route exists in the list

php artisan route:list

and also in Middleware\VerifyCsrfToken.php check post routes are allowed


class VerifyCsrfToken extends Middleware {

    /**
     * The URIs that should be excluded from CSRF verification.
     *
     * @var array
     */
    protected $except = [
        'api/*'
    ];

}

Olly · Answer 4 · 2021-03-26T09:11:28.513

12

I had the same Issue & resolved it by changing the way Routes were ordered.

Before:

Route::get('/p/{post}', 'PostsController@show');
Route::get('/p/create', 'PostsController@create');

After: (and the that 404 disappeared)

Route::get('/p/create', 'PostsController@create');
Route::get('/p/{post}', 'PostsController@show');

edited Mar 26 '21 at 09:11

answered Jun 27 '20 at 09:47

Olly

121
1
6

2

You saved my life thanks. – Krzysztof Duszczyk Jan 23 '21 at 12:37
1

You saved me. I add a new method to ResourceRegister and was stuck all day. The route is shown in the route:list as well. If I had many other accounts I'd have come and upvoted this all day. Thanks again. – Gayan Kavirathne May 15 '21 at 11:23
Taking the same example you have given, I think the reason is, If we had /p/{post} before, route is matching the request to /p/create to /p/{post} with create as the variable value to {post} . – Gayan Kavirathne May 15 '21 at 11:32

score 6 · Answer 5 · answered May 09 '19 at 03:03

6

I had the same issue and fixed by following

I have edit .htaccess file

RewriteEngine On
RewriteBase /path/of/project/folder/
# change above to your site i.e.,  RewriteBase /whatever/public/

Hope it will work for you

answered May 09 '19 at 03:03

Ram Chander

648
6
23

It worked for me ! I had an alias and was working on subfolder of my localhost. Only homepage was working. After adding RewriteBase /myalias/ in htaccess file of public folder, my routes started working ! – Aurel May 26 '21 at 08:00

score 6 · Answer 6 · answered Nov 03 '19 at 14:33

This is old question but is active yet. for windows users if you using CAPITAL characters (upper-case letter) in your project folder you should using same in your browser. If your project is in "c:\xampp\htdocs\MyProject\" you should using MyProject as url instead of myproject for example in the above project (MyProject) following route:

Route::get('/dashboard', function () {
    return 'welcome to dashboard!';
});

will work if you use:

http://MyProject/dashboard

but is better using lowercase characters in directories

score 4 · Answer 7 · answered Jul 15 '20 at 08:25

4

I was going crazy about my routes not working and here is also a quick fix. I had the following route:
users/{user}/user-detail-changes/{user-detail-change}/update-status
The fix was to rename parameters. Laravel doesn't accept minus character -. Rather than that you have to use camelCase or underscore (_) variable naming conventions.
So it has to be like:
users/{user}/user-detail-changes/{userDetailChange}/update-status

answered Jul 15 '20 at 08:25

Franci

51
4

1

This turned out to be the issue I was having too. Thanks, you have saved me quite a bit of hair pulling – kaan_a Jul 18 '20 at 05:35
Thank you for this answer – Kaustubh Bagwe Apr 15 '21 at 09:09

score 3 · Answer 8 · answered Oct 01 '19 at 18:40

3

Make sure you added correct Accept header.

In my case I tried to access api endpoints and each time recieved 404 resource not found. When I've added Accept: application/json header I got response from matched route

answered Oct 01 '19 at 18:40

Anthony Artemiev

1,390
1
12
14

score 2 · Answer 9 · answered Jan 24 '21 at 16:52

When at the time of website hosting there is the problem 404 Not Found Error on requested pages. At That time there is only home page is work fine. And if i request another page for e.g. mydomain.com/any_page then it sends me to the 404 Not Found Error Then i looked at my controller files and other routes files to solve the problem. Finally i think there is absent of the .htaccess file When i just added the .htaccess file to the same folder of the index.php of the laravel project then it juts works file.

Conclusion

By adding the .htaccess file at the same folder location of the index.php it solves the 404 page not found error in my laravel Project.

score 1 · Answer 10 · answered May 01 '17 at 12:03

1

make sure, the url passed is equal in your route. check the parameters and action in the form. To get clear answer post your mvc

answered May 01 '17 at 12:03

Kayal

13
7

Thank you, I'm forget to direct and declare port of localhost URL – May 23 '17 at 03:48

score 1 · Answer 11 · answered Dec 24 '19 at 19:32

I had the same issue recently and I thought I was using a Reserved word, which I couldn't find in the list of reserved words of PHP.

Originally my Routes/web.php was:

Route::post('sysinfo/store',['as'=>'sysinfo.store', 'uses'=>'SysinfoController@store']);

After I changed to another name as shown bellow, it worked!

Route::post('newsysinfo/store',['as'=>'newsysinfo.store',   'uses'=>'SysinfoController@store']);

What's weird is that I have other working routes such as:

Route::get('sysinfo/',['as'=>'sysinfo.index',   'uses'=>'SysinfoController@index']);
Route::post('sysinfo/{sysinfo}',['as'=>'sysinfo.update',   'uses'=>'SysinfoController@update']);
Route::get('sysinfo/create',['as'=>'sysinfo.create',   'uses'=>'SysinfoController@create']);
Route::get('sysinfo/{id}/edit',['as'=>'sysinfo.edit',   'uses'=>'SysinfoController@edit']);
Route::get('sysinfo/{sysinfo}/destroy',['as'=>'sysinfo.destroy',   'uses'=>'SysinfoController@destroy']);

Although it's not an explanation of the causes of the problem, perhaps this workaround can help you.

I wager that your post route for `sysinfo/{sysinfo}` was answering all of your attempts to hit `sysinfo/store` — Conspicuous Compiler, Feb 05 '20 at 19:55

score 1 · Answer 12 · answered Jan 05 '20 at 16:27

Don't forget the order of your routes. For example, if you want to go to /path/second and have the following routes registered:

Route::get('/path/{dynamic_second}', 'Controller@actionDynamic');

Route::get('/path/{dynamic_second}/{dynamic_third}', 'Controller@third');

Route::get('/path/second', 'Controller@action');

This will break, as second is consumed by /path/{dynamic_second}.

If you want to access /path/second, you have to have your routes listed like so:

Route::get('/path/second', 'Controller@action');

Route::get('/path/{dynamic_second}', 'Controller@actionDynamic');

Route::get('/path/{dynamic_second}/{dynamic_third}', 'Controller@third');

score 1 · Answer 13 · answered Aug 11 '20 at 09:44

1

Hello! I also encountered this problem before. Please check your Apache's httpd.conf file. Make sure that you enabled the LoadModule rewrite_module modules/mod_rewrite.so by removing the # from the start line of the code.

And also change inside the httpd.conf from Require all denied to Require all granted, AllowOverride All, and Options Indexes FollowSymLinks

Like This:

answered Aug 11 '20 at 09:44

Hashmat Waziri

561
7
9

Yeah, this was my problem, a new installation of apache that didn't have the `LoadModule` uncommented. – Nick Nov 10 '20 at 01:34

score 1 · Answer 14 · answered Mar 02 '21 at 07:43

On Centos

Set the proper permission for the application files and directories.

chown -R apache.apache /var/www/YOUR_LARAVEL_APP
chmod -R 755 /var/www/YOUR_LARAVEL_APP
chmod -R 755 /var/www/YOUR_LARAVEL_APP/storage

SELinux enabled systems also run the below command to allow write on storage directory.
```
chcon -R -t httpd_sys_rw_content_t /var/www/myLaravelApp/storage
```

Finally, access your Laravel application in a web browser.

Note: If you are using Nginx use nginx.nginx instead of apache.apache.

score 0 · Answer 15 · answered Feb 26 '19 at 16:35

0

Changing the server port worked for me after trying several fixes all to no avail. I was running on loalhost:3000 and changed to localhost:4000. I think this might have to do with some memory cahe

answered Feb 26 '19 at 16:35

ogunniran olusola

1

score 0 · Answer 16 · answered Feb 17 '20 at 08:59

0

Update 2020
There are many case happened above, I've once more case I met a long time but I still forget and sometimes I dont know why. This is some url patterns is the same, example abc.com/c/{get_an_id} and abc.com/c/get_text. You can change order but only first can run, 404 for the second url.

answered Feb 17 '20 at 08:59

May'Habit

866
7
13

This should be its own question. But the issue is the path with the parameter ({get_an_id}) needs to come second. Otherwise "get_text" would be sent as the parameter value. If it is already second and getting a 404, it's probably because a lookup is failing (.i.e abc.com/c/54 returns 404 because there is no id that matches 54 in your DB) – ChronoFish May 29 '20 at 11:44

score 0 · Answer 17 · answered Oct 01 '20 at 22:41

Maybe this help someone, I fix this problem changing the order from my routes in laravel.

in my case i had the route ..users/crea --> 404 error

 Route::get('users', 'Admin\UserController@index')->name('users.index')
 Route::put('users/{user}', 'Admin\UserController@update')->name('users.update')
 **Route::get('users/crea', 'Admin\UserController@crea')->name('users.crea');**

and to fixed

 Route::get('users', 'Admin\UserController@index')->name('users.index')
 *Route::get('users/crea', 'Admin\UserController@crea')->name('users.crea');*
 Route::put('users/{user}', 'Admin\UserController@update')->name('users.update')

score 0 · Answer 18 · answered Nov 13 '20 at 21:08

For me, it was issue with .htaccess file. Make sure you have the .htaccess in public_html folder. I downloaded this file from one server but the dot(.) was removed by the downloader. Then when I uploaded in another server, the dot(.) was missing and I got 404.

My .htaccess looks like below:

# disable directory browsing, but specific file browsing is possible, e.g. /js/bootstrap.js
        
    Options ExecCGI Includes IncludesNOEXEC SymLinksIfOwnerMatch
#To set which file will be acted as index file: DirectoryIndex index.php
<IfModule mod_rewrite.c>
    <IfModule mod_negotiation.c>
        Options -MultiViews
    </IfModule>

    RewriteEngine On

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

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

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


<Files 403.shtml>
order allow,deny
allow from all
</Files>

# deny from some DDoS attackers ip
# deny from 69.171.251.0/24


# php -- BEGIN cPanel-generated handler, do not edit
# This domain inherits the “PHP” package.
# php -- END cPanel-generated handler, do not edit

score 0 · Answer 19 · answered Dec 08 '20 at 19:20

Im using Homestead, and after being stuck for quite some time trying everything that there was to try, what finally worked was re-checking my Hosts file (/etc/hosts on *nix systems), verifying my Homestead.yaml configuration file, and running the 'provision' command on the Homestead Vagrant Box.

The provision seems to have cleared some caches previously held or deployed the currently working site, honestly can't understand what changed since the databases were working and unit tests were passing.

But leaving it here in case it can help somebody out.

score 0 · Answer 20 · answered Dec 24 '20 at 05:34

one thing i would like to add for user's who use nginx server and have configured server blocks(virtual hosts). check which server block is activated in your nginx conf files.

also in /etc/hosts file check whether you are using correct url to your server block or not.

also check your IP address there.

Plus all other point that are mentioned.

score 0 · Answer 21 · answered Feb 04 '21 at 06:44

0

For me it was a permissions issue. User I was logged in with didnt have the necessary assigned role that gave the required permission to view said URL/section.

answered Feb 04 '21 at 06:44

SupaMonkey

646
6
22

score 0 · Answer 22 · answered Apr 06 '21 at 11:02

0

Make sure you are not running another laravel project on the same port.

answered Apr 06 '21 at 11:02

Tonykay

11
4

score 0 · Answer 23 · answered May 15 '21 at 20:55

0

One more possibility... If the controller has Laravel's findOrFail() method, and the item sought is not found, a 404 page is returned.

answered May 15 '21 at 20:55

Usually Confused

1
1

score -1 · Answer 24 · answered Aug 08 '18 at 16:47

-1

dontforget, the url is sensitive case to the folder name

answered Aug 08 '18 at 16:47

david valentino

783
9
16

Can you explain further what this means? How did you guess that there is a problem using cases? How to solve this? – Nico Haase May 10 '19 at 14:42
1

if your htdocs subfolder contain capital case, then you must call the url with capital case.ie. folder is AvenGers inside the htdocs, then must call localhost/AvenGers – david valentino May 12 '19 at 03:37

score -3 · Answer 25 · answered Jul 14 '20 at 15:23

-3

I had the same problem but the solution is that simple :

go to cmd and tap cd #your project path#

then tap php artisan serve

copy the link of the server given (http://127.0.0.1:8000) to your browser, and it'll work!

answered Jul 14 '20 at 15:23

selharem

29
9

404 Not Found, but route exist in Laravel 5.4

25 Answers25

On Centos

Linked