whip connection does not work

I'm trying to use WHIP instead of RTMP (RTMP works fine) but after accepting the connection the connection drops.

Config

logging:
  level: debug
redis:
    address: localhost:6379
api_key: *******
api_secret: *******
ws_url: wss://MY.URL
rtmp_port: 1935
whip_port: 8080
http_relay_port: 9090

rtc_config:
  tcp_port: 7882 # 7881 - already in use
  udp_port: 7885
  use_external_ip: false

[biglittlebigben]

Could you provide some more details, such as ingress, livekit-server and OBS logs?

Thanks,

[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/go-rtmp@v0.0.0-20230829211117-1c4f5a5c81ed/server_conn.go:31\ngithub.com/livekit/go-rtmp.(*Server).handleConn\n\t/root/go/pkg/mod/github.com/livekit/go-rtmp@v0.0.0-20230829211117-1c4f5a5c81ed/server.go:116\nruntime.goexit\n\t/root/go/pkg/mod/golang.org/toolchain@v0.0.1-go1.23.4.linux-amd64/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 RTMP session	{"nodeID": "NE_qoo9YkszSbUn"}

livekit-server:

livekit-server 2025-02-06T22:41:05.553Z INFO    livekit rtc/room.go:469 participant active      {"room": "f5826762-8621-4442-9ab4-4d418a36eb79", "roomID": "RM_aNEBtU8WESfz", "participant": "70104df9-1d78-4cd2-95e7-db19b889a2a8", "pID": "PA_giwewUyiVQjR", "remote": false, "publisherCandidates": ["[local][selected:7][trickle] udp4 host 207.5.196.134:53450 (resolved: 207.5.196.134:53450)", "[local][trickle] tcp4 host 207.5.196.134:7881 (resolved: 207.5.196.134:7881)", "[remote][trickle] udp4 host 192.168.0.4:53996", "[remote][trickle] udp4 host 192.168.0.5:58552", "[remote][trickle] tcp4 host 192.168.0.4:9", "[remote][trickle] tcp4 host 192.168.0.5:9", "[remote][trickle] udp4 srflx 71.36.37....:53996  related 192.168.0.4:53996", "[remote][trickle] udp4 relay 207.5.196....:33750  related 207.5.196....:33750", "[remote][selected:7][trickle] udp4 prflx 71.36.37....:53996", "[remote][selected:6][trickle] udp4 prflx 71.36.37....:58552", "[remote][trickle] udp4 srflx 71.36.37....:58552  related 192.168.0.5:58552", "[remote][trickle] udp4 relay 207.5.196....:30201  related 207.5.196....:30201"], "subscriberCandidates": ["[local][trickle] tcp4 host 207.5.196.134:7881 (resolved: 207.5.196.134:7881)", "[local][selected:1][trickle] udp4 host 207.5.196.134:51252 (resolved: 207.5.196.134:51252)", "[remote][trickle] udp4 host 192.168.0.4:51767", "[remote][trickle] udp4 host 192.168.0.5:59625", "[remote][trickle] tcp4 host 192.168.0.4:9", "[remote][trickle] tcp4 host 192.168.0.5:9", "[remote][trickle] udp4 srflx 71.36.37....:51767  related 192.168.0.4:51767", "[remote][trickle] udp4 relay 207.5.196....:37354  related 207.5.196....:37354", "[remote][trickle] udp4 srflx 71.36.37....:59625  related 192.168.0.5:59625", "[remote][trickle] udp4 relay 207.5.196....:31175  related 207.5.196....:31175", "[remote][selected:1][trickle] udp4 prflx 71.36.37....:51767"], "connectionType": "udp"}
livekit-server 2025-02-06T22:41:05.640Z INFO    livekit.webhook webhook/url_notifier.go:124     sent webhook    {"event": "participant_joined", "id": "EV_nQgnBkRjunxG", "webhookTime": 1738881665, "room": "f5826762-8621-4442-9ab4-4d418a36eb79", "roomID": "RM_aNEBtU8WESfz", "participant": "70104df9-1d78-4cd2-95e7-db19b889a2a8", "pID": "PA_giwewUyiVQjR", "url": "https://api.studio.rumble.com/core/livekit/webhook-endpoint", "queueDuration": "17.84µs", "sendDuration": "86.848891ms"}
livekit-server 2025-02-06T22:41:03.063Z INFO    livekit service/roomallocator.go:164    selected node for room  {"room": "f5826762-8621-4442-9ab4-4d418a36eb79", "selectedNodeID": "ND_vYK43TWQR8G8"}
livekit-server 2025-02-06T22:41:03.066Z INFO    livekit.api     service/twirp.go:124    API RoomService.CreateRoom      {"service": "RoomService", "method": "CreateRoom", "room": "f5826762-8621-4442-9ab4-4d418a36eb79", "request": {"name": "f5826762-8621-4442-9ab4-4d418a36eb79", "maxParticipants": 15}, "duration": "3.886839ms", "status": "200"}
livekit-server 2025-02-06T22:41:12.421Z INFO    livekit.api     service/twirp.go:124    API Ingress.ListIngress {"service": "Ingress", "method": "ListIngress", "room": "f5826762-8621-4442-9ab4-4d418a36eb79", "duration": "456.853µs", "status": "200"}
livekit-server 2025-02-06T22:41:08.404Z INFO    livekit.api     service/twirp.go:124    API Ingress.ListIngress {"service": "Ingress", "method": "ListIngress", "room": "f5826762-8621-4442-9ab4-4d418a36eb79", "duration": "845.516µs", "status": "200"}
livekit-server 2025-02-06T22:41:12.432Z INFO    livekit.api     service/twirp.go:124    API Ingress.CreateIngress       {"service": "Ingress", "method": "CreateIngress", "inputType": "WHIP_INPUT", "name": "asdf", "room": "f5826762-8621-4442-9ab4-4d418a36eb79", "identity": "RTMP_PARTICIPANT:5f9b29c9-e3e7-4b27-afe3-60bba23adfff", "ingressID": "IN_JqeGwhkJ9xpB", "duration": "2.076035ms", "status": "200"}

OBS:

OBS logs give a hit that livekit might be communicating with HTTP/0.9 which is EOL and operation systems and programs are dropping support.

[biglittlebigben]

CreateIngress and OBS indicate a WHIP session, but the ingress logs indicate that you are trying to connect to the RTMP port. Please check your OBS settings and the network/load balancer configuration on your server.

[James-Whitney]

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. My investigation began from user reports of WHIP ingest no connecting to the server.

grepping through the logs, i can't find any log line matching my test ingress id, name, stream key, nothing.

[docisit]

Im having issues making a connection with an Ice or Stun Server. Rtmp works great,. Ingress was working great when I was just pushing a feed to my server, and letting Egress grab it and push it on to my social platfroms. But now, i am trying to use Ingress to push as host to a room with OBS. My Obs Virtual Cam works great, but I know Ingress would be better for this