Skip to content
This repository has been archived by the owner on Oct 4, 2020. It is now read-only.

PSVue addon no longer accepting login credentials #43

Open
mghalverson55 opened this issue May 28, 2019 · 149 comments
Open

PSVue addon no longer accepting login credentials #43

mghalverson55 opened this issue May 28, 2019 · 149 comments

Comments

@mghalverson55
Copy link

As of approx. 1 week ago, when I sign out of PSVue within Kodi, and then attempt to sign back in, I receive a "PSVue error, check the log for more information". It APPEARS to be concurrent with a recent update of the dependencies, but I am not sure. This issue is affecting both the Windows and Linux versions of Kodi 18.2. Also, if I do NOT sign out of PSVue (I have Kodi and the PSVUE addon installed on multiple computers), I am able to use the addon with no problems. The issue surfaces only after signing out. I contacted Sony and verified that my account is not being blocked or limited in any way (I can access the web version of PSVue, plus my AppleTV streaming box is not experiencing issues). Also, as a test, I created a new, temporary (free trial) PSVue account and attempted to log into it via Kodi and the PSVue addon, and it still failed. Finally, I did a clean install of Kodi and the addon on two PC's, one Windows, the other Linux (Ubuntu), and had the same result. I'm attaching the kodi error log for reference.

This is a great addon, thanks for the help.

Thank you.

Mike Halverson
([email protected])

psvue error after logout login kodi.log
@hackthis02
Copy link
Contributor

Yes, I'm seeing that to. You're getting a 403 response. We'll need to look into this.

@mghalverson55
Copy link
Author

mghalverson55 commented May 28, 2019 via email

@hackthis02
Copy link
Contributor

403 means forbidden. Basically the site said you were trying to access something you won't allowed too. This can also happen when the url to something changes.

@snoopyjoe
Copy link
Contributor

I'll look into this tonight. Looks like the login json info is missing or changed urls.

@mghalverson55
Copy link
Author

mghalverson55 commented May 28, 2019 via email

@snoopyjoe
Copy link
Contributor

snoopyjoe commented May 29, 2019 •
edited
Loading

Looks like the android_tv device type id is no longer accepted. I changed it to the web3-w id and it seems to authenticate again. Please let me know if there are adverse issues with the change. I would recommend uninstalling and delete the psvue userdata folder before installing update. That way the authentication doesn't try to use any old cookie data.

Authenticate Issue Update

@mghalverson55
Copy link
Author

mghalverson55 commented May 29, 2019 via email

@snoopyjoe
Copy link
Contributor

You will need to delete the psvue folder in the userdata folder. That folder stores all the cookie and login info. .Kodi/userdata/plugin.video.psvue

@mghalverson55
Copy link
Author

mghalverson55 commented May 30, 2019 via email

@mghalverson55
Copy link
Author

mghalverson55 commented May 30, 2019 via email

@snoopyjoe
Copy link
Contributor

I'll do some more testing before sending another update.

@eracknaphobia, seems the user needs to be logged in for the ssocookie url to work. I can log in from the grant code url but I need to be able to pass the credentials in the headers or payload. I'll work on it tonight and see what I can do.

@VegasChris
Copy link

VegasChris commented May 30, 2019 •
edited
Loading

Still recieving the same error. I think I'm following your instructions correctly, however the plugin.video.psvue folder is not in the userdata folder exactly. My path located in ../userdata/addon_data/. I'm hoping this was just a typo.

  1. Deleted ../userdata/addon_data/plugin.video.psvue/
  2. I uninstalled the addon.
  3. Restarted Kodi
  4. Reinstalled the addon from the developer repositoy (2019.5.29)
  5. Restarted Kodi
  6. Entered my login credentials.

Log file from Sony Bravia Android TV
Log File From Ubuntu 18.04 Laptop

I hope you find this information helpful. Thanks again for all the hard work that's gone into this addon.

VegasChris,
Student, Computer Science,
University of Nevada, Las Vegas

@snoopyjoe
Copy link
Contributor

I'm not sure if the request module changed or if Sony changed, but I'm able to login again. Let me implement it in the code and I'll pay something or soon.

@VegasChris
Copy link

I'm not sure if the request module changed or if Sony changed, but I'm able to login again. Let me implement it in the code and I'll pay something or soon.

Once the final patch is applied, would you mind making it ver. 2019.05.30 so we know when your all finished? Also, Not sure if this is up to you or not, but a lot of people rely on the official kodi repo. Might be a good idea to get the new one in there too.

@mghalverson55
Copy link
Author

mghalverson55 commented May 31, 2019 via email

@mghalverson55
Copy link
Author

snoopyjoe-
I had narrowed the offending file down to "settings.xml" under the userdata directory, and copied a known good "setting.xml" file from Windows over to Ubuntu, and the psvue addon began working again in Ubuntu. That is until about 8:30 this morning Pacific Daylight Time. Now, none of the machines where I have the addon installed are working. So I presume you, or someone, has changed something very recently.
-mike halverson

@VegasChris
Copy link

I just wanted to confirm that a solution has NOT yet been found for this issue? I'm still unable to log in on any platform besides the first party app or website.

@mghalverson55
Copy link
Author

mghalverson55 commented Jun 1, 2019 via email

@snoopyjoe
Copy link
Contributor

The login url is giving a access denied error. Sony may have changed something for the login. We'll keep working on it to see whats changed.

@VegasChris
Copy link

The login url is giving a access denied error. Sony may have changed something for the login. We'll keep working on it to see whats changed.

Is it possible that they're trying to prevent 3rd party app development?

@integrator-miller4-us
Copy link

Has this issue been resolved.
I'm am trying to test out psvue and hdhomerun to see if I can get to a single interface with all the channels I (I mean my wife) need.

@snoopyjoe
Copy link
Contributor

@eracknaphobia, may need your help with this one. I think Sony changed their authorization type but I can't find to what type. I ran out of time over the weekend trying to figure it out.

@mghalverson55
Copy link
Author

mghalverson55 commented Jun 3, 2019 via email

@hackthis02
Copy link
Contributor

The login credentials are cached and only re-authenticated when the add-on gets a 401 error.

@snoopyjoe
Copy link
Contributor

Correct. Your session expires when the cookie expires. Then the add-on uses your login to start a new session. So anyone still logged in now should be fine until their session expires. All the URLs are fine and work but the ssocookie URL no longer takes the logins as we're currently passing them.

Logging in else where then sending request to the URLs works perfectly. So all we need to do is figure the new way to send the login information.

@mghalverson55
Copy link
Author

mghalverson55 commented Jun 4, 2019 via email

@eracknaphobia
Copy link
Owner

I was able to get the login partially working. Still running into issues, almost seems like sony has a timeout between login attempts.

@snoopyjoe
Copy link
Contributor

That's as far as I got too. We're you able to log in from the ssocookie URL or from the grant code url?

@mghalverson55
Copy link
Author

mghalverson55 commented Jun 4, 2019 via email

@eracknaphobia
Copy link
Owner

ssocookie. Seems like there is an additional call needed to validate the device id before logging in, but I'm not certain yet.

@clonesr1
Copy link

clonesr1 commented Aug 15, 2019 •
edited
Loading

unfortunately I found everything else but I have not found the cookie tab (clicking on ssocookie then only shows header, preview, repsonse, and timing tabs). I have no idea why the cookie tab does not show up?

@snoopyjoe
Copy link
Contributor

It should always show a cookies tab unless you're clicking on the incorrect request or you logged in wrong. Almost every request should have cookie information.

@snoopyjoe
Copy link
Contributor

The ssocookie will be a XHR file

@clonesr1
Copy link

image
same tabs (heading, preview, response, timing, no cookie)

@snoopyjoe
Copy link
Contributor

Did you try widening the view or right clicking and select copy cookies? Looks like you just have everything squashed together. Your browser could be blocking the cookie.

@clonesr1
Copy link

clonesr1 commented Aug 16, 2019 •
edited
Loading

image
@snoopyjoe BTW, I do appreciate you trying to help me as always.

Tried widening the view, but no luck. Also when I double click on ssocookie, I get a new tab open and on that page is:{"npsso":"33zeA055hFeU9urt3R3YuzjdzntpzacoSoIJK89VUt6Cl1KQAC2wORnG56AqVYQJ"}.

Strange, there are entries that I click on them the cookie tab shows up, so it appears (not sure if I am saying this correctly) that there is not a cookie associated with the ssocookie, so only the other tabs are visible... Just not sure if there is something in my settings that are missing something?

Previously to be able to login to playstation vue on Chrome I had to allow 3rd party cookies, but not sure how the browser would be blocking cookies. But as you can see, still no cookie tab.

Also, tried Firefox, the developer tools does have the cookie tab but I am not finding ssocookie.

How is everyone else doing with the fix?

@clonesr1
Copy link

clonesr1 commented Aug 18, 2019 •
edited
Loading

Well, somehow I was able to get it to work. I was able to compare the my cookie.lwp file in my computers which did not have a problem to the one which PS Vue had the cookie issue. (I still was not able to get a cookie tab to show for ssocookie, but by looking at an auth setting which had cookies attached to it and found the npsso). I happen to notice the computer that was not working was missing a fourth area the cookie.lwp file (note below).

Set-Cookie3: npsso=THIS IS WHERE I PASTED THE NPSSO CODE I FOUND; path="/"; domain="auth.api.sonyentertainmentnetwork.com"; path_spec; secure; expires="2019-08-22 18:16:29Z"; version=0

So I entered the npsso, and then copied the rest of the setting from the non-working computer, and took a logical leap on the expiration date, since I did not find that in the working computer. I also added the npsso to the settings.xml and everything ended up working. Not sure if this makes any sense but the damn thing works for now.

@robmich55
Copy link

IT IS WORKING AGAIN...

On a whim, I did a reset ID and it is all working again. I did nothing else. Let's see how long this lasts.....

@snoopyjoe
Copy link
Contributor

I can confirm that @robmich55 solution worked. Tested on a remote device by resetting device ID then logging in again.

@gottahavit
Copy link

I can also confirm that resetting device id has everything working again.

@mghalverson55
Copy link
Author

mghalverson55 commented Aug 20, 2019 via email

@snoopyjoe
Copy link
Contributor

I don't use the repo versions but the GitHub version is the latest. Dated in june

@hackthis02
Copy link
Contributor

Resetting the device ID does not seem to be a wide spread fix. I've tried it to no success.

@mlburgett
Copy link

I have to agree. It has not worked for me, either.

@mfreeman72
Copy link

Resetting the device ID did not work for me, either.

@mfreeman72
Copy link

Question: Does the resetting ID only work if you've done the workaround of getting a valid cookie from inspecting the website data? Because I haven't done that. I was wondering if those who have the ID reset working are those that previously did the workaround.

@eracknaphobia
Copy link
Owner

Work around no. 2

  • Login to ps vue through chrome and start a stream

  • Press F12 to view the developer window

  • Select Application > Storage > cookies on the right and copy the reqPayload value
    image

  • Go to the addon_data folder of the ps vue addon and open the settings.xml file

  • Paste the value into the EPGreqPayload (remove double quotes at beginning and end of the value if applicable)

  • Set the last_auth time to a date in the distant future
    image

@hackthis02
Copy link
Contributor

hackthis02 commented Aug 22, 2019 •
edited
Loading

That work around worked for me. We'll have to see how long it lasts.

Update: After an undisclosed amount of time, clicking on any DVR episode prompts a message saying "This episode airs in the future". The only fix for this seems to be redoing the payload workaround.

@clonesr1
Copy link

clonesr1 commented Aug 22, 2019 •
edited
Loading

It was working but about 3 hours later, I started getting Playback Error, this episode has not aired yet. When I start Kodi now. On my other computer, when attempting to play a show, I get 'abck' cookie error.

I did note something, from the fix I was able to do about 4 days ago by adding:

Set-Cookie3: npsso=THIS IS WHERE I PASTED THE NPSSO CODE I FOUND; path="/"; domain="auth.api.sonyentertainmentnetwork.com"; path_spec; secure; expires="2019-08-22 18:16:29Z"; version=0

has now disappeared from the cookie.lwp file.

@mfreeman72
Copy link

mfreeman72 commented Aug 23, 2019 •
edited
Loading

@eracknaphobia That seems to have worked! Thank you! We were about to cancel our subscription! I hope that lasts, and I hope we can eventually find a more plug-and-play solution again.

EDIT: It looks like the PS Vue EPG Build Service addon doesn't want to work with this method. When I select a channel, it does nothing. Unless I've done something wrong there. I'll pick my battles, though. Going through the regular add-on works fine. Thanks for all your great work!

@mghalverson55
Copy link
Author

mghalverson55 commented Aug 23, 2019 via email

@eracknaphobia
Copy link
Owner

Damn, I just updated my repo with a new version thinking I had finally cracked it, but seems both that the old kodi repo version and the newest release both work. Wish I would've read @mghalverson55 post before hand. Oh well, lets hope sony has settled down with all the changes.

@clonesr1
Copy link

clonesr1 commented Aug 24, 2019 •
edited
Loading

Just tried to update to the ps vue from the kodi repo, and now I'm getting login failure, and going back to @eracknaphobia addon continues to give cookie errors.

EDIT: stupidly, I just needed to have the correct password
EDIT: Found when updating & reverting to the kodi repository addon, you may also need to log out and restart Kodi

@mghalverson55
Copy link
Author

mghalverson55 commented Aug 24, 2019 via email

@mghalverson55
Copy link
Author

mghalverson55 commented Aug 24, 2019 via email

@eracknaphobia
Copy link
Owner

Simply performing a logout after updating / downgrading seemed to work for me.

@mghalverson55
Copy link
Author

mghalverson55 commented Aug 24, 2019 via email

@mghalverson55
Copy link
Author

mghalverson55 commented Aug 27, 2019 via email

@mghalverson55
Copy link
Author

mghalverson55 commented Aug 27, 2019 via email

@K3rm1t4
Copy link

K3rm1t4 commented Aug 30, 2019 •
edited
Loading

I can confirm that the newest version from the Github repo is working fine on my devices as well. Thanks very much to @eracknaphobia and all other contributors!

That work around worked for me. We'll have to see how long it lasts.

Update: After an undisclosed amount of time, clicking on any DVR episode prompts a message saying "This episode airs in the future". The only fix for this seems to be redoing the payload workaround.

It was working but about 3 hours later, I started getting Playback Error, this episode has not aired yet. When I start Kodi now. On my other computer, when attempting to play a show, I get 'abck' cookie error.

@hackthis02, @clonesr1:
Even though the mentioned reqPayload work around is not needed anymore right now, you could have very well seen the effects of what I described in issue #45. I'm not sure but it seems like the validity of the reqPayload value may have been limited to 3 hours resulting in authentication failures whenever it is used in API calls.

Unfortunately, issues mentioned in #45 have survived all the drama of the last weeks/months and are still there. Now that the login procedure is back to being stable again (at least for the moment) I really hope somebody can find time and help to resolve these issues.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests