You've gone offline. Attempting to reconnect

ruckus over 1 year ago

Strange warning from tabs pointed at the Telligent connect after signing out...

You've gone offline. Attempting to reconnect...

I know, I've logged out - don't both reconnecting me (that would be a security issue).

Top Replies

Michael Monteleone 1 month ago in reply to drnas +1 suggested

This sounds like authentication is being lost. drnas said: It appears to cause some users to fail to post messages and therefore lose their message text. This reinforces this theory. Please review...
gregg.thomason 1 month ago in reply to drnas +1 suggested

The ultimate solution for us was to regenerate the machineKey; somehow something was not syncing up. Once we did this, it was solved.

Parents

0 gregg.thomason 2 months ago

I get this error constantly now, after my 10.2 upgrade, often in the middle of doing work on the site or simply browsing.

ETA: My console is laden w/ "Failed to load resource: the server responded with a status of 403 (Forbidden)" and "socket.ashx/negotiate?(full URL elided)". I have 2 web servers.
Cancel
Up 0 Down

Reply

Verify Answer

Cancel
0 Michael Monteleone 2 months ago in reply to gregg.thomason

How is your environment configured? Do you have a load balancer?
Cancel
Up 0 Down

Reply

Verify Answer

Cancel
0 gregg.thomason 2 months ago in reply to Michael Monteleone

Yes; AWS ALB. I also had a wild idea to check the license tab under site; it shows only 1 registered server (as it happens, a correct entry). We have 2 and our license permits up to 5.
Cancel
Up 0 Down

Reply

Verify Answer

Cancel
0 Michael Monteleone 2 months ago in reply to gregg.thomason

The issue resolved above for 10.1 was to prevent this error for members that log out of one tab but have remaining tabs open. Is that what you're seeing?

That said, it shouldn't be license-related. As long as you're logged in, nothing in the platform should be returning a 403 from that endpoint. We have seen occasional issues before where proxy configuration would prevent web sockets, server-sent events, or long polling -- all automatically negotiated over socket.ashx.

This, along with your other thread do make we wonder if some broader issue may be at work here. I'd still recommend opening a support ticket to help more deeply analyze the upgrade and potentially review an HTTP trace. My apologies if you've already taken these steps.
Cancel
Up 0 Down

Reply

Verify Answer

Cancel
0 gregg.thomason 2 months ago in reply to Michael Monteleone

We don't have a proxy, so I've opened a support case.
Cancel
Up 0 Down

Reply

Verify Answer

Cancel

Reply

0 gregg.thomason 2 months ago in reply to Michael Monteleone

We don't have a proxy, so I've opened a support case.
Cancel
Up 0 Down

Reply

Verify Answer

Cancel

Children

No Data