James Whitney

Experiencing a similar issue Ingress: ``` livekit-ingress-6d6b899b7f-2588t ingress time="2025-02-06T22:53:54Z" level=info msg="Server closed by error: Err = unexpected EOF\nFailed to handshake\ngithub.com/livekit/go-rtmp.(*serverConn).Serve\n\t/root/go/pkg/mod/github.com/livekit/[email protected]/server_conn.go:31\ngithub.com/livekit/go-rtmp.(*Server).handleConn\n\t/root/go/pkg/mod/github.com/livekit/[email protected]/server.go:116\nruntime.goexit\n\t/root/go/pkg/mod/golang.org/[email protected]/src/runtime/asm_amd64.s:1700" logger=ingress nodeID=NE_qoo9YkszSbUn livekit-ingress-6d6b899b7f-2588t ingress 2025-02-06T22:53:54.806Z INFO ingress rtmp/server.go:355 closing ingress...

I'll double check, I may have grabbed the incorrect ingress log line, I've got roughly 30 ingresses running a mix of RTMP and WHIP, so the logs are very noisy....

I'm also seeing this issue, > I don't think MaxConnectedUsers higher than 40 is supported so maybe that's it? Try changing it to 40. My config has 40 set, so...

i can confirm this is the issue, you can edit your continue settings which was located here for me: `"C:\Program Files (x86)\Steam\userdata\MY_STEAM_ID\1604030\remote\v3\ServerHistory.json"` my server's IP was listed as `0.0.0.0`, setting...

I've tried a build with `RUN apt install -y openssl iproute2 ca-certificates` added without success, if you have a working Dockerfile or built image I'd be happy to test it...

> > I've tried a build with `RUN apt install -y openssl iproute2 ca-certificates` added without success, if you have a working Dockerfile or built image I'd be happy to...

Actually, I don't think it fixed the issue, i just got lucky when the server started up correctly several times in a row. Other than the UDP default, another difference...