Vivaldi on one of my PC's decided i am logged out of Twitter

VaxPrime

So Vivaldi on one of my PC's decided i am logged out of Twitter now for no reason,... cleared cookies, restarted Vivaldi keeps on giving me "Something went wrong. Try reloading." when i try Twitter. Yet it works flawlessly on Brave Browser on the same PC, any ideas?

yngve

Clearing cookies will always log you out.

Most login services have a max time you can be logged in before they automatically log you out by specifying an expiration time of x days or months for the authentication cookie(s) from the day you logged in. Unless you logged into the other browser on the same day the other would keep being logged in for a while longer.

Another aspect, regarding Twitter, is that last week they disabled SMS Text Two-factor authentication for non-subscribers. I suspect that if a user's session was logged in using that method, then they might forcibly log the user out for that session.

Additionally, Twitter have "recently" had a tendency to be "slightly" unstable at odd times.

VaxPrime

@yngve Thanks for your reply.

I did not clear cookies before Tweetdeck told my to retry...
I never get logged out, i have been using Twitter since 2009.
My Brave browser logs into both Twitter and Tweetdeck without a hitch.
My Browsers are all set up to remember my Twitter Login Details , so if i was to get logged out it is no problem, it automatically lags back in.
Vivaldi on my Second PC on my Second Twitter Account is running without a Hitch.

There is some bug on This Vivaldi on This PC that Clearing Cookies, redoing Passwords does not fix... Probably by tomorrow it will just magically come right again.

VaxPrime

@yngve

VaxPrime

@VaxPrime Clicking Retry seems to have no effect at all.

DoctorG

@VaxPrime Check if one of your privacy/adblock extensions or Vivaldi Blocker (Shield in address field) cause such issue.

yngve

Unfortunately, I have no way to tell what goes wrong with Twitter. However, that screen shot does seem to indicate a server-side issue, probably with one of the micro-services (it is the same dialog one gets when twitter generally breaks down).

I had no issues getting to the login dialog in a 5.8 build, even with tracker and ads blocked. Considering that Twitter almost certainly still have CDN nodes around the world, the problem could be regional.

I'll note that one of my own machines got logged out of Twitter last week, just after the SMS 2FA disabling (No worries, I had already changed to a different 2FA for the account).

VaxPrime

Thanks for your reply.

I have reconfirmed, Adblock and Vivaldi blocking turned off, same issue still occurs.

VaxPrime

@yngve Thanks for your reply

So since it works on one PC and not on the other, i do not have either of them on 2 FA (Both Vivaldi latest update), it feels al wrong, i hope it sorts itself out.

DoctorG

@VaxPrime Could be a broken Cookies database. Sometimes helps: close Vivaldi, open browser data folder and delete Cookies file.

VaxPrime

@DoctorG I got this far: "userfiles\AppData\Local\Vivaldi", can you sugest which specific file host the Cookies Folder, i dont see it?

DoctorG

@VaxPrime Standard profile is at ...\Appdata\Local\Vivaldi\User Data\Default, there you can fidn the file Cookies.

VaxPrime

@DoctorG OK found it, logged me out of everything, but still the same issue

VaxPrime

mmmm, OK fuckit, ill just use Brave Browser then.

Thanks for your efforts guys.

yngve

@VaxPrime We got another, similar report yesterday about Twitter login not working.

That report included an important extra piece of information: The problem was due to the certificate verification error "ERR_SSL_PINNED_KEY_NOT_IN_CERT_CHAIN" .

Twitter have asked for a set of records locking several types of security features for their sites to be hardcoded in all browsers [1][2]. One of those locked security features is that their secure servers can only use certificates issued from a specific set of SSL Certificate Issuers (CAs), something called "pinning". This is something that have to be done carefully, because it is quite possible to brick your site for months if configured incorrectly.

This error is caused by one or more of Twitter's login servers using a certificate from a non-approved CA, and as a result Vivaldi block access to the server because it must be assumed that the server is fake and is using a certificate obtained fraudulently from a non-pinned CA.

I have no idea why your install always gets connected that/those badly configured server nodes, and your other browsers doesn't, servers should be assigned randomly, even in a CDN. It could be a network/DNS configuration issue, and that your other browsers get DNS information from a different source than the one that fails.

The Twitter entries in the list have been unchanged for 5 or 10 years, and it still the same in Chrome Canary, so this is not due to a sudden change in the pinning configuration.

This is something Twitter needs to fix, we can't. They have to locate their badly configured servers(s) and fix them.