Kodi connect: Timeout

I recently got a Synology and running Sonarr on there now. But I can’t seem to get the Kodi connect to my Raspberry PI working for some reason.

Sonarr version (exact version): 2.0.0.5338
Mono version (if Sonarr is not running on Windows): 5.18.0.240
OS: Synology

These are my settings in Sonarr: screenshot

All I can see in the logs is this:

[Trace] Http: Req: 530 [PUT] /api/notification/1
[Trace] EventAggregator: Publishing ProviderUpdatedEvent<INotification>
[Trace] Http: Res: 530 [PUT] /api/notification/1: 202.Accepted (150 ms)
[Debug] Api: [PUT] /api/notification/1: 202.Accepted (150 ms)
[Trace] Http: Req: 531 [POST] /api/notification/test
[Debug] XbmcService: Determining version of Host: 193.168.1.15:8080
[Error] XbmcService: Unable to send test message

[v2.0.0.5338] System.Net.WebException: The operation has timed out.
  at NzbDrone.Core.Rest.RestSharpExtensions.ValidateResponse (RestSharp.IRestResponse response, RestSharp.IRestClient restClient) [0x00074] in <808631c82f974aa9ade775cc9d46232a>:0
  at NzbDrone.Core.Rest.RestSharpExtensions.ExecuteAndValidate (RestSharp.IRestClient client, RestSharp.IRestRequest request) [0x00007] in <808631c82f974aa9ade775cc9d46232a>:0
  at NzbDrone.Core.Notifications.Xbmc.XbmcJsonApiProxy.ProcessRequest (RestSharp.IRestRequest request, NzbDrone.Core.Notifications.Xbmc.XbmcSettings settings, System.String method, System.Collections.Generic.Dictionary`2[TKey,TValue] parameters) [0x00035] in <808631c82f974aa9ade775cc9d46232a>:0
  at NzbDrone.Core.Notifications.Xbmc.XbmcJsonApiProxy.GetJsonVersion (NzbDrone.Core.Notifications.Xbmc.XbmcSettings settings) [0x00006] in <808631c82f974aa9ade775cc9d46232a>:0
  at NzbDrone.Core.Notifications.Xbmc.XbmcService+<>c__DisplayClass8_0.<GetJsonVersion>b__0 () [0x00000] in <808631c82f974aa9ade775cc9d46232a>:0
  at NzbDrone.Common.Cache.Cached`1[T].Get (System.String key, System.Func`1[TResult] function, System.Nullable`1[T] lifeTime) [0x0006a] in <76bdc4530d5346bba006f54e6ddfeb8a>:0
  at NzbDrone.Core.Notifications.Xbmc.XbmcService.GetJsonVersion (NzbDrone.Core.Notifications.Xbmc.XbmcSettings settings) [0x00044] in <808631c82f974aa9ade775cc9d46232a>:0
  at NzbDrone.Core.Notifications.Xbmc.XbmcService.Test (NzbDrone.Core.Notifications.Xbmc.XbmcSettings settings, System.String message) [0x00021] in <808631c82f974aa9ade775cc9d46232a>:0

[Trace] NzbDroneErrorPipeline: Handling Exception
[Warn] NzbDroneErrorPipeline: Invalid request Validation failed:
 -- Unable to send test message
[Trace] Http: Res: 531 [POST] /api/notification/test: 400.BadRequest (100046 ms)
[Debug] Api: [POST] /api/notification/test: 400.BadRequest (100046 ms)

The webinterface works fine on: http://192.168.1.15:8080

Doing a direct JSON request from the console also seems to work fine:

Command:

curl -i -X POST                                                  \
>      -H 'Content-Type: application/json'                         \
>      -d '{"jsonrpc": "2.0","method": "JSONRPC.Version","id": 1}' \
>      http://192.168.1.15:8080/jsonrpc

Output:

HTTP/1.1 200 OK
Connection: Keep-Alive
Content-Length: 78
Content-Type: application/json
Cache-Control: private, max-age=0, no-cache
Accept-Ranges: none
Date: Thu, 21 Nov 2019 19:56:19 GMT

{"id":1,"jsonrpc":"2.0","result":{"version":{"major":10,"minor":3,"patch":0}}}

I tried doing it with a username and password and without. But I get the same results.
This worked fine when I was running sonarr on my pi as well, but now that it’s running on my Synology it just keeps timing out.

Could anyone tell me if I’m doing something wrong? Any help would be appreciated, thanks!

Don’t want to beat a dead horse, but is there anyone who could be able to help me with this? This keeps being a really annoying problem. Everytime new episodes have been added I need to update Kodi manually, while before it neatly did it automatically after every download.

I just can’t understand why Sonarr can’t connect to Kodi, while the server (Synology NAS) itself can do it.

Determining version of Host: 193.168.1.15:8080
The webinterface works fine on: http://192.168.1.15:8080

193 vs 192.

holy …
fucking …
hell …

God I’m an idiot! Thank you markus for taking the time to point out my stupidity!

1 Like

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.