HTTP/HTTPS: Reuse or merge port for API and Stream to avoid HTTP Proxy, to avoid proxy, it is recommended to reuse the port.

[winlinvip]

The SRS 4.0 HTTP API and Stream listen at different ports, so we must use a HTTP proxy if listen at a single HTTP or HTTPS port. Note that SRS 5.0 supports HTTP API and Stream listen at the same port, such as 8080.

Translation: Currently, the HTTP API and Stream design of SRS 4.0 are separate in order to support API listening on a separate port. However, in simple scenarios, it is inconvenient to use as it requires relying on an external HTTP proxy to combine the API and Stream on a single port.

Note: SRS 5.0 supports using the same port, such as 8080, for both HTTP API and Stream transmission, eliminating the need for a reverse proxy.

You could also use the default self-signed SSL certs, please search thisisunsafe from Wiki.

Ports

SRS 4.0 HTTP API ports:

• 1985 HTTP API
• 1990 HTTPS API

SRS 4.0 HTTP Stream ports:

• 8080 HTTP Stream
• 8088 HTTPS Stream

SRS 5.0 + HTTP API and Stream ports:

• 8080 HTTP API and Stream
• 8088 HTTPS API and Stream

Note: You can config http_api.listen to the same as http_server.listen, such as 8080.

Paths

• EN: https://ossrs.io/lts/en-us/docs/v6/doc/http-server#paths
• CN: https://ossrs.net/lts/zh-cn/docs/v6/doc/http-server#paths

Nginx Proxy

• EN: https://ossrs.io/lts/en-us/docs/v6/doc/http-server#nginx-proxy
• CN: https://ossrs.net/lts/zh-cn/docs/v6/doc/http-server#nginx-proxy

Caddy Proxy

• EN: https://ossrs.io/lts/en-us/docs/v6/doc/http-server#caddy-proxy
• CN: https://ossrs.net/lts/zh-cn/docs/v6/doc/http-server#caddy-proxy

Nodejs KOA Proxy

• EN: https://ossrs.io/lts/en-us/docs/v6/doc/http-server#nodejs-koa-proxy
• CN: https://ossrs.net/lts/zh-cn/docs/v6/doc/http-server#nodejs-koa-proxy

HTTPX Proxy

• EN: https://ossrs.io/lts/en-us/docs/v6/doc/http-server#httpx-proxy
• CN: https://ossrs.net/lts/zh-cn/docs/v6/doc/http-server#httpx-proxy

TRANS_BY_GPT3

[jonahzheng]

Caddy config

:80 {
  gzip
  reverse_proxy / localhost:8080 {
    header_up -Origin
  }
  reverse_proxy /api 127.0.0.1:1985/api/ {
    header_up -Origin
  }
  reverse_proxy /rtc 127.0.0.1:1985/rtc/ {
    header_up -Origin
  }
}

[winlinvip]

@jonahzheng What about HTTPS config like Nginx? Apart from HTTP proxy, I want to config the HTTPS with SSL key and cert file.

[finaldzn]

So i guess this config works if with an ingress and the https being done by the ingress router ?

[dwj1979]

On the console page, there is a connection that directly accesses port 1985, but the above nginx configuration file does not have a proxy listening on port 1985.

TRANS_BY_GPT3