You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In normal logging, Sonarr URLs are sanitized: The hostname and the API key are obfuscated. This makes sharing logs not a security risk.
When an exception is thrown due to some HTTP failure, the URL is not sanitized. This is a different code path. Example:
[DBG] HTTP Request to http://hostname:8989/api/v3/system/status?apikey=SNIP
[DBG] HTTP Response (No response) from http://hostname:8989/api/v3/system/status?apikey=SNIP
[ERR] HTTP error while communicating with Sonarr
Flurl.Http.FlurlHttpException: Call failed. No connection could be made because the target machine actively refused it
. (localhost:8989): GET http://localhost:8989/api/v3/system/status?apikey=2424b3643507485ea2e06382d3f0b8a3
---> System.Net.Http.HttpRequestException: No connection could be made because the target machine actively refused it
. (localhost:8989)
The text was updated successfully, but these errors were encountered:
While the target for this was mainly Radarr, I believe this applies to Sonarr as well. I haven't thoroughly tested it but I will reopen this if I find an issue.
In normal logging, Sonarr URLs are sanitized: The hostname and the API key are obfuscated. This makes sharing logs not a security risk.
When an exception is thrown due to some HTTP failure, the URL is not sanitized. This is a different code path. Example:
The text was updated successfully, but these errors were encountered: