Hello,
I’ve finally started my official move from SugarCRM 6.2.1. My setup is
Ubuntu 22.04
SuiteCRM 8.6.1
and I getting some issues I’d like resolve.
For this topic, I randomly get the error message. I’ve poked around a bit and found some other people and their fixes. Of them
mod rewrite is enabled
access to Alerts is enabled
We do not use SuiteCRM to its fullest potential (see our use case in other posts by me). It seems like a real error but one that does not matter to us. We use Accounts, Cases, Contacts, Documents, Notes. We can drop KnowledgeBase and Reports.
If I create a Role for just our used areas would this remove this error? Initially I did check in suitecrm.log but did not see anything obvious (or did not recognize the msg + link the error together)
browsers are higher than the minimum, fails in both Firefox and Chromium
MariaDB - ‘mariadb Ver 15.1 Distrib 10.6.18-MariaDB’ > I gotta say, I’m not clear on which version MariaDB it’s telling me v15 or v10? I think the backend/brain is v10.6
It seems to happen if I leave the browser sit for awhile between clicking. An example is it auto-opens the page when I open my browser, if it sits unused then I try to login fresh 20mins later I get the error. I then refresh the pager and can log straight in no problems.
Is there some timeout/refresh I new to increase in my php.ini?
Yup. The error still exists for me. My current/installed version is 8.8.0 also. There is a script that sets permissions on a Linux setup. It’s been 2-3 months but I seem to remember running that script when I upgraded from 8.6 to 8.8. No change
Some more notes
if the web page sits at the login screen and I don’t log in for hour (maybe 20mins?) I always get the error
if I login when my browser opens (it preloads the screen in a tab) it works fine
if I login and leave it logged in I rarely get the error, I can leave it logged in for hours and it is mostly error free, not seriously tested but I would say it operates properly +90% of the time
whenever I receive the error a browser page refresh clears it up, whether (waited) initial login or actively using it and it fails with the error
