```server { listen 80; # you can use 443 and l...
# orm-help
j
Copy code
server {
    listen 80; # you can use 443 and letsencrypt to get SSL for free
    server_name 143.198.151.73; # domain name
    #access_log /var/log/somestuff/access.log; # mkdir dir first
    #error_log /var/log/somestuff/error.log error;

    # for public asset into _next directory
    location _next/ {
        alias /var/www/html/nextjs/.next/;
        expires 30d;
        access_log on;

    location / {
        # reverse proxy for next server
        proxy_pass <http://localhost:8000>; # your nextJs service and port
        proxy_http_version 1.1;
        proxy_set_header Upgrade $http_upgrade;
        proxy_set_header Connection 'upgrade';
        proxy_set_header Host $host;
        proxy_cache_bypass $http_upgrade;

        # we need to remove this 404 handling
        # because next's _next folder and own handling
        # try_files $uri $uri/ =404;
        }
    }

}
h
This has more to do with NGINX than, Prisma itself. You’ll probably have a better luck asking in a NGINX forum instead here.