Scrobbling to Last.fm stopped working, what should I look for to troubleshoot?

[nulledone]

I have been using Navidrome since last December, I absolutely had no issues prior. But few days ago (15 April to be exact), I saw that my scrobbles have stopped. The only thing I've done prior to it stopping working is just restarting my whole server while resolving network connectivity issue.

I have tried to re-enable the last.fm scrobbling but now I encounter this error:

`An error occurred while authorizing with Last.fm.

Request ID: bb5bacbb9058/c2gkgxdoFb-004031`

I have tried changing the API key (I was already using custom one due to recent update), but nothing have worked.

I can see that the process is advances as intended (Last.fm correctly shows app name connected to the api key) but the last step spits out the error above.

[nulledone]

The logs state:
2024-04-19 13:30:54 navidrome | time="2024-04-19T10:30:54Z" level=error msg="Could not fetch LastFM session key" error="Get \"https://ws.audioscrobbler.com/2.0/?api_key=[REDACTED]&api_sig=1682e834d3a44eaf15e88f3509dc9c46&format=json&method=auth.getSession&token=wPUaKpGiiT__U8StOTGIrJgZ8n4qSwkI\": context deadline exceeded (Client.Timeout exceeded while awaiting headers)" requestId=bb5bacbb9058/c2gkgxdoFb-004352 token=wPUaKpGiiT__U8StOTGIrJgZ8n4qSwkI userId=be286a04-4dec-4e18-b235-f8d004f02749 2024-04-19 13:30:54 navidrome | time="2024-04-19T10:30:54Z" level=warning msg="HTTP: GET http://[mydomain]/api/lastfm/link/callback?uid=be286a04-4dec-4e18-b235-f8d004f02749&token=wPUaKpGiiT__U8StOTGIrJgZ8n4qSwkI" elapsedTime=1 httpStatus=400 remoteAddr=176.88.28.62 requestId=bb5bacbb9058/c2gkgxdoFb-004352 responseSize=94

Maybe related to following:
NixOS/nixpkgs#151550

[nulledone]

Figured it out, some DNS resolver issue as I was suspecting. I've changed the docker wsl2 dns servers to cloudflare and it fixed the issue.