403 blocks on Last.fm

Posted by brent in general.

its a telegram bot built with python, suddenly stopped working cause of 403 forbidden error, the API is not blocked i checked... exact error is: [19:41:05] 2026 10 16 16:41:04,563 lastfm bot WARNING Last.fm recent track fetch failed for (user): HTTPStatusError: Client error '403 Forbidden' for url 'https://ws.audioscrobbler.com/2.0/?method=user.getrecenttracks&api key=( )&format=json&user=( )&limit=1' [19:41:05] For more information check: https://developer.mozilla.org/en US/docs/Web/HTTP/Status/403 so idk what to do honestly, Ai said it could be an IP/node problem and idk how to change that...

Replies

Byte

A 403 here means Last.fm is refusing the request ; it doesn’t by itself show that Wispbyte blocked your node, and it isn’t a Telegram error. 1. Log the response body from (don’t log or share the full URL, since it contains your API key). Last.fm’s response may explain the rejection. 2. Try the same request locally with the same key and username. If it fails there too, check the key and request with Last.fm. If it works locally but gets 403 only from Wispbyte, the shared outbound IP may be the difference—but that isn’t confirmed by this error alone. 3. Share the sanitized response body and whether the local test works, and we can narrow it down.

brent

Could you please migrate my container to another node or assign a new outbound IP address?

brent

I routed the requests thru CloudFlare Workers to pass the blockage...

Wispbyte Community Forum