I cannot sign in to my Playstation account when using a regular browsing window, but I can when I use a private browsing window

Browser Support Web Compatibility
1

Description of the issue:
I cannot sign in to my Playstation account when using a regular browsing window, but I can when I use a private browsing window. Extensions are disabled in both cases, shields are up in both cases.

How can this issue be reproduced?

  1. Visit [https://](https://www.playstation.com/en-us/) in a regular browser session
  2. Click the blue Sign in button in the top right
  3. Fill in the form and click the Sign In button.
  4. Repeat the same steps in a Private browsing window

Expected result: Regardless of browsing session - private or regular - the page should redirect to the Playstation store with your username shown in the top right.

Actual result: An error message saying Can't connect to the server. (0.b71edf17.1735975450.cb2e5172).

Repeat these steps in a Private window and notice that logins are successful.

Exact URL of the website in question: https://www.playstation.com/en-us/

Did the issue present with default Shields settings? (yes/no) Yes

Does the site function as expected when Shields are turned off? Yes

Is there a specific Shields configuration that causes the site to break? If so, tell us that configuration. (yes/no): no

Does the site work as expected when using Chrome? Yes

Brave version (check About Brave): v1.73.104

Additional Information: In the Network panel, I observed that a POST request sent to https://ca.account.sony.com/api/v1/ssocookie returns a 403 - FORBIDDEN response when using regular browsing, but returns 200 - OK response when in private browsing mode. I suspect that this may be a CORS issue where certain security rules are applied in regular browsing sessions but not applied in Private windows.

Somewhat related: I also cannot access Gmail from a regular browsing session. I can only do it from a Private browsing window. In a regular browsing window, it just hangs when I enter the URL and press Enter. I’m assuming some security restrictions are at play here as well.

2

I’m assuming you realize that the only real difference between a private window and normal is when using default settings, (1) Private has no extensions (2) It starts with no cookies and clears cookies from that session when you exit.

Part of the troubleshooting I’d suggest is that you attempt in a new browser profile. Most likely it will work there. So hamburger menu → more tools → add new profile and create a second test profile. In that new profile, go to PlayStation and try to login.

If it works in the new profile, it just confirms what was noticed by you seeing it work in Private. The easier first step may be to clear all cookies for all time. If it starts working, then you know it’s that. If not, then it’s likely one of your extensions. Can test by removing them from your profile or you can attempt to add them to the new test profile.

Tbh, based on information you’ve given, I’m thinking it would be solved if you just straight up clear all cookies for all time.

3

It looks like nuking all the cookies did it. There is something fishy I noticed with the NordVPN extension where although it is allowed to run in Private windows it only proved problematic in the normal one. I’ll have to investigate that further.

Thank you for your help!

1 Like
4

Awesome! I figured that might be the case, especially when you mentioned the ssocookie part in your network panel. But I wasn’t entirely sure. Glad to hear the main issue seems to be resolved!

That’s interesting. If you have more details about the issues you noticed—or if you identify the cause or solution—I’d really appreciate it if you could share. It’d be super helpful in case others report similar problems in the future.

1 Like