Can't get gotify to work with Jellyfin (docker)

[User 3911]

I am using Gotify for some bash scripts and Uptime Kuma, Works great. I noticed I could also use it with Jellyfin so I wanted to give it a go. Just like Uptime Kuma and Gotify itself I use a docker container for Jellyfin, same homelab. All behind Ngnix Proxy Manager, However Gotify does not recieve a single message and I can't figure out why not. Token and url are correct. There is not much that go wrong really Anyone an idea how to fix this?

Code:

version: "3.5"
services:
  jellyfin:
    image: jellyfin/jellyfin
    container_name: jellyfin
    network_mode: "host"
    group_add:
      - "110"
    volumes:
      - /srv/jellyfin/config:/config
      - /srv/jellyfin/cache:/cache
      - /media:/media
    devices:
      - /dev/dri/renderD128:/dev/dri/renderD128
    restart: "always"
    # Optional - alternative address used for autodiscovery
    environment:
      - JELLYFIN_PublishedServerUrl=https://domain.com

Version: 10.8.12
Operating System: Linux
Architecture: X64

[tmsrxzar]

i can't say i know anything about gotify but..

this is incorrect JELLYFIN_PublishedServerUrl=https://domain.com

that will broadcast to clients that jellyfin is serving from "https://domain.com" and i am positive you do not own that domain

needs to be JELLYFIN_PublishedServerUrl=http://jfserver:8096

if gotify is using the broadcasted url ^^^ then that's why it's failing

[User 3911]

i can't say i know anything about gotify but..

this is incorrect JELLYFIN_PublishedServerUrl=https://domain.com

that will broadcast to clients that jellyfin is serving from "https://domain.com" and i am positive you do not own that domain

needs to be JELLYFIN_PublishedServerUrl=http://jfserver:8096

if gotify is using the broadcasted url ^^^ then that's why it's failing

You are absolutely right, I just didn't want to publish my actual domain on a forum

[tmsrxzar]

ah then i have a suggestion; when redacting urls don't use ones that people looking for mistakes are going to think are done by mistake

(i deal with/have dealt with some ... "not technological people" and nothing really surprises me)

[User 3911]

ah then i have a suggestion; when redacting urls don't use ones that people looking for mistakes are going to think are done by mistake

(i deal with/have dealt with some ... "not technological people" and nothing really surprises me)

Fair point