Keep Getting Logged Out - Not All Browsers

fixed
#1

On my Mac I have been asked to enter a registration code several times over the last day. I realize there was an ST outage yesterday but not once have I been asked to register the browser again on my iPhone in the same period.

I mentioned this re-registering issue recently in the thread that talks about the new webCoRE web UI and it was explained that my login had just expired. But this seems like more as I have had to re-register the browser on my Mac about 6 times in the last 12 hours. And if was due to the ST issue then why has my iPhone not had to re-register?

Any ideas?

#2

I’ve been noticing this when I’m connected to vpn. That’s the only thing I narrowed it down to, not sure about others.

#3

Hmmm, no VPN in use here (other than in a Parallels VM I’m using for work - but that’s not new).

#4

Happening to me as of lately. :rage:

I have to get my iPhone, open WebCore app, obtain a temporary token, switch to my Mac/Chrome and enter token and re-authenticate. It’s a real pain of extra keystrokes especially when I indicated in the mobile client browser security option that I desired to stay logged in indefinitely.

When ST is having a mobile client outage, I am locked out of WebCore because I cannot obtain a temporary token. I would prefer that we could eliminate the temporary token page.

#5

There used to be a cookie issue where the IDE / webCoRE logins clashed with each other, when run in the same browser. Logging into the IDE logged out WC and visa-versa.

It was fixed a long time ago by @ady624, but I wonder if the dashboard updates might have unfixed it on some browsers / OS’s?

The dashboard update did include a cookie update that stores the state of hidden panels and the side-bar.

Perhaps try running the IDE in a private tab and let us know if that helps?

@ipaterson @acd37

#6

The hidden panels are tracked in local storage where the dashboard data is cached, as it turned out no cookies had to be added for the dashboard updates.

Have any of you seen a message at the top of the screen, either “There was a problem loading the dashboard data” or “There was a problem loading the dashboard data, please reload the dashboard to reauthorize this browser”? Are your Macs connected to ethernet or to wifi?

#7

Not so far that I have noticed. My Mac is connected to Ethernet and Wi-Fi.

Since I reported the issue above I have not had a repeat but I am watching it closely so I can try and see if there’s a pattern.

#8

Thanks, I’m particularly curious if it tends to happen after the computer wakes from sleep. I haven’t investigated whether the dashboard data is reloaded periodically but if it is attempting to reload and the network isn’t ready yet I could see a potential problem.

A change was made in the new dashboard to log out after 3 consecutive refreshes where the dashboard fails to load. Usually that is due to a misconfiguration, like a browser that was registered to a webCoRE instance that has since been deleted. If that code runs in the background under any circumstances rather than requiring the user to refresh the browser it would cause the behavior you’re seeing. However, based on your experience of getting kicked out 6 times in 12 hours I have very little confidence that this is related.

#9

On a windows PC here using chrome. Yesterday I had to log back in when I came home, my laptop woke from sleep and after refreshing the dashboard, got the login prompt.

#10

Do any of you have multiple browser tabs or windows open to webCoRE?

#11

Had multiple browser tabs displaying webCoRE lastnight … no problems … Windoze 10, Chrome. I had to register the browser (Chrome) on my Android, but not the PC, after that ST outage :man_shrugging:

#12

I don’t seem to have the issue here at work where I’m wired… err the computer is.

#13

Turns out the dashboard data is polled every 10 seconds (wow) but from what I’ve seen as soon as one poll fails the polling stops. So there could be a few things going on here:

  1. With 3 tabs open, each of those 3 tabs’ dashboard polling can fail when the computer loses network connectivity at which point you’ve hit the logout-after-3-failures.
  2. If the dashboard data stops polling after a single failure then coming back to the dashboard after a certain length of time you’re operating on outdated tokens and such until the dashboard data is reloaded… I don’t really know what effect that outdated data would have.
#14

Occasionally I have two tabs with the Dashboard running.

#15

Okay, just happened to me again on my Mac. I refreshed the tab with the dashboard running and it wants me to enter a new registration code. No other dashboard tabs running on this machine. iPhone is still good as is my iPad.

#16

Seems to happen to me on my Apple MacBook Pro/Chrome after closing and reopening the laptop which I’m assuming that this background polling issue is what is logging me out. I really would like to see a work around for this new issue as having to get the iPhone for a login token several times is getting tiresome.

I might need to come up with a way to generate the WebCore login token from the Mac?

#17

I’m going to make the log out after 3 errors an opt-in rather than automatic action. The error loading the dashboard message will just include a link to allow logging out which should be just as helpful for those who are affected by an actual data issue.

#18

That would be great. It’s happening more often for me, vpn or not. As soon as the laptop sleeps, it’s going to require a new login.

#19

@Nezmo @eibyer @kurtsanders and anyone else who was affected by the periodic sign out, please use the dashboard at https://staging.webcore.co for the next few days to test whether the removal of the automatic logout error handling fixes the problem for you.

This includes the following changes:

  1. Automatic logout after 3 failed dashboard load attempts is removed
  2. Added a cancel button to return from the registration screen after clicking Register Instance on mobile
  3. Show the dashboard with cached data if it fails to load over the network, primarily to allow access to log out, links to forum, etc. The dashboard error message continues to be visible but can be hidden with a click or tap to access the menu behind. The status message at the top is sanitized so I was not able to add a logout link.
#20

Got it. As of now I’m on the dashboard you provided a link to.

Just prior to changing I had another request to re-register.