Web terminal freeze after 1min inactivity - common problem?

[kodiak]

I’m using the web terminal on rOS 6.7 (on a CRS125) and notice that no matter the browser it freezes after 1min of inactivity, requiring an F5 refresh in the address bar which resets the console session.

Is this a common thing or is this a problem with my browser?

So far I’ve had a chance to test on Linux w/ Chromium and Google Chrome.

[efaden]

@kodiak

I’m using the web terminal on rOS 6.7 (on a CRS125) and notice that no matter the browser it freezes after 1min of inactivity, requiring an F5 refresh in the address bar which resets the console session.

Is this a common thing or is this a problem with my browser?

So far I’ve had a chance to test on Linux w/ Chromium and Google Chrome.

Never had that problem before… I’m running 6.8 as there is a bug with the CRS on 6.7 that was driving me nuts. But never seen that before.

[kodiak]

@efaden

@kodiak

I’m using the web terminal on rOS 6.7 (on a CRS125) and notice that no matter the browser it freezes after 1min of inactivity, requiring an F5 refresh in the address bar which resets the console session.

Is this a common thing or is this a problem with my browser?

So far I’ve had a chance to test on Linux w/ Chromium and Google Chrome.

Never had that problem before… I’m running 6.8 as there is a bug with the CRS on 6.7 that was driving me nuts. But never seen that before.

Ah, thanks very much for the response. I didn’t know if it was just me, sounds like it is. What was up w/ 6.7 on the CRS, I’d like to keep an eye out for trouble!

[efaden]

@kodiak

@efaden

@kodiak

I’m using the web terminal on rOS 6.7 (on a CRS125) and notice that no matter the browser it freezes after 1min of inactivity, requiring an F5 refresh in the address bar which resets the console session.

Is this a common thing or is this a problem with my browser?

So far I’ve had a chance to test on Linux w/ Chromium and Google Chrome.

Never had that problem before… I’m running 6.8 as there is a bug with the CRS on 6.7 that was driving me nuts. But never seen that before.

Ah, thanks very much for the response. I didn’t know if it was just me, sounds like it is. What was up w/ 6.7 on the CRS, I’d like to keep an eye out for trouble!

All of the traffic showed on ALL ports of a ether group… so you couldn’t tell which of the ports actually had traffic. Was a bug from 6.6 that was fixed in 6.8rc.