Session timeout using chrome > v88
- Dominant language
- C#
- Stars
- 5.1k
- Forks
- 1.6k
- PR merge metrics
- No merged PRs in 30d
Description
The UI disconnect happens after ~5 minutes of chrome tab inactivity. Any existing remote connection survives but the Remotely UI asks to reconnect due to session timeout.
As for the answer in #250 Its not a proxy misconfiguration, I use Ubuntu 20 and I tried every Nginx options for weeks and then gave up and tried plain Caddy instead only to get to the same Session reconnect popup.
I then tried Firefox which I don't normally use and I was like ... Whaaat!! No issues whatsoever.
The issue is due to [SignalR and latest Chromium](https://github.com/SignalR/SignalR/issues/4536) >88.
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by reproducing the session timeout after about five minutes of Chrome tab inactivity, comparing Chrome with Firefox and reviewing the linked SignalR/Chromium issue. The fix is complete when the Remotely UI no longer shows the reconnect popup while the existing remote connection survives inactivity.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- frontend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100