Connect - Notifications to Jellyfin broken since Jellyfin update

[bonswouar]

Is there an existing issue for this?

• I have searched the existing open and closed issues

Current Behavior

When the notification to Jellyfin is sent an error is returned (see log attached), and the status becomes "Notifications unavailable due to failures: Jellyfin"

Expected Behavior

Notifications to Jellyfin should work

Steps To Reproduce

1. Update Jellyfin server to 10.9.0 or 10.9.1
2. Send a notification from Radarr to Jellyfin (for example when a movie is added)
3. See status/error (side-note: it seems when using the "Test" button from "Edit Notification - Emby / Jellyfin", the 404 isn't considered as an error, the checkmark is green but the error is still in the logs as a warning)

Environment

- OS: Debian 12
- Radarr: 5.5.3.8819
- Docker Install: Yes
- Using Reverse Proxy: Yes
- Database: Sqlite 3.44.2

What branch are you running?

Master

Trace Logs? Not Optional

2024-05-15 12:05:56.2|Warn|HttpClient|HTTP Error - Res: HTTP/1.1 [POST] http://jellyfin_host:8096/mediabrowser/Notifications/Admin: 404.NotFound (0 bytes)
2024-05-15 12:05:56.2|Warn|NotificationService|Unable to send OnDownload notification to: Jellyfin

[v5.5.3.8819] NzbDrone.Common.Http.HttpException: HTTP request failed: [404:NotFound] [POST] at [http://jellyfin_host:8096/mediabrowser/Notifications/Admin]
   at NzbDrone.Common.Http.HttpClient.ExecuteAsync(HttpRequest request) in ./Radarr.Common/Http/HttpClient.cs:line 119
   at NzbDrone.Common.Http.HttpClient.Post(HttpRequest request) in ./Radarr.Common/Http/HttpClient.cs:line 363
   at NzbDrone.Core.Notifications.Emby.MediaBrowserProxy.ProcessRequest(HttpRequest request, MediaBrowserSettings settings) in ./Radarr.Core/Notifications/MediaBrowser/MediaBrowserProxy.cs:line 59
   at NzbDrone.Core.Notifications.Emby.MediaBrowserProxy.Notify(MediaBrowserSettings settings, String title, String message) in ./Radarr.Core/Notifications/MediaBrowser/MediaBrowserProxy.cs:line 31
   at NzbDrone.Core.Notifications.Emby.MediaBrowserService.Notify(MediaBrowserSettings settings, String title, String message) in ./Radarr.Core/Notifications/MediaBrowser/MediaBrowserService.cs:line 34
   at NzbDrone.Core.Notifications.Emby.MediaBrowser.OnDownload(DownloadMessage message) in ./Radarr.Core/Notifications/MediaBrowser/MediaBrowser.cs:line 33
   at NzbDrone.Core.Notifications.NotificationService.Handle(MovieFileImportedEvent message) in ./Radarr.Core/Notifications/NotificationService.cs:line 157

Trace Logs have been provided as applicable. Reports will be closed if the required logs are not provided.

• I have read and followed the steps in the wiki link above and provided the required trace logs - the logs contain trace - that are relevant and show this issue.

[tordenflesk]

I'm experiencing the same issue with Sonarr as well.

[bonswouar]

Related to jellyfin/jellyfin#1681

[Theetjuh]

Same issue here, just noticed the error.

[ddalben]

Also seeing it from both Sonarr and Radarr

[gaalma]

also experiencing the described behaviour in both Sonarr and Radarr

[jstewart612]

Did some digging.

I think it happened here:

• Remove unused notification endpoints jellyfin/jellyfin#8952
• Remove Emby.Notifications jellyfin/jellyfin#9147

Based on: Sonarr/Sonarr#5828

The closing, it seems, was without proper resolution. Hence, why we are here now: because 9147 seems to have hit on 10.9.3: