Unable to Remove Last.fm Connection from Roon Profile (ref#Y8TC8O)

Support
1

I have a broken Last.fm connection stuck on my Roon profile that I cannot remove through the app, and I would like your help removing it.

Problem:
My profile shows Last.fm as “Failed to login” under “Connected to your profile.” I cannot disconnect or remove it from anywhere in the app. Under Settings > Services and in the profile Edit screen, there is no working disconnect button for Last.fm - clicking it only opens a dialog with “Retry” and “Done”, and Retry always fails. Manage Services does not help either.

Background:
I deleted my old Last.fm account some time ago. Roon still keeps trying to log in to that deleted account and fails on every track, filling my server logs with repeated “Invalid session key - Please re-authenticate” errors (track.scrobble and track.updateNowPlaying, HTTP 403). I also tried creating a brand new Last.fm account and connecting it, but the stuck “Failed to login” connection did not change.

Request:
Please remove the Last.fm connection from my profile on your end. Important: I want to KEEP all my play history, favorites, and library data. Please remove ONLY the Last.fm connection - do not delete or reset the profile itself.

I can provide my profile name privately if needed for identification.

Setup:

  • Roon Server 2.70 (build 1671), running on a headless Linux machine

My home network: standard home setup, server connected via Ethernet. (Not relevant to this issue - this is a profile/account matter, not a network problem.)

2

I’m on the same problem. Nice to get a fix for this issue.

3

Hi @Peri and @BergeP,

Thanks for the report! We’ll go ahead and escalate this internally.

In the meantime, could you please try:

  • Disconnecting from a different remote/platform (e.g. desktop app vs. the mobile app), since the broken "Retry/Done" dialog behavior may differ across clients.
  • Sign the Roon account fully out and back in on the server, then re-check Services, though since the bad token is cloud-side, I'd expect it to persist. Worth a quick test to rule out a local cache issue.
Thank you! We’ll be in touch once development is able to take a closer look. 👍
4

Hi @BergeP and @Peri,

Good news! Our team already has a fix for this in the pipeline that should be included in our next Roon update.

You can keep track of what’s included in our updates here:

Thanks for your patience until the fix is deployed and in your hands! :folded_hands: