Sony auth page says "Can't connect to the server" when 2FA is enabled

[igorsantos07]

Description of the issue

I was able to install the add-on and it found my PS5, but following the auth page from Sony, I receive this error below:

I got a hint this was related to 2FA when I tried to sign in to a separate page, where it properly asked for the 2FA code after my password... But it looks like the session is not reused on the auth link provided, even though I'm also logged at the Account Management page, under the same domain.

I got to the redirect page after going to the link above and disabling 2FA.

I guess this is a limitation on the Sony side, so maybe you could just add a note to the setup popup explaining that 2FA must be disabled for the add-on to work? (not sure if re-enabling works after the auth, I'm having several issues with my HA as well after installing the add-on and couldn't wrap it up lol)

Addon version

1.3.3

Platform

...............

Logs of the issue (if applicable)

No response

[RobertD502]

Are you referring to the steps for obtaining the NPSSO token? (the documentation seen below)

If so, open the first link (visit Playstation Homepage) in a private browser session (incognito). Do the sign in there. Then, in the same private browsing session, visit the this page hyperlink from the documentation.

I've had this issue happen to me before (I also have 2FA setup) and getting the token via a private session got around this issue. The issue is related to the current browsing session / Sony and will only be experienced (and not always) by those that have already signed in previously. No need to disable 2FA - keep yourself safe and re-enable 2FA.

[igorsantos07]

Nope... I meant the initial auth when enabling the add-on. I just wanted to know if the PS5 was on or sleeping, so didn't even bother with the NPSSO thingie. I was only able to properly get to the redirect page (the one you need to copy the whole URL) when 2FA was disabled 🤷‍♂️

[RobertD502]

Same process for this step - I opened the authentication button in a private session, which circumvented the error. Never had to disable 2FA. It all comes down to the browser session and is an issue on Sony's end. Perhaps it may make sense to include a little note in the README about carrying out the authentication/NPSSO token acquisition in a private session if a user happens to come across this problem.

[igorsantos07]

Nice, didn't think about using a private session - just trying to log in before carrying on with the add-on procedure, but that didn't do the trick.

It is indeed Sony's fault, very odd. I would suggest not only a note in the README, but on the auth popup as well, as I mentioned in the start - it's where the user will definitely see what's going on, without going through the eventual frustration of "looking in docs for a solution".

[FunkeyFlo]

Perhaps it may make sense to include a little note in the README about carrying out the authentication/NPSSO token acquisition in a private session

Agreed. Although my experience is that most people won't read it. But at least we'll get to say "rtfm". 😂

but on the auth popup as well

The pop-up is not managed by this project. It's a part of the psn-api project. If you want that changed you should log an issue/PR with that project.

[RobertD502]

Agreed. Although my experience is that most people won't read it. But at least we'll get to say "rtfm". 😂

Perhaps the chance of that happening can be decreased by adding a little markdown pizzazz to catch the user's eye. Something like this:

Caution

NOTE HERE ABOUT PRIVATE SESSION

😬

[github-actions]

This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 5 days