Scrobbler: Improve Error Logging for Network and TLS Connections

[geciriy235@afterdo.com]

Hello,
I am using the official AIMP Scrobbler plugin to scrobble my music to a self-hosted Maloja instance.

My Maloja server runs behind a Traefik reverse proxy, which is strictly configured to accept TLS 1.3 only. During the initial setup, the plugin failed to connect, and I noticed that the error messages in aimp_scrobbler.log are highly uninformative and misleading.

For example, the log shows:

Code: [Select]

Main 2026.06.11 18:19:43.774 D/Scrobbler: Maloja (self-hosted scrobble DB): Error: 12029. HttpSendRequest failed. Maybe a certificate issue. Ensure that TLS 1.2/1.3 are switched on
The Problem:

The generic error code 12029 (which is a standard Windows WinINet error for "cannot connect") combined with the placeholder text covers too many distinct issues at once. It could mean a total lack of network connection, a DNS failure, a severe TLS handshake mismatch, or actual certificate invalidity. This makes proper troubleshooting extremely difficult for users.

In my specific case, the plugin completely failed to handshake over TLS 1.3. The only way I managed to establish a successful connection was by downgrading my Traefik security settings to allow TLS 1.2. This clearly indicates that the plugin (or the underlying Windows component it uses) struggles with TLS 1.3-only endpoints.

The Request:

Could you please improve the error handling and logging mechanism for network requests? It would be highly beneficial to:

1. Parse and separate actual TLS/handshake errors from generic connection timeouts or DNS drops.
2. Provide more precise debug details in the log file to allow proper troubleshooting.
3. Verify if the plugin fully supports strict TLS 1.3 environments without relying on TLS 1.2 fallbacks.

Thank you for your time and for maintaining this great plugin!

[Artem]

As I say in previous topic, AIMP uses high level Windows API to access the network. On this level I have no detailed information what exactly goes wrong due attempt to connect to the server

[geciriy235@afterdo.com]

Is it possible to implement the OpenSSL library? It definitely has TLS 1.3, and they implement new security standards faster than Windows updates.

[Artem]

Is it possible to implement the OpenSSL library? It definitely has TLS 1.3, and they implement new security standards faster than Windows updates.

No. Windows already supports for TLS 1.3, ensure that the protocol is enabled in IS settings