I am unable to get kick.com to work as a custom platform in the json config

[successtheman]

Below is the contents of my json config file with the stream keys removed, however when I try to start the docker container (I am using podman but it should not matter) it throws these errors (shown in the pastebin paste)

https://pastebin.com/QzsjAbwh

{
  "endpoint": "live",
  "transcodeProfiles": {
    "936_60fps": {
      "pixels": "1664x936",
      "videoBitRate": "6000k",
      "videoFrameRate": 60,
      "videoKeyFrameSecs": 2,
      "audioBitRate": "320k",
      "audioSampleRate": "48000"
    }
  },
  "rebroadcastList": [
    {
      "name": "twitch",
      "platform": "twitch",
      "streamKey": "STREAMKEY",
      "transcodeProfile": "936_60fps"
    },
    {
      "name": "kick",
      "platform": "custom",
      "fullRTMPURL": "rtmps://fa723fc1b171.global-contribute.live-video.net/STREAMKEY",
      "transcodeProfile": "936_60fps"
    }
  ]
}

[successtheman]

I am not sure if the kick URL should be the way I have it or rtmps://fa723fc1b171.global-contribute.live-video.net/app/streamkey (the first one here still has the same error), but I also saw rtmps://fa723fc1b171.global-contribute.live-video.net/kick/streamkey suggested on their discord server. Either way I asked a question in their discord to see if I can figure it out.

I think the issue might be that it's a custom RTMPS URL but I am not sure. It probably shouldn't matter if the URL is valid or not regardless since the example ones don't throw errors and they are random characters. It works fine for twitch without kick in my config

[successtheman]

managed to get it working using this instead https://hub.docker.com/r/thiagoeolima/nginx-rtmps/

[successtheman]

For future reference the only format that worked was rtmps://fa723fc1b171.global-contribute.live-video.net/kick/streamkey

[michaelkamprath]

Glad you got things working for yourself. I haven't used this for a while myself, and it would seem Twitch has changed their URL format. With this project, you can always used the custom URL destination rather than the currently implemented twitch support as the code here currently uses the old (pre-2022?) twitch stream ingest. If I get time I will update things, but someone is always welcome to create a PR too, as this is open source after all.