-
Notifications
You must be signed in to change notification settings - Fork 87
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Spotify: "unable to login offline: no such user" #531
Comments
Hi!, thanks for taking the time. I am pretty sure this is the error you get when the credentials used are incorrect. Please check your username and password. Also, note that you need Spotify Premium to stream audio from Spotify using Tizonia. |
I've created an issue to make sure Tizonia exists with an error message explaining that the login attempt has failed due to incorrect credentials. See #533. |
Closing this question now (note that #533 is now closed). |
I'm having the same issue, and I've double and triple checked that the credentials I have provided are correct. Literally copy+pasted from my password manager. |
Is Tizonia outputting this error?
If that is the case, then Spotify is the one preventing the login of the user with those credentials. Are you sure you can use those same credentials from another browser? |
I get the same error as well. I have triple-checked the credentials against my Spotify application, and they are correct. No non-ascii characters in either the username or password. I have tried removing all white spaces from those two lines of the config file. Same error. I have also tried bypassing the config file and entering the credentials directly as input arguments, but I get the same error.
|
Really strange. I can't really figure out what is going on. @atzorvas @LazyBoot @FrenchieSmalls I suppose you guys are all Premium users, correct? if so, for how long? Any chances that any of you could temporarily change your password and try with something else? (running out of useful ideas really..) |
Yes, Premium account on my end. I've had it for at least a couple of years now. I probably shouldn't change the password, because my wife uses the account as well. I thought that there might have been an issue with other open clients, so I made sure that Spotify was closed on my two computers and phone. It may be open on my wife's phone, but she's currently at a conference and won't be actively using the app. |
Hello, i got a same problem. Spotify] [Track] 'Planet Of New Orleans' [Dire Straits]. [OMX.Aratelia.audio_source.spotify.pcm:port:0] |
Yes, public playlists and in general any other Spotify metadata is accessible without credentials; but a Premium account is required to stream the tracks. Would any of you be able to go to this location with a browser that hasn't got your credentials stored and see if they work in there (I assume they will)? |
My credentials work at that link. |
|
[Spotify] [Connecting] : 'USERNAME'. |
Getting the same error. Credentials work at that link...not via tizonia. Not sure if it matters or not but I'm on a Premium Family Plan |
That is unrelated. It is just a reminder to install a faster fuzzy matcher. You can do it like this:
|
@tizonia OK, thnx :) |
My account is the regular Premium account... |
I tried changing my password, it didn't help. |
@LazyBoot I'll keep investigating. |
If it helps: I'm located in Germany, but I logged into my VPN with US access and I still get the error. |
Same problem here, tried Spotify username and e-mail (both are working via open.spotify.com), no special characters, same error when using credentials via tizonia config file and via command parameters. Active Spotify Premium account, Linux Mint 19 Tara, all system and python packages updated. Tizonia installed via shell script and all dependencies are fulfilled.
|
@d1X0n thanks for your feedback. Unfortunately, I have no idea yet why this is working for some people and not for others. But this is obviously high in my priority list. |
I have exactly the same issue and I use also Premium Family Plan. |
I do have premium family as well! Do all of us have premium family?
…On Sat, Dec 8, 2018, 01:13 Bartłomiej Zieliński ***@***.*** wrote:
I have exactly the same issue and I use also Premium Family Plan.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#531 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAgMvi_J_lAidhASP8lKoUuQPczgvJ7kks5u2vYggaJpZM4Y7L03>
.
|
Just a reminder that the Spotify login name currently has to be provided to Tizonia as 'username' i.e., without the '@Domain' part. I noticed that some of you tried both forms, without luck, but just in case. |
Well, my username doesn't have an @Domain part anyway. |
@juanrubio Sorry, but that didn't work either. I reinstalled mopidy with the spotify extensions, but still getting the error. I have the problem on Ubuntu 18.10, tizonia installed via snap, regular premium user. |
@juanrubio tried to generate mopidy client-id and client-secret credentials on https://www.mopidy.com/authenticate/ and used that as my username and password in tizonia, but unfortunately it didn't work either :( |
Same login issue, snap install: [Spotify] [Tracks in queue] '35'. [OMX.Aratelia.audio_source.spotify.pcm:port:0] |
Removed the snap and built from source, same errors: [Spotify] [Cache]: '/var/tmp/tizonia-rich-spotify-USERNAME' [OMX.Aratelia.audio_source.spotify.pcm:port:0] Interestingly enough it was working on my Kubuntu install as recently as Friday Dec 14 2018. But some drunken disk reorganization messed up that install. |
Same login issue here, clean install from AUR (latest stable release). I have student spotify premium (should not matter) registered with email. Same behavior on two different machines, one running Manjaro and other Arch. |
I am getting the same login error, putting username and password in "" did not resolve the issue either. both are defined in the config file.
The relevant part of the configuration file:
The project looks great, shame the logging in does not work |
Exact same problem on Debian Stretch.
|
Hey, thanks everyone for the feedback. It has been very useful. Here is some more information. I've created a new premium account (non-family, non-facebook login) and I can confirm that the new account does not work with Tizonia (i.e. libspotify), whereas my old account continues to work perfectly fine without any issues. One obvious difference between the new account and my old account is that the username is not related anymore to the email address and instead it is now a random string of around 25 characters allocated by Spotify. However, the interesting detail is this one (screenshot from my old account): Tizonia was registered a long time ago as a Spotify client (required in order to use libspotify); However a user of Tizonia has never needed to explicitly authorize Tizonia to use his/her account. I.e. giving your Spotify credentials to Tizonia was enough to implicitly authorize Tizonia to use your account (I think this is what Spotify calls 'Implicit Grant Flow'). This is what I believe has changed in recent times. So any old users of Tizonia (like me) that already have Tizonia as an authorized app in their account should be able to use Tizonia as normal. But the Implicit Grant Flow seems to be disabled now for libspotify-based clients. The solution that I believe might work is to implement one of the other authorization flows, like the Authorization Code Flow: I believe this is what mopidy-spotify does and I suspect still works: Tizonia had this for SoundCloud, but not for Spotify, since it has not been required (until now). I will investigate how to add this new authorization flow for Tizonia. |
Thanks for investigating. I've been running the heavy spotify client like some kind peasant. |
@tizonia I indeed have a 25 char account name, any help I can provide? |
I too have 25 char account name. I tried to use both email and the long account name for my username in the config but both give the same error. |
Just another piece of info. I received last week an email from Spotify asking me to reset my password. Sounds like my attempts to access Spotify from other countries using various VPNs triggered the reset on their end. So I had to change my password and after that, I can no longer access Spotify with Tizonia, even though Tizonia still is displayed in my account as an authorized app. Maybe I'll have some time to implement the new auth flow this coming weekend. |
I've created a new premium account today (with a new email address). Try to use it with the latest 0.16.0 version but I'm getting the same error as everybody.
But strangely, if I use the exact same command on an older Tizonia installation (which is on 0.15.0) it does work with the exact same account.
I don't know if it's a useful info. |
Spotifyd (https://github.com/Spotifyd/spotifyd) works great if all you want is a spotify client. |
Thanks, @codeKonami
Most useful indeed. Pretty unfortunate, but a regression was introduced in 0.16.0. Just realized after comparing 0.15.0 and 0.16.0. The fix is now in the develop branch (96074c2). It looks like an already populated cache (e.g. /var/tmp/tizonia-me-spotify-my) would hide this regression for an existing user of the software (like me). However new users, (or people changing their Spotify passwords, or people installing the software on another machine, where the cache would not be populated yet) would see this problem. I am spinning a new release now. Version 0.17.0 will be in the repos in the next 2-3 days. |
Great,
thnx.
M.
čt 17. 1. 2019 v 0:52 odesílatel Tizonia <notifications@github.com> napsal:
… Thanks, @codeKonami <https://github.com/codeKonami>
I don't know if it's a useful info.
Most useful indeed.
Pretty unfortunate, but a regression was introduced in 0.16.0. Just
realized after comparing 0.15.0 and 0.16.0. The fix is now in the develop
branch (96074c2
<96074c2>
).
It looks like an already populated cache (e.g.
/var/tmp/tizonia-me-spotify-my) would hide this regression for an existing
user of the software (like me). However new users, (or people changing
their Spotify passwords, or people installing the software on another
machine, where the cache would not be populated yet) would see this problem.
I am spinning a new release now. Version 0.17.0 will be in the repos in
the next 2-3 days.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#531 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ArhRuVXelTyRUHlfnkIIbmqqyg_OClhUks5vD7szgaJpZM4Y7L03>
.
|
@tizonia Great news! Thanks |
Hi,
thnx, i got a new update - all work's fine !!
M.
čt 17. 1. 2019 v 13:07 odesílatel Juan A. Rubio <notifications@github.com>
napsal:
… Closed #531 <#531>
via 96074c2
<96074c2>
.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#531 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ArhRuUXEPPc7Wy1C2o_BGytV55OdS6UAks5vEGd6gaJpZM4Y7L03>
.
|
Sadly, the docker image is still on 0.16 https://github.com/tizonia/docker-tizonia/blob/master/Dockerfile#L12 |
I've successfully updated to version 0.17.0 and everything now works like a charm! Finally, I can fully enjoy your product :) Thank you very much! |
Hopefully, the docker image will get updated very soon. Thanks all for your patience! |
The docker image is now working too! |
Tizonia no work its down ? for spotify |
First of all, gratz for the project!!
Description
Can't use spotify integration
Steps to Reproduce
tizonia --spotify-user atzorvas --spotify-password "XXX" --spotify-track "Can't stop"
Expected behavior: Be able to listen to some music :)
Actual behaviour:
Reproduces how often: Always (for me at least..)
Versions
Installation Method Used
Snap package
The text was updated successfully, but these errors were encountered: