-
Notifications
You must be signed in to change notification settings - Fork 6
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
Get 'Invalid Partner Login' With Valid Credentials #41
Comments
Maybe try another set of partner credentials, this set says it requires Pandora One so may work better for you: https://6xq.net/pandora-apidoc/json/partners/#internal-tuner-pandora-com |
I had thought the same thing before and had tried several different ones with no luck. |
The I'll update the README page to highlight this fact in the next release. |
I just tried going back to the original values but using internal-tuner for api_host and still get the same thing. |
Could you perhaps confirm which versions of Mopidy-Pandora and pydora you are using? |
...as well as the version of 'certifi' that is installed. |
According to pip freeze I have: I don't have 'certifi' installed, but it's not listed as a dependency of mopidy-pandora, is it? |
'certifi' is required by 'tornado', which is a dependency of Mopidy's - so it should be there if you installed Mopidy using pip. As far as I understand certifi is required to make HTTPS requests (Mopidy won't even start up for me without it?). |
Odd Mopidy works fine for me without... I will install it and see if that makes any difference. |
Same thing even after installing 'certifi'. ERROR 2016-01-07 15:57:14,285 [1608:PandoraBackend-7] mopidy_pandora.uri |
I saw this with some of the certifi versions, but haven't looked into it in detail because I was not sure if it was unique to my setup. Please try this specific version: |
I would also try running pydora outside of Mopidy to help isolate the problem. Have a look at the installation instructions over at the pydora project site.
You could also try creating a free ad-supported account at www.pandora.com for testing - just to make doubly sure that the problem is not related to an issue with the Pandora user account somehow. |
No luck with certifi==2015.4.28
The 'internal' url also gives me the 'Invalid Partner Login'. I will try the other things you mention. Thanks for the help! |
Assuming you are using pydora 1.6.4, it looks like This would indicate a problem with the user account, rather than the actual partner credentials. It's a little misleading as they both result in an Invalid Partner Login error message, which is perhaps something that we can try to improve. |
So I no longer get any errors! YAY! However, I don't see anything when I pull up the web client I can't find anything to do with Pandora. |
If you do not see 'Pandora' in the Mopidy library it means that the Mopidy-Pandora extension did not load successfully. There should be some indication of the root cause in the log. For the configuration that you posted; the comment at the end of |
That was a problem and I fixed that. It shows 'pandora' in the list of 'Enabled extensions' and the list of Disabled extensions is 'none'. I even see: But this is what I see in my UI: |
That's new. Could you perhaps run mopidy with Also include the output of |
Please also confirm that you get a listing of your Pandora stations if you just run |
Here is the debug log:
pip list
Running 'pydora' from the command line works fine. |
I'm fresh out of ideas. Mopidy should be logging any further issues in communicating with the Pandora server, so if the logs are clean there really is no reason I can think of why an entry for Pandora should not be showing up in the library. If you've got access to the source code you could try commenting out the implementation of |
I installed via pip but I am more then happy to try uninstalling and doing an install via source. Once I download the source from github should I just do a: python setup.py develop ? |
Yes please. |
Commenting that out made no difference except that the log line "requests.packages.urllib3.connectionpool: Starting new HTTPS connection (1): tuner.pandora.com" goes away. Maybe something to do with "PandoraFrontendFactory"? |
|
Where SHOULD Pandora be showing in the UI? |
So I reinstalled Mopidy and now it shows up! When I try and play anything I get no sound and the following shows up in my logs:
|
Ok sounds like good progress. Those are probably development branch-related dependency issues. The It might be simpler to just stick to the latest released version of Mopidy-Pandora for now (0.1.8). We've got some major changes underway in develop that will only really be stable when the next maintenance releases of pydora and Mopidy are available (which fix a few subtle bugs that have and adverse effect on Mopidy-Pandora). |
Sorry for the delay in getting back. I ran into a Mopidy issue which held me up in checking this out. Anyways, going back to the stable branch fixed this, and I now have a working setup! |
I have a Pandora One account (so I am actually paying Pandora monthly) and I am trying to setup mopidy-pandora to use my account, but no matter what I do I always get back 'Invalid Partner Login' and the extension ends up getting disabled.
The full error dump is:
My config is as follows:
I got the Partner encrypt/decrypt/username/password/device from the link provided in the setup details.
The text was updated successfully, but these errors were encountered: