-
Notifications
You must be signed in to change notification settings - Fork 8
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
Can't Login on Chrome #19
Comments
I am having the same problem! Please fix! Thank you. |
Hmm, I can't seem to reproduce this on my Chrome install. Can you collect some information for me to help identify the issue?
Also send me any other info that you think might help. |
Hi. Google Chrome is up to date version 66.0.3359.117 when I go the link https://tuner.pandora.com it says Forbidden I do not see a green lock. It keeps wanting to log in with a user name and password. I have tried both my gmail account and my pandora account to log in. I can get into my pandora account |
I run a dual boot of Ubuntu and Windows on my computer, but I rarely use Windows. I first discovered this issue on Ubuntu, so I decided to boot into Windows to see if the problem was the same there. Since it had been months since I last booted into Windows, Chrome was not up to date. I'm not sure what version of Chrome I was running but Anesidora worked fine, and https://tuner.pandora.com/ said "Forbidden" with a green lock in the corner, secure https connection. But, as soon as Chrome told me "I'm ready to update, just reload Chrome!", I did so, and Anesidora stopped working, and the tuner.pandora website was no longer a private connection. Hope this info helps. |
Looks like this is exactly the same as #18. I'm also concerned that this might be the signaling of Pandora deprecating the API on tuner.pandora.com, which would kill this extension. Hope not though! |
When I try to login to the extension on Chrome, I get this error:
I'm certain that my username and password are correct - I tried several times, and I tried the exact same credentials on the firefox version of this extension and had no problem logging in.
The text was updated successfully, but these errors were encountered: