Also struggling to connect to this container

[themeatsweats]

Container is running fine, but no logs after a movie is recorded so I suspect I am not understanding either local/remote/relative paths here, or my port configuration is off (8080 is tied up with another service).

recent exec into my JF container:
root@a22f46a74b54:/config/scripts# curl -X POST http://localhost:8585/comskip curl: (7) Failed to connect to localhost port 8585 after 0 ms: Couldn't connect to server

Default recording path in JF is /data/DVR to match the mounted volume - /synology:/data/

Compose:

  comcutter:
    image: bljohnsondev/comcutter
    container_name: comcutter
    environment:
      - PUID=1000
      - PGID=1000
      - TZ=America/New_York
    ports:
      - 8585:8080
    volumes:
      - /storage/docker/comcutter:/data
      - /synology/DVR:/library
    restart: unless-stopped

config.yml:

api:
  apikey: 9fa085afa57c4eddfc0f # replace this with your own generated key
  log_dir: "/data/logs"
  log_level: "debug"
  library_dir: "/library"
  port: 8080

comskip:
  comskip_cmd: "/usr/local/bin/comskip"
  comskip_ini: "/data/config/comskip.ini"
  cmd: "/usr/local/bin/comcut"
  keep_edl: true
  timeout: 300
  size_percentage: 0.7

Postprocess script (mounted in JF container at /config/scripts/jellyfin-drv-comskip.sh):

#!/bin/bash

filepath="$@"

# example file - '/data/media/dvr/Family Guy/Season 22/Family Guy S22E05 Old World Harm.ts'
stripped=`echo "$filepath" | cut -c 9-`

curl -X POST \
  http://localhost:8585/comskip \
  -H 'Content-Type: application/json' \
  -d "{\"api\": \"9fa085afa57c4eddfc0f\", \"file\": \"${stripped}\"}"

[bljohnsondev]

If I’m reading this correctly, this could be because “localhost” in your Jellyfin container is the JF container itself and not the exposed port 8585 for the comcutter container. If you’re running them on the same machine you could add the comcutter service to your Jellyfin docker-compose file. That way they’ll both be in the same Docker network. Then you can access it from JF with http://comcutter:8080/comskip and no need to expose a port for comcutter at all.

[themeatsweats]

Thanks. After playing with it a bit more this morning, I've narrowed it down to a volume issue. When I force the script in my JF container, I get an error in the console with a similar error in the comcutter logs: 11-20-2025 12:59:42 PM - WARNING : [172.18.0.1] could not open file: /data/DVR/Beast (2022)/Beast (2022).ts

Somewhere between the compose volume mounts, the config.yml and the script there is a disconnect

[bljohnsondev]

Weird. So your error message says this:

11-20-2025 12:59:42 PM - WARNING : [172.18.0.1] could not open file: /data/DVR/Beast (2022)/Beast (2022).ts

Did you change your config.yml file from the version you originally posted? It looks like you changed api.library_dir to /data/DVR, possibly?

It's trying to find your media file in /data/DVR but according to your comcutter compose file above you're mounting your media library to /library. You should be fine with setting api.library_dir to /library.

[themeatsweats]

No, I've monkeyed with volumes and the script a bit, but haven't touched the config file. Is it possible that setting the record path changes how JF is reporting the file path?

[bljohnsondev]

Sorry for the delay. Jellyfin should be sending the full path to the media that was recorded (including /data/DVR/...).

Basically the script just needs to strip out /data/DVR when sending the file path string over to your comcutter container. It will then look for the file in "/library" (the api.library_dir config setting). So Jellyfin will pass this to the script:

"/data/DVR/Beast (2022)/Beast (2022).ts"

The script should strip the "/data/DVR" and only send "/Beast (2022)/Beast (2022).ts" to comcutter. It will then look for "/library/Beast (2022)/Beast (2022).ts".

You could modify the script (and not have to math it) like this:

#!/bin/bash

filepath="$@"

jellyfinvol="/data/DVR"
stripped="${filepath##$jellyfinvol}"

curl -X POST \
  http://localhost:8080/comskip \
  -H 'Content-Type: application/json' \
  -d "{\"api\": \"YOUR_GENERATED_API_KEY\", \"file\": \"${stripped}\"}"

I am confused by the comcutter logs based on the configuration you provided, though. The error message is this?
could not open file: /data/DVR/Beast (2022)/Beast (2022).ts

It should be trying to open the file based on the config.yaml api.library_dir setting. So if it's set to "/library" it should be looking for your file in "/library/Beast (2022)/Beast (2022).ts".

I know it's a bit confusing but it's built this way because I run comcutter on a separate VM/machine than the one Jellyfin runs on. Because I can't guarantee the volume mounts will match, and because Jellyfin sends the full absolute path, some extra work has to be done to account for it.