Trouble signing in

Spotify is throttling the whole app for a while. It is not your account, your password or your connection, and because the limit is on the app, every attempt during the cool-off is refused in exactly the same way.

• Wait it out. The sign-in button unlocks itself the moment the cool-off is over.
• Nothing you can change on this side makes it shorter. Reloading, clearing cookies and using another browser all hit the same wall, because the limit is on the app rather than on you.
• Anything already in your library is untouched. A sync that was interrupted resumes by itself once sign-in works again.

Spotify runs new apps in a development mode that allows only a small number of connected accounts, and ours is full. This is a limit on notch.fm, not a judgement about you or your account. We have applied for wider access; we have no date for it and would rather say so than invent one.

• Your notch.fm account still works. You can sign in, and nothing you have saved is affected - it is only the Spotify connection that cannot be made right now.
• There is nothing to retry. Every attempt during the cap is refused the same way, so pressing connect again will not get a different answer.
• If you have been told a slot is free for you, connect again and it will go through.

notch.fm is built for Apple Music and Spotify, and only connects to the ones switched on in this build. The one you asked for is not among them right now, which is a fact about this deployment rather than about your account.

• Your notch.fm account is unaffected. Rating, tagging, searching and playlists all work with no service connected.
• Settings → Music service lists what can be connected today, and takes your address for the ones that cannot yet.
• There is nothing to retry: the same link will give the same answer until the service is switched on.

The Spotify consent screen came back with a no. notch.fm cannot read a library it has not been given permission to read, so there is nothing to sign in to yet.

• Press Continue with Spotify again and choose Agree on Spotify's screen.
• If that screen never appeared, a pop-up blocker or a password manager may have closed it before you saw it.
• If you want to know exactly what is being asked for before agreeing, the privacy page lists every scope and what it is used for.

One account at a music service can be connected to one notch.fm account, so that nobody's library and ratings end up attached to two profiles. This usually means you already have an account here and are signed in to a different one.

• Sign out, then sign in to the notch.fm account that already has it connected. If you are not sure which, the email address it used is the one to try.
• If you meant to move the connection, disconnect it from the other account first in Settings → Music service, then connect it here.
• If you did not set up that other account, say so through the contact page and it will be looked at rather than guessed about.

Connecting a music service adds it to an account you are already signed in to; it is not a way to sign in. The session ended somewhere between starting and finishing, which usually means it was started in one browser and finished in another, or the tab sat for a long time first.

• Sign in, then start the connection again from Settings → Music service.
• Finish it in one go, in the same browser you started it in.

A verification link works once and expires. This one had already been used, or it had been sitting in an inbox too long. It is not a sign that anything is wrong with your account.

• Sign in and ask for a new one from Settings. The newest link is always the one that works.
• Check you opened the most recent email, if you asked for more than one.

Signing in with Google relies on Google confirming the address belongs to you. For this account it has not, and accepting it anyway would mean anybody who could claim the address could claim the account with it.

• Verify the address with Google, then try again.
• Or create an account with an email and a password instead, which does its own verification.

Linking a Google account holds a short-lived window open while you confirm it, and the window closed. Nothing is wrong with either account; the link simply has to be started again.

• Start the link again and finish it in one go.

Spotify's reply did not match the request this browser started. That check is what stops somebody else's sign-in from landing in your session, so a mismatch is refused rather than trusted.

• Start again from this page, not from an old tab, a bookmark or the back button.
• Close any other notch.fm tab with a half-finished sign-in in it. Two at once overwrite each other's check.
• If it keeps happening, this browser is probably dropping the short-lived notch_oauth cookie: allow cookies for this site, or come out of private browsing.

The reply from Spotify arrived without the short-lived cookie that started it. It expires after ten minutes, and it belongs to one browser only.

• Press Continue with Spotify and finish it in one go, in this browser.
• Do not open the Spotify link in a different browser or on a different device from the one that started it.
• If the cookie is being blocked outright, allow cookies for this site or leave private browsing, then try again.

Spotify issues a one-time code and refuses it the second time it is presented. Reloading the page you landed on, or going back to it, spends the code and produces exactly this.

• Press Continue with Spotify for a fresh code. This normally works first time.
• Do not reload or bookmark the page Spotify sends you back to - start from this one instead.

Spotify let the sign-in through and then would not hand over the profile behind it. On an app still in Spotify's development mode, that is what an account which has not been added to the app looks like.

• If this app is still in development mode, the Spotify account has to be added to it in the Spotify developer dashboard before it can sign in. Nothing on this page can do that.
• If you revoked notch.fm at spotify.com/account/apps, sign in again and grant it.
• The code shown with the message is the exact status Spotify returned. Quote it in a report - it is the difference between a guess and a diagnosis.

Spotify answered with a server error of its own. Nothing is wrong with your account, and nothing is wrong with this app's connection to it.

• Give it a few minutes. Outages on their side clear without anybody doing anything here.
• If it lasts, Spotify's own status and support channels will know before this page does.

The request from this server to Spotify never completed. That leg is between the two servers, so your own connection is not the thing to check.

• Try again in a minute or two. A single dropped connection is common and usually not repeated.
• If every attempt fails this way, the server has lost outbound network or DNS and somebody has to look at it.

The client id, secret or redirect URI this deployment is using was refused by Spotify. That is a fault in the deployment, not in your account, and signing in again will fail the same way until it is fixed on the server.

• Nothing on this side helps. Trying again, another browser and another account all produce this.
• If you run this instance: check SPOTIFY_CLIENT_ID and SPOTIFY_CLIENT_SECRET, and check the redirect URI registered in the Spotify dashboard matches the one this server sends.

Sign-in got past Spotify and stopped inside notch.fm - a database write or the session itself. Spotify is fine; this one is ours.

• Try again. A one-off write failure usually does not repeat.
• If it does repeat, note the time and roughly what you did. Server logs are searchable by time, and that is what makes this findable.