Unable to RTMP push to other platforms

[TheTurkeyDev]

I'm attempting to use push publishing to send my stream to other platforms but I'm encountering errors starting the push publish. I am using the latest dev version of the docker container

Application Providers & Publishers

<Providers>
        <RTMP />
</Providers>
<Publishers>
        <AppWorkerCount>1</AppWorkerCount>
        <StreamWorkerCount>8</StreamWorkerCount>
        <Push>
        </Push>
</Publishers>

I've replaced my actual stream key with streamKey in the below outputs

I'm utilizing the API to start these pushes using

{
  "id": "push_1_4",
  "stream": {
    "name": "1",
    "variantNames": []
  },
  "protocol": "rtmp",
  "url": "rtmp://a.rtmp.youtube.com/live2",
  "streamKey": "streamKey"
}

Relevant debug log:

[2025-02-24 15:52:56.042] D [PushSessionCtrl:15] FFmpeg | third_parties.cpp:127  | [URLContext: 0x7f6f37c2a300] Address 172.217.4.76 port 1935
[2025-02-24 15:52:56.042] D [PushSessionCtrl:15] FFmpeg | third_parties.cpp:127  | [URLContext: 0x7f6f37c2a300] Address 142.250.190.12 port 1935
[2025-02-24 15:52:56.042] D [PushSessionCtrl:15] FFmpeg | third_parties.cpp:127  | [URLContext: 0x7f6f37c2a300] Address 142.250.190.140 port 1935
[2025-02-24 15:52:56.042] D [PushSessionCtrl:15] FFmpeg | third_parties.cpp:127  | [URLContext: 0x7f6f37c2a300] Starting connection attempt to 142.250.191.140 port 1935
[2025-02-24 15:52:56.042] E [PushSessionCtrl:15] FFmpegWriter | ffmpeg_writer.cpp:58   | connection timeout occurred. stop the writer. 5000 milliseconds. 
[2025-02-24 15:52:56.042] E [PushSessionCtrl:15] FFmpeg | third_parties.cpp:113  | [URLContext: 0x7f6f37c2a240] Cannot open connection tcp://a.rtmp.youtube.com:1935?tcp_nodelay=0
[2025-02-24 15:52:56.042] E [PushSessionCtrl:15] FFmpegWriter | ffmpeg_writer.cpp:188  | Error opening file. error(Immediate exit requested), url(rtmp://a.rtmp.youtube.com/live2/streamKey)
[2025-02-24 15:52:56.073] D [FLT-rsmp-t2:25] FFmpeg | third_parties.cpp:127  | [AVFilter: 0x7f6f31a13180] tb:1/1000 pts:26192 -> tb:1/48000 pts:1257216
[2025-02-24 15:52:56.073] D [FLT-rsmp-t2:25] FFmpeg | third_parties.cpp:127  | [AVFilter: 0x7f6f31a13180] tb:1/1000 pts:26215 -> tb:1/48000 pts:1258320
[2025-02-24 15:52:56.105] D [FLT-rsmp-t2:25] FFmpeg | third_parties.cpp:127  | [AVFilter: 0x7f6f31a13180] tb:1/1000 pts:26238 -> tb:1/48000 pts:1259424
[2025-02-24 15:52:56.105] D [FLT-rsmp-t2:25] FFmpeg | third_parties.cpp:127  | [AVFilter: 0x7f6f31a13180] tb:1/1000 pts:26262 -> tb:1/48000 pts:1260576
[2025-02-24 15:52:56.143] I [PushSessionCtrl:15] Push | push_application.cpp:233  | Push started. uid(push_1_4) vhost(default) app(live) stream(1) -> protocol(rtmp) url(rtmp://a.rtmp.youtube.com/live2) streamKey(streamKey)
[2025-02-24 15:52:56.143] D [PushSessionCtrl:15] FFmpeg | third_parties.cpp:127  | [URLContext: 0x7f6f37c2a240] No default whitelist set
[2025-02-24 15:52:56.143] D [PushSessionCtrl:15] FFmpeg | third_parties.cpp:127  | [URLContext: 0x7f6f37c2a300] No default whitelist set
[2025-02-24 15:52:56.150] D [FLT-rsmp-t2:25] FFmpeg | third_parties.cpp:127  | [AVFilter: 0x7f6f31a13180] tb:1/1000 pts:26285 -> tb:1/48000 pts:1261680
[2025-02-24 15:52:56.183] D [FLT-rsmp-t2:25] FFmpeg | third_parties.cpp:127  | [AVFilter: 0x7f6f31a13180] tb:1/1000 pts:26308 -> tb:1/48000 pts:1262784

I am able to stream directly to YouTube with the same information taking out OME

[bchah]

Try using <RTMPPush /> in your application publisher.

[bchah]

Huh, looks like you're right - the arguments are indeed interchangeable.

Based on the FFmpeg error it seems like it isn't able to communicate with the YouTube server, even though the IP does get resolved. Can you try pushing to a local IP, perhaps another instance of OME?

[TheTurkeyDev]

That actually works. A url of rtmp://192.168.0.200:1935 which is the IP of the same machine, different OME instance worked. I agree it did seem to resolve the IP for YouTube, but then was not able to start the stream?

[TheTurkeyDev]

I am able to stream from that machine to YouTube using ffmpeg in the cli, so it's not something with that machine. It's either OME or docker?

[TheTurkeyDev]

Seems it was some sort of weird DNS thing and the ip's were just being resolved too slowly. Forcing the DNS server on the container fixes the issue