Opened 3 years ago
Closed 3 years ago
#2218 closed enhancement (invalid)
Support RTMPS with non-standard ports
| Reported by: | Owned by: | ||
|---|---|---|---|
| Priority: | minor | Milestone: | |
| Component: | nginx-core | Version: | 1.19.x |
| Keywords: | Cc: | ||
| uname -a: | |||
| nginx -V: |
nginx version: nginx/1.14.0 (Ubuntu)
built with OpenSSL 1.1.1 11 Sep 2018 TLS SNI support enabled configure arguments: --with-cc-opt='-g -O2 -fdebug-prefix-map=/build/nginx-H4cN7P/nginx-1.14.0=. -fstack-protector-strong -Wformat -Werror=format-security -fPIC -Wdate-time -D_FORTIFY_SOURCE=2' --with-ld-opt='-Wl,-Bsymbolic-functions -Wl,-z,relro -Wl,-z,now -fPIC' --prefix=/usr/share/nginx --conf-path=/etc/nginx/nginx.conf --http-log-path=/var/log/nginx/access.log --error-log-path=/var/log/nginx/error.log --lock-path=/var/lock/nginx.lock --pid-path=/run/nginx.pid --modules-path=/usr/lib/nginx/modules --http-client-body-temp-path=/var/lib/nginx/body --http-fastcgi-temp-path=/var/lib/nginx/fastcgi --http-proxy-temp-path=/var/lib/nginx/proxy --http-scgi-temp-path=/var/lib/nginx/scgi --http-uwsgi-temp-path=/var/lib/nginx/uwsgi --with-debug --with-pcre-jit --with-http_ssl_module --with-http_stub_status_module --with-http_realip_module --with-http_auth_request_module --with-http_v2_module --with-http_dav_module --with-http_slice_module --with-threads --with-http_addition_module --with-http_geoip_module=dynamic --with-http_gunzip_module --with-http_gzip_static_module --with-http_image_filter_module=dynamic --with-http_sub_module --with-http_xslt_module=dynamic --with-stream=dynamic --with-stream_ssl_module --with-mail=dynamic --with-mail_ssl_module |
||
Description
When trying multi-broadcast an inbound RTMP toward outbound targets, Nginx has limitations related to non-standard ports used with RTMPS which are undermining the usability of Nginx for those situations.
Specifically, adding push URL for of the form rtmps://foo.bar.com:2935/qux in the nginx.conf file fails with the error message
nginx: [emerg] invalid port in url rtmps://foo.bar.com:2935/qux
Convoluted work-arounds are possible with Stunnel, but as the target URLs are changing the host as well for each video (LinkedIn does this), this approach is tedious.
Considering that all the major streaming platforms are migrating toward RTMPS and that adhoc ports will be frequent, it would be very nice if this was a supported scenario by Nginx.
By itself, nginx does not support RTMP. For feature requests in Roman Arutyunyan's nginx-rtmp module, consider using the module's own request tracker.