RudeySH / lastfm-bulk-edit

Bulk edit your scrobbles for any artist, album or track on Last.fm at once.

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

406 Not Acceptable errors

melat0nin opened this issue · comments

Great script! It worked for me once, and now I'm getting lots of 406 Not Acceptable server responses, and the javascript error 'There was a problem loading your scrobbles, please try again later.'

This happens even if I try to edit a single scrobble -- the popup displays with the loading spinner, then ~40% in it stops with the javascript error.

image

Does this happen when bulk editing any artist, album or track? If it is happening on specific artists/albums/tracks, please link them here along with your Last.fm profile link.

What browsers did you try? And which userscript manager, Violentmonkey or Tampermonkey?

Strangely, it just worked again after leaving things alone for about an hour. But now it's not working (again, same error). Is is possible there's some kind of API rate limit?

I'm running Firefox 103 beta on Windows 11, with lastfm-bulk-edit 0.5.2 through Violentmonkey. The problem arises on every artist/album I've tried (I attempted a selection, with different characters in their titles etc.)

I'm getting this issue right now as well. I'm not sure if it's rate limiting. If it is, they're using the wrong HTTP status code. This issue does not just affect my script, but the Last.fm website itself as well. It's very strange.

When viewing the list of tracks of an artist in a user's library, everything loads fine until you click "Next" or "2" to view the second page of tracks.

The same thing also happens when viewing the list of scrobbles on a track page. For example:

There seems to be something wrong with the page query parameter. Even page=1 results in a 406.

I created a topic about this issue on the Last.fm Support Forums: https://support.last.fm/t/error-406-can-t-access-any-of-my-recent-scrobbles/61503/12?u=rudeysh

A couple of hours after I created that topic on the Last.fm Support Forums, the moderator @hans-juergen replied the following message:

Staff has investigated this issue again and believes to have fixed it.

I haven't seen a 406 since my last comment, but I also don't use my script very often.