@wag0325

Generally, for /, you’d have a location block like this:

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

…which is missing in the configuration that you’ve posted. That’s a standard / location block for just about any CMS or blog using PHP.

I’d recommend adding that block to your configuration, and then restarting NGINX.

@wag0325

I’ve setup quite a few WordPress and WordPress MS instances on NGINX and I’ve never ran in to an instance where q=$uri&$args was needed instead of just ?$args.

So instead of:

try_files $uri $uri/ /index.php?q=$uri&$args;

I would recommend using:

try_files $uri $uri/ /index.php?$args;

…

That being said, I would recommend creating a backup of default, and starting clean. Once you’ve got a backup of default, run the following command.

This will wipe this file clean, so make sure you have a backup.

truncate -s 0 /etc/nginx/sites-available/default

Once that’s done, open it back up:

nano /etc/nginx/sites-available/default

and paste in:

server {
    listen 80;
    listen [::]:80;
    server_name pinkbulletin.com www.pinkbulletin.com;

    return 301 https://$server_name$request_url;
}

server {
    listen 443 ssl http2;
    listen [::]:443 ssl http2;

    include snippets/ssl-pinkbulletin.com.conf;
    include snippets/ssl-params.conf;

    root /var/www/html;

    index index.php index.html;

    server_name pinkbulletin.com www.pinkbulletin.com;

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

    location ~ [^/]\.php(/|$) {
        fastcgi_split_path_info ^(.+?\.php)(/.*)$;

        fastcgi_pass  127.0.0.1:9000;
        fastcgi_index index.php;

        include fastcgi_params;
    }

    location ~ /.ht {
        deny all;
    }

    location ~ /.well-known {
        allow all;
    }

    location /phpmyadmin {
        index index.php;
    }

    if (!-e $request_filename) {
        rewrite /wp-admin$ $scheme://$host$uri/ permanent;
        rewrite ^/[_0-9a-zA-Z-]+(/wp-.*) $1 last;
        rewrite ^/[_0-9a-zA-Z-]+(/.*\.php)$ $1 last;
    }
}

Now, make a backup of /etc/nginx/fastcgi_params, and then run:

truncate -s 0 /etc/nginx/fastcgi_params

Now open it up:

nano /etc/nginx/fastcgi_params

and paste in:

fastcgi_connect_timeout 60;
fastcgi_send_timeout 180;
fastcgi_read_timeout 180;
fastcgi_buffer_size 512k;
fastcgi_buffers 512 16k;
fastcgi_busy_buffers_size 1m;
fastcgi_temp_file_write_size 4m;
fastcgi_max_temp_file_size 4m;
fastcgi_intercept_errors off;

fastcgi_param SCRIPT_FILENAME   $request_filename;
fastcgi_param PATH_INFO         $fastcgi_path_info;
fastcgi_param PATH_TRANSLATED   $document_root$fastcgi_path_info;
fastcgi_param QUERY_STRING      $query_string;
fastcgi_param REQUEST_METHOD    $request_method;
fastcgi_param CONTENT_TYPE      $content_type;
fastcgi_param CONTENT_LENGTH    $content_length;
fastcgi_param SCRIPT_NAME       $fastcgi_script_name;
fastcgi_param REQUEST_URI       $request_uri;
fastcgi_param DOCUMENT_URI      $document_uri;
fastcgi_param DOCUMENT_ROOT     $document_root;
fastcgi_param SERVER_PROTOCOL   $server_protocol;
fastcgi_param REQUEST_SCHEME    $scheme;
fastcgi_param HTTPS             $https if_not_empty;
fastcgi_param HTTP_PROXY        "";
fastcgi_param GATEWAY_INTERFACE CGI/1.1;
fastcgi_param SERVER_SOFTWARE   nginx/$nginx_version;
fastcgi_param REMOTE_ADDR       $remote_addr;
fastcgi_param REMOTE_PORT       $remote_port;
fastcgi_param SERVER_ADDR       $server_addr;
fastcgi_param SERVER_PORT       $server_port;
fastcgi_param SERVER_NAME       $server_name;
fastcgi_param REDIRECT_STATUS   200;

Save the file, exit and then restart NGINX.

Once you’ve got those changes applied, let’s see what happens then. If any errors pop up, check the logs again by running:

tail -20 /var/log/nginx/error.log

and paste that to a code block and we’ll continue to troubleshoot :-).