[GH-ISSUE #90] Does support grpc ? #1398

New issue

Closed

opened 2026-02-27 12:10:22 +03:00 by kerem · 3 comments

kerem commented

2026-02-27 12:10:22 +03:00

Owner

Originally created by @UMUTBAYGUT on GitHub (Mar 13, 2023).
Original GitHub issue: https://github.com/0xJacky/nginx-ui/issues/90

Hello ,
does support grpc proxy ?
Can you show example if support ?

Originally created by @UMUTBAYGUT on GitHub (Mar 13, 2023). Original GitHub issue: https://github.com/0xJacky/nginx-ui/issues/90 Hello , does support grpc proxy ? Can you show example if support ?

kerem closed this issue

2026-02-27 12:10:22 +03:00

kerem commented

2026-02-27 12:10:22 +03:00

Author

Owner

@0xJacky commented on GitHub (Mar 13, 2023):

Do you mean the configuration template of grpc proxy?

@0xJacky commented on GitHub (Mar 13, 2023): Do you mean the configuration template of grpc proxy?

kerem commented

2026-02-27 12:10:22 +03:00

Author

Owner

@UMUTBAYGUT commented on GitHub (Mar 14, 2023):

Yes , can you show configuration template of grpc proxy ?

@UMUTBAYGUT commented on GitHub (Mar 14, 2023): Yes , can you show configuration template of grpc proxy ?

kerem commented

2026-02-27 12:10:22 +03:00

Author

Owner

@0xJacky commented on GitHub (Mar 14, 2023):

Here is an example of an nginx configuration template for a gRPC proxy:

http {
  upstream grpc_backend {
    server backend1:9000;
    server backend2:9000;
    server backend3:9000;
  }

  server {
    listen 80;
    server_name grpc.example.com;

    location / {
      grpc_pass grpc://grpc_backend;
      error_log /var/log/nginx/grpc.error.log;
      access_log /var/log/nginx/grpc.access.log;
      grpc_set_header Host $http_host;
      grpc_set_header X-Real-IP $remote_addr;
      grpc_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
      grpc_set_header X-Forwarded-Proto $scheme;
    }
  }
}

In this configuration, the upstream block defines the gRPC backend servers, and the server block defines the proxy server. The location block specifies that gRPC traffic should be passed to the backend servers via the grpc_pass directive, and sets various headers for the gRPC requests.

Note that this is just an example configuration, and you may need to modify it to suit your specific use case.

@0xJacky commented on GitHub (Mar 14, 2023): Here is an example of an nginx configuration template for a gRPC proxy: ``` http { upstream grpc_backend { server backend1:9000; server backend2:9000; server backend3:9000; } server { listen 80; server_name grpc.example.com; location / { grpc_pass grpc://grpc_backend; error_log /var/log/nginx/grpc.error.log; access_log /var/log/nginx/grpc.access.log; grpc_set_header Host $http_host; grpc_set_header X-Real-IP $remote_addr; grpc_set_header X-Forwarded-For $proxy_add_x_forwarded_for; grpc_set_header X-Forwarded-Proto $scheme; } } } ``` In this configuration, the upstream block defines the gRPC backend servers, and the server block defines the proxy server. The location block specifies that gRPC traffic should be passed to the backend servers via the grpc_pass directive, and sets various headers for the gRPC requests. Note that this is just an example configuration, and you may need to modify it to suit your specific use case.

kerem referenced this issue

2026-02-27 12:27:48 +03:00

[GH-ISSUE #1398] [Bug] Docker log keeps showing record not found #2838

kerem referenced this issue

2026-02-27 12:27:51 +03:00

[GH-ISSUE #1398] [Bug] Docker log keeps showing record not found #2840

kerem referenced this issue

2026-02-27 12:27:55 +03:00

[GH-ISSUE #1398] [Bug] Docker log keeps showing record not found #2843

kerem referenced this issue

2026-02-28 11:58:08 +03:00

[GH-ISSUE #1398] [Bug] Docker log keeps showing record not found #3879