Hi,
I dont really know when but Prowl seems to fail after sonarr has been running for awhile on my system…
Log says: Invalid API Key: "mylongboringapikey"
When I get this problem I just restart sonarr and Prowl messeges start sending out again fine.
I use Prowl for many services and in my own scripts and its only through sonarr Im experiencing this weird behaviour.
I have a friend who is also using Prowl with Sonarr and he started experience this issue around the same time as me.
Thanks for a great piece of software!
AN invalid API comes from Prowl’s API, either they are actually returning that or the Library Sonarr uses to connect to Prowl (Prowlin) is misinterpreting the response, that library hasn’t changed in years, but AFAIK the API hasn’t either.
We’ll need ((trace logs)) that include the failure and the version or Sonarr, operating system and mono version (if applicable) to investigate further.
Here is my log with tracelog enabled:
Component Message Time
NzbDroneErrorPipeline Invalid request Validation failed:
– Unable to send test message 08:33
ProwlService Unable to send test message: API Key: "myboringapikey"is invalid: API Key: “myboringapikey” is invalid 08:33
ProwlService Invalid API Key: “myboringapikey” 08:33
I can clearly read that it says my api key is invalid but the key isnt invalid, I use it for other programs/script and it always work if I just restart Sonarr.
Mono version:
mono version is 3.2 or better: 4.2.2
Sonarr version:
Latest 2.0.0.4326 - Sep 13 2016
OS: Synology DSM Latest.
Its not permitted to upload .txt logs to the forum so here it is in raw text, tried to remove my api key from below text.
[v2.0.0.4326] System.Net.WebException: The request timed out
at System.Net.HttpWebRequest.EndGetResponse (IAsyncResult asyncResult) [0x00065] in /home/bean/spksrc/native/mono/work-native/mono-4.2.2/mcs/class/System/System.Net/HttpWebRequest.cs:946
at System.Net.HttpWebRequest.GetResponse () [0x0000e] in /home/bean/spksrc/native/mono/work-native/mono-4.2.2/mcs/class/System/System.Net/HttpWebRequest.cs:958
at Prowlin.HttpInterface.GetResultDocument (System.Collections.Generic.Dictionary`2 parameters, System.String method, Prowlin.ResultBase resultBase) <0x41aea2b0 + 0x00047> in :0
at Prowlin.HttpInterface.SendVerification (IVerification verification) <0x41aea130 + 0x00067> in :0
at Prowlin.ProwlClient.SendVerification (IVerification verification) <0x41ae3040 + 0x00031> in :0
at NzbDrone.Core.Notifications.Prowl.ProwlService.Verify (System.String apiKey) [0x00023] in M:\BuildAgent\work\6c3239faf2b92630\src\NzbDrone.Core\Notifications\Prowl\ProwlService.cs:68
16-10-4 08:48:22.4|Warn|ProwlService|Invalid API Key: "myboringapikey"
16-10-4 08:48:22.4|Error|ProwlService|Unable to send test message: API Key: “myboringapikey” is invalid
[v2.0.0.4326] NzbDrone.Core.Notifications.Prowl.InvalidApiKeyException: API Key: “myboringapikey” is invalid
at NzbDrone.Core.Notifications.Prowl.ProwlService.Verify (System.String apiKey) [0x0008b] in M:\BuildAgent\work\6c3239faf2b92630\src\NzbDrone.Core\Notifications\Prowl\ProwlService.cs:80
at NzbDrone.Core.Notifications.Prowl.ProwlService.Test (NzbDrone.Core.Notifications.Prowl.ProwlSettings settings) [0x00000] in M:\BuildAgent\work\6c3239faf2b92630\src\NzbDrone.Core\Notifications\Prowl\ProwlService.cs:88
Been having the same issue since sometime this summer. Assume the logfile above will provide the lead you need, but I can run one too if you like. Thanks.