在Linux（Ubuntu20.04）用Nginx部署ASP.NET Core gRPC服务遇502错误求助

问题分析 #

你遇到的Status(StatusCode="Unavailable", Detail="Bad gRPC response. HTTP status code: 502")错误，核心原因是Nginx无法成功连接后端Kestrel服务，或请求路由匹配规则不符合gRPC的调用路径要求。结合你的配置，主要问题集中在Kestrel的HTTPS配置冲突和Nginx请求路径匹配逻辑两点。

排查与修复步骤 #

1. 确认后端服务运行状态 #

先确保ASP.NET Core gRPC服务正常启动：

• 若用systemd托管服务，执行：

  sudo systemctl status your-grpc-service-name
  

• 在服务器本地测试Kestrel端口可用性：

  curl -v http://127.0.0.1:5001/
  

  正常响应会返回gRPC提示文本：Communication with gRPC endpoints must be made through a gRPC client...

2. 修正Kestrel配置（核心修复） #

Nginx已通过Let's Encrypt处理SSL证书，后端Kestrel无需再启用HTTPS——否则Nginx的grpc_pass（默认使用明文HTTP/2）无法与Kestrel的HTTPS端口建立连接，直接触发502错误。

修改appsettings.json

将Kestrel端点改为HTTP协议：

{
  "Logging": {
    "LogLevel": {
      "Default": "Information",
      "Microsoft.AspNetCore": "Warning"
    }
  },
  "AllowedHosts": "*",
  "Kestrel": {
    "Endpoints": {
      "Grpc": {
        "Url": "http://localhost:5001",
        "Protocols": "Http2"
      }
    }
  }
}

修改Program.cs

调整监听配置，仅监听本地端口（避免直接暴露服务，提升安全性），同时移除生产环境的HTTPS重定向逻辑：

using GrpcService.Services;
using Microsoft.AspNetCore.Server.Kestrel.Core;

var builder = WebApplication.CreateBuilder(args);

builder.WebHost.ConfigureKestrel(options =>
{
    // 监听本地5001端口，使用HTTP/2明文协议
    options.ListenLocalhost(5001, o => o.Protocols = HttpProtocols.Http2);
});

builder.Services.AddGrpc();

var app = builder.Build();

// 移除HTTPS重定向（Kestrel已使用HTTP，重定向会导致请求异常）
// if (app.Environment.IsProduction())
// {
//     app.UseHttpsRedirection();
// }

app.MapGrpcService<GreeterService>();
app.MapGet("/", () => "Communication with gRPC endpoints must be made through a gRPC client. To learn how to create a client, visit: https://go.microsoft.com/fwlink/?linkid=2086909");

app.Run();

3. 修正Nginx配置 #

调整请求路径匹配规则

原location /greet.Greeter仅匹配精确路径，但gRPC实际请求路径是/greet.Greeter/SayHello形式，需改为前缀匹配，并添加必要请求头传递：

server {
    root /var/www/vm2.arzval.com/html;
    server_name vm2.arzval.com;

    # 匹配gRPC服务的前缀路径
    location /greet.Greeter {
        grpc_pass grpc://127.0.0.1:5001;
        # 传递请求头到后端服务
        grpc_set_header Host $host;
        grpc_set_header X-Real-IP $remote_addr;
        grpc_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
    }

    listen [::]:443 ssl http2 ipv6only=on; # managed by Certbot
    listen 443 ssl http2; # managed by Certbot
    ssl_certificate /etc/letsencrypt/live/vm2.arzval.com/fullchain.pem; # managed by Certbot
    ssl_certificate_key /etc/letsencrypt/live/vm2.arzval.com/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 = vm2.arzval.com) {
        return 301 https://$host$request_uri;
    } # managed by Certbot

    listen 80;
    listen [::]:80;
    server_name vm2.arzval.com;
    return 404; # managed by Certbot
}

验证Nginx配置合法性

执行命令确保配置无语法错误：

sudo nginx -t

4. 重启服务生效 #

# 重启ASP.NET Core服务
sudo systemctl restart your-grpc-service-name

# 重启Nginx
sudo systemctl restart nginx

5. 日志排查（若问题仍存在） #

• 查看Nginx错误日志：/var/log/nginx/error.log
• 查看ASP.NET Core服务日志（systemd托管）：journalctl -u your-grpc-service-name -f

内容的提问来源于stack exchange，提问作者sam golpasha