Php – Laravel 5.1 404 not found on apache server

.htaccessapachelaravel-5laravel-5.1PHP

I have currently hosted laravel 5.1 application to my 1and1.com server and I am facing a 404 not found errors to all my routes except for the root route i.e www.example.com/server/

The root route is working with get request but all the other routes are coming as 404 not found , everything is working good in localhost.

My application folder structure:

  • -example.com

    • -server
      • App
      • database
      • config
      • storage
      • .env
      • .htaccess
      • index.php
      • server.php

as you can see that I have removed the default laravel public folder and moved the contents to root.

My .htaccess

<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}]   RewriteCond     %{REQUEST_URI} !^  RewriteRule ^(.*)$ /$1 [L]  </IfModule>

My Index.php

<?php

/**
 * Laravel - A PHP Framework For Web Artisans
 *
 * @package  Laravel
 * @author   Taylor Otwell <taylorotwell@gmail.com>
 */

/*
|--------------------------------------------------------------------------
| Register The Auto Loader
|--------------------------------------------------------------------------
|
| Composer provides a convenient, automatically generated class loader for
| our application. We just need to utilize it! We'll simply require it
| into the script here so that we don't have to worry about manual
| loading any of our classes later on. It feels nice to relax.
|
*/

require __DIR__.'/bootstrap/autoload.php';

/*
|--------------------------------------------------------------------------
| Turn On The Lights
|--------------------------------------------------------------------------
|
| We need to illuminate PHP development, so let us turn on the lights.
| This bootstraps the framework and gets it ready for use, then it
| will load up this application so that we can run it and send
| the responses back to the browser and delight our users.
|
*/

$app = require_once __DIR__.'/bootstrap/app.php';

/*
|--------------------------------------------------------------------------
| Run The Application
|--------------------------------------------------------------------------
|
| Once we have the application, we can handle the incoming request
| through the kernel, and send the associated response back to
| the client's browser allowing them to enjoy the creative
| and wonderful application we have prepared for them.
|
*/

$kernel = $app->make(Illuminate\Contracts\Http\Kernel::class);

$response = $kernel->handle(
    $request = Illuminate\Http\Request::capture()
);

$response->send();

$kernel->terminate($request, $response);

Server.php

/**
 * Laravel - A PHP Framework For Web Artisans
 *
 * @package  Laravel
 * @author   Taylor Otwell <taylorotwell@gmail.com>
 */
$uri = urldecode(
    parse_url($_SERVER['REQUEST_URI'], PHP_URL_PATH)
);

// This file allows us to emulate Apache's "mod_rewrite" functionality from the
// built-in PHP web server. This provides a convenient way to test a Laravel
// application without having installed a "real" web server software here.
if ($uri !== '/' && file_exists(__DIR__.''.$uri)) {
    return false;
}

require_once __DIR__.'index.php';

Routes.php

Route::get('/', function(){
        echo'test';exit();
    });//test

Route::get('/s', function(){
        echo'testss';exit();
    });//test   

now if you see that the first route is working fine, but when I do www.example.com/server/s this gives 404 not found.

Best Answer

If your project migrated to the new server it could be in case if you use default project document root configuartion so it could be disabled to read your .htaccess file by default. You need to change AllowOverride option from "None" to "All" (in example) option value in the /etc/httpd/conf/httpd.conf (in case if centos):

<Directory /var/www/html/public>
    ...
    AllowOverride All
    ...
</Directory>

Then reload your server to apply changes

sudo service httpd reload
Related Topic