# Custom streaming zoom

**URL:** <https://devforum.zoom.us/t/custom-streaming-zoom/138689>\
**Category:** API and Webhooks\
**Created:** [November 13, 2025, 12:05pm UTC](https://devforum.zoom.us/t/custom-streaming-zoom/138689 "2025-11-13T12:05:26Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![sanket](https://avatars.discourse-cdn.com/v4/letter/s/57b2e6/32.png) [@sanket](https://devforum.zoom.us/u/sanket)\
**Post date:** [November 13, 2025, 12:05pm UTC](https://devforum.zoom.us/t/custom-streaming-zoom/138689/1 "2025-11-13T12:05:26Z")

</div>

**Title:** Unable to live stream to custom RTMP server (Connection Refused)

We’re trying to stream a Zoom meeting to our custom NGINX RTMP server hosted at `rtmp://content-sandbox-studentzone-ncdoe.nmims.edu/live/zoom`. The RTMP service is running, port **1935** is open, and we can stream locally using FFmpeg.

However, Zoom fails with the message:

> “Unable to live stream to the custom service.”

Could Zoom confirm if RTMPS (SSL) is now mandatory or if there are any known issues with NGINX RTMP for custom streaming? Any guidance would be appreciated.

---

<div class="post-metadata">

**Author:** ![amanda-recallai](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/amanda-recallai/32/44747_2.png) [@amanda-recallai](https://devforum.zoom.us/u/amanda-recallai)\
**Post date:** [November 13, 2025, 5:13pm UTC](https://devforum.zoom.us/t/custom-streaming-zoom/138689/2 "2025-11-13T17:13:14Z")

</div>

Hi @Sanket, [while Zoom supports RTMPs](https://support.zoom.com/hc/en/article?id=zm_kb&sysparm_article=KB0077038), Zoom still also streams out [over plain RTMP streams](https://devforum.zoom.us/t/live-streaming-with-rtmp/63328) and the docs for [livestreaming meetings or webinars on a custom site](https://support.zoom.com/hc/en/article?id=zm_kb&sysparm_article=KB0064210) do not specify/require RTMPS, so SSL should not be mandatory here

That specific Zoom error usually means the meeting client cannot reach your RTMP endpoint or the URL/key are split wrong so you should double check that port 1935 on that host is publicly reachable from the internet rather than only inside your network