Keith

Hello @codexonics , thank you for the detailed explanation. It was my side error. I was new to Nginx, and got mixed up with a lot of basic server configuration, and one of which was the cause of this freeze.

Now that I have finished testing, I have other questions, but I think it is better to create another ticket.

• This reply was modified 2 years, 9 months ago by Keith.

server {
        listen 80;
        listen [::]:80;
        root /var/www/class.giai.org;
        index  index.php index.html index.htm;
        server_name 1.maindomain.com 2.maindomain.com newdomain.com;

        error_log /var/log/nginx/1.maindomain.com_error.log;
        access_log /var/log/nginx/1.maindomain.com_access.log;
        
        location / {
                try_files $uri $uri/ /index.php?$args;
        }
        location ~ \.php$ {
                include snippets/fastcgi-php.conf;
                fastcgi_pass unix:/run/php/php8.1-fpm.sock;
                fastcgi_param   SCRIPT_FILENAME $document_root$fastcgi_script_name;
        }
}


server {
        listen 443 ssl http2;
        error_log /var/log/nginx/2.maindomain.com_error.log;
        access_log /var/log/nginx/2.maindomain.com_access.log;
        root /var/www/2.maindomain.com; #(Not sure if I should uncomment this line, as there is no 2.main.com folder in /var/www)
        server_name 2.maindomain.com;
        ssl_certificate /etc/letsencrypt/live/2.maindomain.com/fullchain.pem;
        ssl_certificate_key /etc/letsencrypt/live/2.maindomain.com/privkey.pem;
}

server {
        listen 443 ssl http2;
        root /var/www/1.maindomain.com;
        error_log /var/log/nginx/1.maindomain.com_error.log;
        access_log /var/log/nginx/1.maindomain.com_access.log;
        server_name 1.maindomain.com;
        ssl_certificate /etc/letsencrypt/live/1.maindomain.com/fullchain.pem;
        ssl_certificate_key /etc/letsencrypt/live/1.maindomain.com/privkey.pem;

Above code is my sample for current server blocks. For the (sub)domains that are defined in 80’s server_name, all are properly mapped. At least I can access them without ‘http”s”‘. For the ones that I have not defined in 80 port’s server block, it is not accessible, as expected.

I think the problem lies in server blocks related to 443. Websites are loaded when I call “http://xxx.com “, but with “https://~ “, it gives me 404. (added space before ending ” due to rendering issue)

I tried to define 443 port’s server name and ssl cert mapping individually for each domain, which seems working because even if I have 404 for 2.maindomain.com. I do have ssl cert on, while newdomain.com without 443 port’s server block has no ssl cert recognized by browsers.

What still puzzles me is where to put in additional settings and what has to be added.

• This reply was modified 2 years, 9 months ago by Keith.
• This reply was modified 2 years, 9 months ago by Yui.
• This reply was modified 2 years, 9 months ago by Keith.

Except the blog No1., all other webpages show NginX server page if it is defined in config, and empty page if not defined.

I must have done something wrong

I have stumbled on this one, and it seems that I should have another server for better security, in addition to performance issue that I’ve raised above. Not sure what are optimal hardware specs for each server, web / DB, but this is something I feel that I can find good information from googling.