JSON Error with SAB

I’m getting the same error but have something different in my logs. Any help would be greatly appreciated. Not sure if this is corruption in the DB, a bad filename that can’t be handled or something else:

Newtonsoft.Json.JsonReaderException: Unexpected character encountered while parsing value: T. Path ‘’, line 0, position 0.
at Newtonsoft.Json.JsonTextReader.ParseValue()
at Newtonsoft.Json.JsonTextReader.ReadInternal()
at Newtonsoft.Json.JsonTextReader.Read()
at Newtonsoft.Json.Serialization.JsonSerializerInternalReader.ReadForType(JsonReader reader, JsonContract contract, Boolean hasConverter)
at Newtonsoft.Json.Serialization.JsonSerializerInternalReader.Deserialize(JsonReader reader, Type objectType, Boolean checkAdditionalContent)
at Newtonsoft.Json.JsonSerializer.DeserializeInternal(JsonReader reader, Type objectType)
at Newtonsoft.Json.JsonConvert.DeserializeObject(String value, Type type, JsonSerializerSettings settings)
at Newtonsoft.Json.JsonConvert.DeserializeObject[T](String value, JsonSerializerSettings settings)
at NzbDrone.Core.Download.Clients.Sabnzbd.SabnzbdProxy.GetConfig(SabnzbdSettings settings) in m:\BuildAgent\work\6c3239faf2b92630\src\NzbDrone.Core\Download\Clients\Sabnzbd\SabnzbdProxy.cs:line 92
at NzbDrone.Core.Download.Clients.Sabnzbd.Sabnzbd.GetStatus() in m:\BuildAgent\work\6c3239faf2b92630\src\NzbDrone.Core\Download\Clients\Sabnzbd\Sabnzbd.cs:line 315
at NzbDrone.Core.HealthCheck.Checks.ImportMechanismCheck.b__0(IDownloadClient v) in m:\BuildAgent\work\6c3239faf2b92630\src\NzbDrone.Core\HealthCheck\Checks\ImportMechanismCheck.cs:line 29
at System.Linq.Enumerable.WhereSelectListIterator2.MoveNext() at System.Collections.Generic.List1…ctor(IEnumerable1 collection) at System.Linq.Enumerable.ToList[TSource](IEnumerable1 source)
at NzbDrone.Core.HealthCheck.Checks.ImportMechanismCheck.Check() in m:\BuildAgent\work\6c3239faf2b92630\src\NzbDrone.Core\HealthCheck\Checks\ImportMechanismCheck.cs:line 29
at NzbDrone.Core.HealthCheck.HealthCheckService.b__0(IProvideHealthCheck c) in m:\BuildAgent\work\6c3239faf2b92630\src\NzbDrone.Core\HealthCheck\HealthCheckService.cs:line 57
at System.Linq.Enumerable.WhereSelectEnumerableIterator2.MoveNext() at System.Collections.Generic.List1…ctor(IEnumerable1 collection) at System.Linq.Enumerable.ToList[TSource](IEnumerable1 source)
at NzbDrone.Core.HealthCheck.HealthCheckService.PerformHealthCheck(Func2 predicate) in m:\BuildAgent\work\6c3239faf2b92630\src\NzbDrone.Core\HealthCheck\HealthCheckService.cs:line 56 at NzbDrone.Core.HealthCheck.HealthCheckService.HandleAsync(ApplicationStartedEvent message) in m:\BuildAgent\work\6c3239faf2b92630\src\NzbDrone.Core\HealthCheck\HealthCheckService.cs:line 93 at NzbDrone.Core.Messaging.Events.EventAggregator.<>c__DisplayClass31.b__0() in m:\BuildAgent\work\6c3239faf2b92630\src\NzbDrone.Core\Messaging\Events\EventAggregator.cs:line 72
at System.Threading.Tasks.Task.InnerInvoke()
at System.Threading.Tasks.Task.Execute()

Please don’t necro threads, you have the option to reply as a linked topic if you feel its related.

Which version of Sonarr?
Which version of SAB?

This appears to be a problem with your SAB configuration (Sonarr is attempting to validate it), if you enable [trace logging] (https://github.com/Sonarr/Sonarr/wiki/Log-Files) and pastebin the result of a test of SAB from Sonarr (in settings) it should give us something more to go on.

OK, thanks. I couldn’t decipher that error, but amazingly that’s all that I needed to know to fix it The port that Sonarr was trying to use (8080 didn’t match my actual port for SABNZBD which was 8085). This had previously been configured to 8085 and was working for a long time. The JSON error in the logs stopped once I put the port back to 8085.

Is it possible that one of the auto-upgrades of Sonarr reverted this setting back to 8080? (As a side note, all other settings in the download client section were still set properly (host, api key, etc)…just the port had somehow been changed back to 8080.

No, Sonarr wouldn’t adjust that port as that would cause countless issues.