You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have searched for existing issues that already report this problem.
Server Hardware
NUC7
StartOS Version
0.3.5-1
Client OS
Android
Client OS Version
Android 14
Browser
Tor Browser
Browser Version
115.2.1
Current Behavior
Hi.
I run a DIY Start9 OS installation on a NUC7 hardware. For months, I have observed that, on a regular basis, I cannot access the UI, neither on .local nor .onion URL. 3 observations: a) SSH access was OK and I could see that all services are running b) mempool.space .onion URL was accessible and functional c) I could not see any particular issue on logs. A simple reboot via SSH and UI interface was operational again till next occurrence.
I have finally discovered on System -> Active Session that more that 40 "Other Sessions" were listed. Strange since I only use an Android device and a Win10 desktop to access the Start9 DIY device.
I have "Terminate All" sessions and since then I could not observe the issue anymore. Nowadays I manually clean "Other Session" on regular basis.
I come to the conclusion that for an unknown reason, "Current Sessions" are not cleaned up on exit and they just accumulate. When there are too many of them, then the UI behaviors is erratic.
Expected Behavior
When a session is "closed/canceled", the session should either a) be reused when the same device is connected or b) the session should be cleaned up so it does not accumulate.
Steps to Reproduce
1.-Open a Tor Browser on an Android device and connect to Start9 DIY device
2.-Close the connection
3.-Open a new Tor Browser connection on the SAME Android device
4.-On System-> Sessions you can observe that the first session is still available, it has not been reused/cleaned up and a new session is active.
Anything else?
I have attached an example.
The text was updated successfully, but these errors were encountered:
In 2023, a feature request was opened and closed where a limit to this observed behavior was requested. I have the opinion that this is an issue since if you do not do anything (like I have not done for months) then the device cannot be used anymore.
Prerequisites
Server Hardware
NUC7
StartOS Version
0.3.5-1
Client OS
Android
Client OS Version
Android 14
Browser
Tor Browser
Browser Version
115.2.1
Current Behavior
Hi.
I run a DIY Start9 OS installation on a NUC7 hardware. For months, I have observed that, on a regular basis, I cannot access the UI, neither on .local nor .onion URL. 3 observations: a) SSH access was OK and I could see that all services are running b) mempool.space .onion URL was accessible and functional c) I could not see any particular issue on logs. A simple reboot via SSH and UI interface was operational again till next occurrence.
I have finally discovered on System -> Active Session that more that 40 "Other Sessions" were listed. Strange since I only use an Android device and a Win10 desktop to access the Start9 DIY device.
I have "Terminate All" sessions and since then I could not observe the issue anymore. Nowadays I manually clean "Other Session" on regular basis.
I come to the conclusion that for an unknown reason, "Current Sessions" are not cleaned up on exit and they just accumulate. When there are too many of them, then the UI behaviors is erratic.
Expected Behavior
When a session is "closed/canceled", the session should either a) be reused when the same device is connected or b) the session should be cleaned up so it does not accumulate.
Steps to Reproduce
1.-Open a Tor Browser on an Android device and connect to Start9 DIY device
2.-Close the connection
3.-Open a new Tor Browser connection on the SAME Android device
4.-On System-> Sessions you can observe that the first session is still available, it has not been reused/cleaned up and a new session is active.
Anything else?
I have attached an example.
![Active_Sessions](https://private-user-images.githubusercontent.com/79864791/342365917-57a2cc1f-d890-4b7c-bcdb-ac8decbd261c.jpg?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MjAxODIyOTQsIm5iZiI6MTcyMDE4MTk5NCwicGF0aCI6Ii83OTg2NDc5MS8zNDIzNjU5MTctNTdhMmNjMWYtZDg5MC00YjdjLWJjZGItYWM4ZGVjYmQyNjFjLmpwZz9YLUFtei1BbGdvcml0aG09QVdTNC1ITUFDLVNIQTI1NiZYLUFtei1DcmVkZW50aWFsPUFLSUFWQ09EWUxTQTUzUFFLNFpBJTJGMjAyNDA3MDUlMkZ1cy1lYXN0LTElMkZzMyUyRmF3czRfcmVxdWVzdCZYLUFtei1EYXRlPTIwMjQwNzA1VDEyMTk1NFomWC1BbXotRXhwaXJlcz0zMDAmWC1BbXotU2lnbmF0dXJlPWJhODQxZDhiNmUwM2IzM2JhMWIyYjZkNGVlYzA2NjYyYmJkMDQ0YTAzMjUxODY2YTEzZTFmOGQwNDRjY2JiMDkmWC1BbXotU2lnbmVkSGVhZGVycz1ob3N0JmFjdG9yX2lkPTAma2V5X2lkPTAmcmVwb19pZD0wIn0.NDJqRXHytA8buK_y0VZWWHv45BJqMob3tuYI-Rt67NY)
The text was updated successfully, but these errors were encountered: