Log view doesn't respond on session timeout

[warg]

Hello,

I suspect that I can still navigate through the Cloudron admin ui when the session is dead but viewing logs doesn't work: It just opens the log viewer without any lines. After relogging it does work. I think the issue is that a session timeout/expiration doesn't force an logout so the log viewer's behavior should be correct but main UI isn't.

Of course this could have a different reason but then I'm not sure what's wrong.

Best Regards,

[nebulon]

The dashboard and logviewer use the same accessToken in the browser localStorage, there are no sessions as such. Possibly the access token got invalidated while the log viewer is open, but looking at the code it should redirect for login again. Did a logviewer reload via the browser work?

[warg]

There was no redirect on any page I had open. The situation was: My computer was in stand-by/power saving mode and I came back a day later, booted it again and saw that I forgot to close the Cloudron tabs. Then I noticed that I'm still logged on and that I could check something I had in mind. After some time I noticed the Log viewer didn't show any logs, e. g. for the LAMP app even when I did requests to the LAMP app and there should have been health check requests ongoing. So basically the log view was just blank with zero lines of information. After I logged out and logged in again, I was able to see the expected log entries.

So for some reason the refreshing/reading information process was broken. No redirect or log out was triggered. Visually there was no clue what could have caused this, e. g. no information about an invalidated access token. Reloading the admin UI or log viewer didn't change anything.

This happened on Windows 11 with latest Firefox.

[nebulon]

ah I see, I guess the websocket died and the code doesn't reconnect in that case then. Have to see how I can reproduce and fix this then.

[nebulon]

This is fixed for the next version.