- Affected version
- 2.2.12
I'm filing this bug as agreed with Jon from XenForo support.
Steps to reproduce on mobile phones (iPhone 13 and Redmi 9 having Android 11), when not connected to cable ISP, but to the mobile operator network:
When using mobile networks (and majority of users do), IP addresses tend to change pretty quickly and there is nothing we can do about that.
This issue happens less with
Also "Security error occurred. Please press back, refresh the page, and try again." dialog is a horrible user experience. It looks like there is some security incident on the forum. Even if we change the wording, it is still bad user experience.
If we need to trigger this error, my suggestion is to force invalidating session and refreshing the page automatically, without displaying any dialog.
Steps to reproduce on mobile phones (iPhone 13 and Redmi 9 having Android 11), when not connected to cable ISP, but to the mobile operator network:
- Login to Forum
- Write a message
- Switch to some other app (leaving the browser)
- More than 4 hours passes (user session limit)
- Open email app
- Got notification from Forum about a new message in the forum topic, click the link to visit it
- The corresponding page of the Forum opens (seeing that you are no longer logged in)
- "Security error occurred. Please press back, refresh the page, and try again" dialog appears.
- After refreshing the page, the same message pops up again
- Any subsequent page you visit - the same message keeps popping up
- The only solution to stop seeing the error is to log in to the Forum again
When using mobile networks (and majority of users do), IP addresses tend to change pretty quickly and there is nothing we can do about that.
This issue happens less with
$config['enableLoginCsrf'] = false;
, but using this is not the solution.Also "Security error occurred. Please press back, refresh the page, and try again." dialog is a horrible user experience. It looks like there is some security incident on the forum. Even if we change the wording, it is still bad user experience.
If we need to trigger this error, my suggestion is to force invalidating session and refreshing the page automatically, without displaying any dialog.