Nginx 作為虛擬主機和反向代理

Question

我在 Ubuntu 服務器上運行 GlassFish（一個 Java 應用程序服務器）。 我還在不同的端口上運行 phppgadmin，比如說 5555 並配置了 apache。

我在 GlassFish 前面使用 Nginx 作為反向代理。 （尚未設置端口 443 的 Ssl 和配置。）

server {
  listen          80;
  server_name     my_domain;

  location / {
        proxy_set_header X-Forwarded-Host $host;
        proxy_set_header X-Forwarded-Server $host;
        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
        proxy_pass http://my_ip_number:8080;
  }
  
  location /phppgadmin {
        proxy_set_header X-Forwarded-Host $host;
        proxy_set_header X-Forwarded-Server $host;
        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
  
        proxy_pass http://my_ip_number:5555/phppgadmin;
  }  
}

當我嘗試通過在/etc/nginx/conf.d/設置以下文件為此處描述的/etc/nginx/conf.d/創建虛擬主機時。 在http://postfixadmin.my_domain/setup.php我只看到 glassfish 的 404 頁。
設置了子域的 DNS A記錄。
我的配置有什么問題？ 如何解決這個問題？

提前致謝

server {
   listen 80;
   listen [::]:80;
   server_name postfixadmin.my_domain;

   root /usr/share/postfixadmin/public/;
   index index.php index.html;

   access_log /var/log/nginx/postfixadmin_access.log;
   error_log /var/log/nginx/postfixadmin_error.log;

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

   location ~ ^/(.+\.php)$ {
        try_files $uri =404;
        fastcgi_pass unix:/run/php/php7.4-fpm.sock;
        fastcgi_index index.php;
        fastcgi_param SCRIPT_FILENAME $document_root$fastcgi_script_name;
        include /etc/nginx/fastcgi_params;
   }
}

Answer 1

我意識到我的服務器的設置方式，不可能實現我在上面嘗試做的事情。 不需要為 PostfixAdmin 創建虛擬主機！

這是我的最終配置，一切正常。

server {
  listen          my_ip_number:80;
  server_name     example.com www.example.com;

  include snippets/letsencrypt.conf;
  return 301 https://$host$request_uri;
}

server {
    listen 443 ssl http2;
    server_name www.example.com;

    ssl_certificate /etc/letsencrypt/live/example.com/fullchain.pem;
    ssl_certificate_key /etc/letsencrypt/live/example.com/privkey.pem;
    ssl_trusted_certificate /etc/letsencrypt/live/example.com/chain.pem;
    include snippets/ssl.conf;
    include snippets/letsencrypt.conf;

    return 301 https://example.com$request_uri;
}


server {
    listen 443 ssl http2;

    server_name example.com;

    ssl_certificate /etc/letsencrypt/live/example.com/fullchain.pem;
    ssl_certificate_key /etc/letsencrypt/live/example.com/privkey.pem;
    ssl_trusted_certificate /etc/letsencrypt/live/example.com/chain.pem;
    include snippets/ssl.conf;
    include snippets/letsencrypt.conf;

    access_log  /var/log/nginx/example.com.access.log; # upstreamlog;
    error_log   /var/log/nginx/example.com.error.log;
    rewrite_log on;

  location / {
        proxy_set_header X-Forwarded-Host $host;
        proxy_set_header X-Forwarded-Server $host;
        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
        proxy_set_header HTTPS "on";

        proxy_pass http://my_ip_number:8080;
  }

  location /phppgadmin {
        proxy_set_header X-Forwarded-Host $host;
        proxy_set_header X-Forwarded-Server $host;
        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;

        proxy_pass http://my_ip_number:5555/phppgadmin;
  }


  location /mypostfixadmin {
        proxy_pass http://my_ip_number:5555/postfixadmin;

        proxy_set_header Host $http_host;
        proxy_set_header Upgrade $http_upgrade;
        proxy_set_header Connection "upgrade";

        proxy_set_header X-Forwarded-Host $host;
        proxy_set_header X-Forwarded-Server $host;
        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
        proxy_set_header X-Scheme $scheme;

        client_max_body_size 0;
  }

}