After Browser Refresh, forced login (unknown error).

[Ace Suares]

Probably since the last update to 10.1.4.GA.4200000.UBUNTU20.64 UBUNTU20_64 FOSS edition, users experience *someetimes* a forced logout after browser refresh. This happens on Chrome and FF, did not test other browsers.

So, while logged in to the Webintereface, press F5 or some other way to refresh the browser.
Case 1: Dialog: Are you sure to leave? -> still logged in after refresh
Case 2: Dialog: The page that you're looking for used information that you entered. Returning to that page might cause any action you took to be repeated. Do you want to continue? -> logged out, so you see the login screen with 'unknow error'.

So, sometimes, the form resubmission question is asked by the browser. Why?

[adrian.gibanel.btactic]

Probably since the last update to 10.1.4.GA.4200000.UBUNTU20.64 UBUNTU20_64 FOSS edition,

What was your Zimbra version prior to the upgrade?

Users experience *sometimes* a forced logout after browser refresh. This happens on Chrome and FF, did not test other browsers.

So, while logged in to the Webintereface, press F5 or some other way to refresh the browser.
Case 1: Dialog: Are you sure to leave? -> still logged in after refresh
Case 2: Dialog: The page that you're looking for used information that you entered. Returning to that page might cause any action you took to be repeated. Do you want to continue? -> logged out, so you see the login screen with 'unknow error'.

So, sometimes, the form resubmission question is asked by the browser. Why?

Not sure why this might happen.

Does this depend on how long the user has been logged in?
Maybe the session expired and returns you back to the login page.

Do some of the users save the Zimbra login credentials in their browser? And some others don't? Maybe that explains why this happens to some users and it does not happen to some other users.

[Ace Suares]

Thanks for the suggestions. We all have creds in the browser.

When I login as userA and close the tab without logging out, and I open a new tab and go to the login screen and log in as userB, then I get 'Unknow Error'. This I think is becuase the old cookie for userA is still there. But that's a totally different thing.

In this case, after refresh also and 'Unknown Error' is visible in the login box.

Have not found any consistency yet.

My previus version was 9.00 ZExtras

[adrian.gibanel.btactic]

Thanks for the suggestions. We all have creds in the browser.

When I login as userA and close the tab without logging out, and I open a new tab and go to the login screen and log in as userB, then I get 'Unknow Error'. This I think is becuase the old cookie for userA is still there. But that's a totally different thing.

In this case, after refresh also and 'Unknown Error' is visible in the login box.

Have not found any consistency yet.

My previus version was 9.00 ZExtras

Maybe check in /opt/zimbra/log/mailbox.log while the error happens. It might be a left-over of the old installation after all.

[Ace Suares]

Checked mailbox.log, nothing there, except the succesful authentication (that is after the browser asks permission to resend data, and after the 'unknown error' at the login screen).

[j.sejo1]

solved: https://wiki.zimbra.com/wiki/How_To_For ... UI_In_ZCS9

It happens with the Default startup tip, but not with Classic, but the COS doesn't take the value. So I applied the link.

[adrian.gibanel.btactic]

solved: https://wiki.zimbra.com/wiki/How_To_For ... UI_In_ZCS9

It happens with the Default startup tip, but not with Classic, but the COS doesn't take the value. So I applied the link.

I wonder if this is fixed on latest builds based on 10.1.x and, well,... it only happens if you have upgraded from an old ZCS version.

Maybe my question is two fold:
- Can this issue be reproduced in the latest FOSS 10.1.x release if you install it from scratch?
- Does it make sense to apply that wiki suggested change to latest FOSS 10.1.x release?

[j.sejo1]

Install clean. 10.1.9 p1 Maldua ubuntu 22.04

This behavior occurs with the Default option. But it doesn't with Classic.

We know the user likes to press F5, hahhahaa.

[adrian.gibanel.btactic]

solved: https://wiki.zimbra.com/wiki/How_To_For ... UI_In_ZCS9

I am checking those changes to maybe adding them as Pimbra changes and I have two questions for a random Synacor employee that reads this thread randomly.

First of all... Are the ZmMsg.properties changes actually needed? After all they are just translations. Don't they? Why don't keep them unmodified if we are not going to use them?

Finally Couldn't we have achieved something similar by enforcing only the Classic entry instead of the Default one?

[adrian.gibanel.btactic]

solved: https://wiki.zimbra.com/wiki/How_To_For ... UI_In_ZCS9

It happens with the Default startup tip, but not with Classic, but the COS doesn't take the value. So I applied the link.

What ZCS version did you apply these changes to?
Was it a FOSS version or a NE version?

Could you please share the exact files and changes you did there?

I have not had the same experience as you trying to apply the wiki so maybe we applied different changes after all.

Thank you.