I developed an app in Laravel that uses Google authentication, it works perfectly on my localhost. When I deployed it in my nginx server (ubuntu 24.04) I get the Google login correctly and it proceeds to my main page as expected. But after that, no route is accessible. All of them throw me a 404. I’ve been googling it for ages but I can’t for the life of me find the solution for this.

EDIT: The 404 comes from Laravel, not nginx. The weird part is if I try php artisan route:list on the ser the routes are indeed missing but on the localhost they all show. The code is pretty much the same.

Here’s is my app conf file:

server {
    server_name partituras-cmcgb.duckdns.org;
    root /var/www/html/partviewer/public;

    index index.php index.html index.htm;

    location / {
        try_files $uri $uri/ /index.php?$query_string;
    }

    location ~ \.php$ {
        include snippets/fastcgi-php.conf;
        fastcgi_pass unix:/var/run/php/php8.3-fpm.sock;
        fastcgi_param SCRIPT_FILENAME $document_root$fastcgi_script_name;
        include fastcgi_params;
    }

    location ~ /\.ht {
        deny all;
    }

    error_log /var/log/nginx/partviewer-error.log;
    access_log /var/log/nginx/partviewer-access.log;

    listen 443 ssl; # managed by Certbot
    ssl_certificate /etc/letsencrypt/live/partituras-cmcgb.duckdns.org/fullchain.pem; # managed by Certbot
    ssl_certificate_key /etc/letsencrypt/live/partituras-cmcgb.duckdns.org/privkey.pem; # managed by Certbot
    include /etc/letsencrypt/options-ssl-nginx.conf; # managed by Certbot
    ssl_dhparam /etc/letsencrypt/ssl-dhparams.pem; # managed by Certbot

}
server {
    if ($host = partituras-cmcgb.duckdns.org) {
        return 301 https://$host$request_uri;
    } # managed by Certbot


    listen 80;
    server_name partituras-cmcgb.duckdns.org;
    return 404; # managed by Certbot


}

Does the uid you are using to run nginx have permissions to read the root folder (defined above as /var/www/html/partviewer/public , not the actual linux root) and below?

Yeah, sounds like a permissions error.

Matt The Horwood
link
fedilink
English
12M

could you replace try_files $uri $uri/ /index.php?$query_string; with try_files $uri $uri/ /index.php?$is_args$args

That might work

@spirinolas@lemmy.world
creator
link
fedilink
English
12M

It was the first “solution” on google. Didn’t work.

Matt The Horwood
link
fedilink
English
12M

Oh, does the route hit your location? What’s in the logs?

@spirinolas@lemmy.world
creator
link
fedilink
English
1
edit-2
2M

The correct URL appears in the browser but the page shows a 404. According to the logs they don’t exist…but they’re there…

You’re probably going to need logs to rule out any permissions errors or the like.

Responsabilidade
link
fedilink
English
12M

I’m not sure, but looks like you’re denying all .htaccess files. Laravel depends on .htaccess to make things work properly

Take a look on Laravel docs - Deployment to make sure your configs are right

@spirinolas@lemmy.world
creator
link
fedilink
English
12M

I already went through that. I wouldn’t post here without starting with the official documentation.

Responsabilidade
link
fedilink
English
-12M

Why are you using that?

    location ~ /\.ht {
        deny all;
    }

You’re denying the access to your root, which is the public/ folder and has the file .htaccess that has

<IfModule mod_rewrite.c>
    <IfModule mod_negotiation.c>
        Options -MultiViews -Indexes
    </IfModule>

    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]

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

This file handles the income requests and send to the front controller.

@fluckx@lemmy.world
link
fedilink
English
22M

The .htaccess file does nothing on nginx though.

@tahoe@lemmy.world
link
fedilink
English
92M

As far as I know only Apache uses .htaccess files, Nginx works a different way

Responsabilidade
link
fedilink
English
02M

deleted by creator

@tahoe@lemmy.world
link
fedilink
English
22M

I was the same until like two months ago when I had to learn Nginx!

@jdf@lemmy.world
link
fedilink
English
2
edit-2
2M

Check out this page. https://laravel.com/docs/10.x/deployment

You have to redirect all requests to index.php in the public folder. There is a sample Nginx configuration file on this page.

autokludge
link
fedilink
English
12M

Could it be a route cache thing? may be worth trying artisan route:clear followed by artisan route:cache

Create a post

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don’t control.

Rules:

  1. Be civil: we’re here to support and learn from one another. Insults won’t be tolerated. Flame wars are frowned upon.

  2. No spam posting.

  3. Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it’s not obvious why your post topic revolves around selfhosting, please include details to make it clear.

  4. Don’t duplicate the full text of your blog or github here. Just post the link for folks to click.

  5. Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).

  6. No trolling.

Resources:

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

  • 1 user online
  • 124 users / day
  • 419 users / week
  • 1.16K users / month
  • 3.85K users / 6 months
  • 1 subscriber
  • 3.68K Posts
  • 74.2K Comments
  • Modlog