Security error when viewing notifications

[DaveInCLT]

for the last few days I’ve been getting the security error below when I first come into the forum and try to view notifications



when I take some other forum actions like view new posts, look at threads, etc and come back to view notifications it then works fine (so there is a workaround).

This is on iPad, ios 16.4.1 (a) with safari. I haven’t yet tried to replicate on my PC with chrome

 

[Burt Gummer]

I’ve had it also.

@amnesia

 

[dlee12]

I get that frequently on my phone when switching tabs..more often than not, CFF is 2/3’s of the tabs I have open.

 

[BigWaylon]

I get that if I’m browsing around and then swipe to go back and attempt to do something. Refreshing the screen always fixes it.

It’s along the lines of leaving a tan open and coming back to see the times listed in chat as in the future.

I don’t think there’s an actual problem.

 

[noway2]

To hazard a guess, most encryption protocols are sensitive to clock skew and while you’re getting the notification, I would guess that there is a mismatch between your current logged in status and the mechanism that is responding to your request such that they cant authenticate. Refreshing things by action such as reloading the page, etc. clears the mismatch.

 

[DaveInCLT]

it’s something I’ve only started seeing in the last week or so though, never had it before with the exact same browsing habits.

not sure if it is recent for others who have seen the same error? Are you also on iOS / safari

 

[noway2]

not sure if it is recent for others who have seen the same error? Are you also on iOS / safari

Yes, I’ve had it happen on occasion, but not too often. Did you per chance change location or turn on / off wifi so that the IP address is different?

 

[BigWaylon]

it’s something I’ve only started seeing in the last week or so though, never had it before with the exact same browsing habits.

not sure if it is recent for others who have seen the same error? Are you also on iOS / safari

It’s not often…but it’s been that way for months, if not years, for me.

Always seems like a cache/cookie issue, or something similar. Basing that on what I know causes it, and what I know fixes if.

 

[DaveInCLT]

Yes, I’ve had it happen on occasion, but not too often. Did you per chance change location or turn on / off wifi so that the IP address is different?

No changes in either.

 

[amnesia]

To hazard a guess, most encryption protocols are sensitive to clock skew and while you’re getting the notification, I would guess that there is a mismatch between your current logged in status and the mechanism that is responding to your request such that they cant authenticate. Refreshing things by action such as reloading the page, etc. clears the mismatch.

Basically this.

Alerts create a socket. That socket has an expiration time set. Leaving the page open and the socket expires then you have to refresh the page.

It also helps us not allow for ddos by using a slow post attack.

 

[noway2]

Alerts create a socket. That socket has an expiration time set.

Hey, im starting to remember the low level TCP/IP programming stuff from 20+ years ago. Back in those days it was kind of like working with black magic.