Error after UNA 13 - A3 update
When I try to post into timeline I get this error "token expired. please try again" - any help please?
-
-
This error by the way occur in other actions not only when posting...for example, when try to delete an article ...
-
The problem is because your site wasn't updated correctly, some DB changes are missing the the DB
-
I did the update through dashboard in Studio. How can we fix these missing changes in DB?
-
I would suggest to change version back to 13.0.0-A2 in sys_modules table and in inc/version.inc.php file and apply update again, to make sure everything is updated
-
Did all of the above and still getting same error. I even went and restored the previous version from my backup and made sure the update occurred smoothly, and yet still getting the same "token expiration" error.
I really think this is an important issue after the "UNA-13-A3" update, as everything was running smooth before then.
-
Done all of the above, still getting the same "token expiration" error.
-
Token expired. Please try again. is the defining feature of UNA 13.
-
In UNA 13 form tokens depend on user's IP for additional security. For some reason it's not working for you, it maybe it's due to some errors during update. If you can provide access to your site in messenger, I can check this issue
-
Thanks @Alex T⚜️ . Since I didn’t get any fix for long time, I already rebuilt my site with B1. It is working now, that is why I am reluctant to update to B2😬
-
I get this error from my pc on our local network but when I use a phone their data network I do not receive this error. Seems to be generated by our isp router ip address.
What can be done to correct this? Our v12 production site does not have this issue
-
Update: issue is using brave browser on pc while firefox on same pc does not have this issue.
-
Thanks for the update. I hope with B5 this issues goes away completely.
-
@Alex T⚜️ @LeonidS I also think that this message comes too often and too quickly. Can we define that somewhere?
-
Hello @Baloo !
Could you plz specify how often did you get that message and what frequency would be fine?
