OBS - Failed to connect to server when running in docker

Hello,

I’ve been trying for a couple of hours to set up nodetube on my local machine (just to test it out) via docker-compose. I’ve added an extra port for the nodetube container “1935:1935” because I care more about the live streaming aspect of this project, Unfortunately, I couldn’t connect to the live-stream via OBS. Every time I try to start the stream I get the message “Failed to connect to server”.

I went to settings and made sure that I have the right link:

Server:  rtmp://127.0.0.1:1935/live
Stream Key:  /test?key=<my key>

I’ve also looked in the OBS logs and saw this:

14:33:55.946: ------------------------------------------------
14:33:58.007: [rtmp stream: 'simple_stream'] Connecting to RTMP URL rtmp://127.0.0.1:1935/live...
14:33:58.008: [rtmp stream: 'simple_stream'] Interface: Software Loopback Interface 1 (type 24, 1073 mbps)
14:33:58.013: RTMPSockBuf_Fill, remote host closed connection
14:33:58.013: RTMP_Connect1, handshake failed.
14:33:58.013: [rtmp stream: 'simple_stream'] Connection to rtmp://127.0.0.1:1935/live failed: -2
14:33:58.022: ==== Streaming Stop ================================================

I couldn’t see anything in the nodetube container logs (nothing showed up other than the “normal” logs, no errors or warnings).

Could you point out what I’m doing wrong? Thank you very much!

Details about my system: Windows 10 Pro Server: Docker Engine - Community Engine: Version: 20.10.2

[l1ghtsword]

I plan on it, its a little more complicated then adding a ngnix-rtmp docker container because nodetube expects the stream to be a readable file being created in uploads… Ill see what i can do to remedy that design.

EDIT: very incorrect. the content from HLS is forwarded to the nodetube service directly and authenticated there. recordings is its own directory and separate from uploads entirely.

[l1ghtsword]

You would need to run it once to have it copy them to the local directory for you. a word of caution, i would advise against changing the env.sample files and instead simply copy and paste them into the root directory and remove the “.sample” at the end.

That way you have a clean reffernce in the event something breaks due to a setting change. Also, env.sample files are subject to change (and get overwritten) as they are template files observed by git. .gitignore only ignores non sample files with the expectation api keys or private settings are in there…

Glad to hear this issue is resolved though, thanks for confirming.