Have you checked these first?
Help us help you: include your environment details. We've made this easy for you. Use the Copy System Info button in Admin Panel › osAwesome › Diagnostics, then paste below.
Note: Never paste the contents of your ost-config.php file here; it holds your database credentials.
Two quick checks before posting: try clearing your browser cache, and press SHIFT+O on any Staff Panel page to enter Safe Mode (a stock osTicket with no enhancements). If the problem still shows in Safe Mode, it's in osTicket itself, not osTicket Awesome. But let us know about the issue either way.
Help us help you: include your environment details. We've made this easy for you. Use the Copy System Info button in Admin Panel › osAwesome › Diagnostics, then paste below.
This forum is public. Never post order numbers, full license keys, email addresses, or payment details.
This is the place for general questions about how billing and licensing work — renewals, activation, staging slots, plan differences, and what happens when a license lapses.
For anything tied to your specific account, refund, or payment, contact us directly instead.
So i have just moved from OSTicket to Awesome following the guide and everything seemed to work. now however though, if im sitting in the SCP and it tries to auto refresh to update the ticket list, it just logs me out and says "Session timed out due to inactivity" this did not happen when I was on OSTicket,
What is much worse though is even if i go though the login it just kicks me back out with the same message "Session timed out due to inactivity" even though i just logged in the only way to fix this is to clear all my cookies and then it only lasts until a refresh tries to happen and it logs me out again.
Please update on this, having paid for this software and it creating a problem that is starting to become un useable as it keeps logging me out of the SCP.
Hi Martin,
I'm sorry for the very late reply.
And you probably aren't going to like this response, but it is extremely unlikely that this issue was introduced by osTicket Awesome. It is an upstream issue with osTicket itself.
Please see this issue report for more information and some possible fixes.
I will close this for now, but if you still feel for some reason that it is an issue related to osTicket Awesome you can still reply again.
Thank you for understanding.