4
Users being logged out of webmail after a very short time
Problem reported by Jason Blanchard - 1/28/2021 at 7:37 AM
Resolved
Last night I updated to Build 7692 and I've noticed today that I've been getting constantly logged out of webmail. Maybe every 20 minutes or so. Are there logs or something I can view to track down why it's happening? I've got my application pool to set to recycle after 1440 minutes. Never had the issue of being logged out before the update. I haven't had any calls about it yet this morning, but I'd like to try to stay ahead of it and get this fixed before they do lol.

23 Replies

Reply to Thread
0
Derek Curtis Replied
Employee Post
Hi, Jason

In most cases, when customers see logouts in webmail, the issue has to do with a time zone setting. Here's a KB on some things you can look for to help with this issue: 

Derek Curtis
COO
SmarterTools Inc.
(877) 357-6278
0
Jason Blanchard Replied
I'll try to clear out the cookies on my computer, but it looks like it might be something else. I only say that because I'm seeing users from different companies all getting logged out at the same time. A lot of the ones that got logged out earlier have been connected for an hour now. Who knows. I'm going to keep an eye on it throughout the day.
0
Jason Blanchard Replied
Here's some more info. I'm using Firefox to login to webmail. I tried to delete any cookies for the site but there were none to delete. But I continue to get logged out. I logged in with a test account in chrome. It's been logged in for 30+ min straight while my Firefox session has logged out 3 times in that 30 min time span. Any idea why there wouldn't be any cookies stored in firefox? It's just strange considering I've never had login issues before the update.
1
Derek Curtis Replied
Employee Post
Did you check all your time zone settings? We’ve seen this same issue a few times over the last month or so and it has always been resolved by ensuring time zones are consistent across the browser, device, OS, mail server and any equipment that sits between all of these. (As much as possible.)
Derek Curtis
COO
SmarterTools Inc.
(877) 357-6278
0
Jason Blanchard Replied
Yeah my timezone settings matched. One thing that helped in firefox was I had to disable "Enhanced Tracking Protection" for that site. I think firefox was preventing it from storing cookies? I turned it off yesterday afternoon. I'm going to try to let it stay connected today to see if that resolves it.
0
Jason Blanchard Replied
Ok so that didn't fix it. It just logged everyone out of webmail 5 minutes ago. 
0
ActorMike Replied
I've had this issue as well for several months in the admin when impersonating a user. SM won't save drafts and effectively logs out the impersonated user which requires logging back in again.
0
Bert Garrett-Tuck Replied
Hi

My webmail users have begun to have the issue described here and are becoming a bit irate. I have even been randomly kicked out of the web interface when logged in as an admin user.

It started after the V7 update.

Again, timezone settings are all consistent (NZDT at the moment) - and calendar appointment time mismatches have been resolved for the most part.

I've directed everyone to clear their browser's cache and cookies. Even resort to changing to another browser (Chrome vs Edge).  They're still kicked out randomly.

0
Kyle Kerst Replied
Employee Post
@Jason: Since you're seeing ALL users logged out simultaneously this would indicate the SmarterMail IIS site or application pool might be restarting/timing out. Can I have you check to confirm its set up not to use Start Mode: Always Running, has no periodic recycle time configured, and is set up to restart only once nightly? These settings are all found within the Advanced Settings for the SmarterMail application pool in IIS. 
Kyle Kerst
Technical Support Specialist
SmarterTools Inc.
(877) 357-6278
www.smartertools.com
1
JerseyConnect Team Replied
You're not alone. We've been facing this issue of users getting randomly logged out for several months now. There's at least one other thread on this topic as well, https://portal.smartertools.com/community/a93922/users-get-logged-out-from-webinterface.aspx.

Support had us instruct our users to get Fiddler traces of the issue occurring. After providing those to support the issue has been escalated to development. I suggest opening a support ticket so they can help you get Fiddler traces of the logouts occurring. Hopefully with more data from different customers they'll be able to resolve this faster.

2
Matt Petty Replied
Employee Post
Yea, this is a frustrating one because I've seen it happen to me a couple times when impersonating and working on other stuff. We've had a few ideas at what could cause it but every attempt to reproduce results in no problems. I've had this issue on my to-do for a bit now and I've picked it up and tried working with it a couple times. If you're planning on submitting a ticket we can try to find more commonalities as to what could be causing it. Letting us know things like the browser they use, how often it occurs, any actions performed shortly before it happening, and what devices they have connected to their account can help a lot. Also if you can manage to capture this happening while the chrome debugger is open (Ctrl+Shift+i) and capture the network traffic and console window that would help a whole lot, but with how intermittent this is, it's been a challenge.

EDIT: Also additional info that could help is, Are all users seeing it or is it happening to just a couple. This gives me more to look at when trying to figure out commonalities.
Matt Petty
Software Developer
SmarterTools Inc.
(877) 357-6278
www.smartertools.com
1
Patrick Fanning Replied
Is this not fixed or at least a realistic work around,  I have web clients that are really getting ... well not happy.

Lost one client with 40 users over this ... 
Only change to the server was the last update install.

Patrick Fanning
CTO Advanced Group
2
Andrew Barker Replied
Employee Post Marked As Resolution
During some recent testing, we noticed a SignalR problem which occurred in inactive tabs when using Chromium-based browsers, such as Chrome and Edge. Even once we understood the problem, we were unable to reliably replicate the random logouts, but the nature of the SignalR problems makes it likely that the issues are related.

When a tab is inactive, Chromium extends all intervals and timeouts to at least one minute. Since, by default, SignalR is configured to disconnect after 30 seconds of inactivity, inactive tabs would drop the connection, then reconnect a minute later. Any processes relying on the SignalR connection would fail if they tried to communicate during this minute long disconnect. This includes the process which updates the authentication token held by the client, which in turn could trigger an apparently random logout.

To correct this, we adjusted our SignalR configuration and keep-alive pings to take into account the delay imposed by Chromium browsers. After making these changes, we have not seen any indication of SignalR issues. We included these fixes in the build 7852, released on July 1.

Andrew Barker
Software Developer
SmarterTools Inc.
(877) 357-6278
www.smartertools.com

0
JerseyConnect Team Replied
Patrick, there was a fix in 7845 that was suppose to resolve the issue, but our users are still experiencing it.
1
Andrea Rogers Replied
Employee Post
Hi JerseyConnect Team, 

I'm sorry to hear that the logout issue is still occurring for your users. The fix we implemented appeared to resolve this for some of our customers, but not all. In order to continue diagnosing the lingering issue, we'll need a Fiddler trace of the logout occurring. If you're able to replicate this issue regularly, will you please work on getting a trace of it occurring? Once you have a trace, please attach it to your support ticket so we can get this to the development team for their review.

Thank you,

Andrea Rogers
SmarterTools Inc.
877-357-6278

www.smartertools.com

1
JerseyConnect Team Replied
Looks like I was replying at the same time Andrew was, so I didn't see his update. Interesting to see that this may be SignalR related as we recently had an issue with that as well.

Unfortunately I've been unable to replicate the issue myself. So after I get SM updated I'll ask my customers for new Fiddler traces.
0
Jane Noel Replied
I have updated to 7859 last weekend in an effort to solve this problem for one user.  After the update I have 2 users complaining of constantly being logged out.  We have not been able to replicate the issue.

I saw Andrea mentioned Fiddler. I need to know more about that.

Should I have my clients install Fiddler Cap on their computer to capture data for a ticket?  Or should I install a different version on the server in an attempt to capture the data?

0
JerseyConnect Team Replied
They need traces from the client side. Here's the instructions that support gave us:

Download here: https://www.telerik.com/download/fiddler

Once installed, you'll then need to change the settings so it can decrypt any HTTPS traffic that occurs during the testing:

https://docs.telerik.com/fiddler/Configure-Fiddler/Tasks/DecryptHTTPS

Once that's ready to go, please close any applications/tabs aside from webmail, then try to recreate the issue. When finished, use the File>Save>All Sessions menu option to export the list of web requests as an SAZ file.
0
Jane Noel Replied
Thanks Jersey!

0
Bill Hughes Replied
Hey did this issue get resolved? We have been struggling with users complaining of exactly this for a couple of months. We have been chasing network issues. We recently updated to 7914 in the hopes of fixing the issue. It has not. I have no idea why this thread did not come up in earlier searches... but I am here now! :-) 

If anyone could give me an idea of how to resolve it, I would be very grateful. 
0
Jane Noel Replied
Bill, we updated a couple more times for other issues and this one seemed to resolve itself. We never even got to the point of using Fiddler.
0
Kyle Kerst Replied
Employee Post
Hey there Bill! The vast majority of affected users have only seen this intermittently or were resolved by correcting time/timezone and related areas from our KB article. If you're still seeing this on the latest release I recommend starting with the KB article below and submitting a ticket if you need a hand tracking this down: 


I hope this helps. Have a good one!
Kyle Kerst
Technical Support Specialist
SmarterTools Inc.
(877) 357-6278
www.smartertools.com
0
JerseyConnect Team Replied
I know we had a few customers switch to mail clients to work around the issue. Besides that we haven't gotten any new complaints nor have we heard back from anyone we asked to send us Fiddler traces. I can only assume the issue resolved itself or people are simply dealing with it.

Reply to Thread