@avif2016

Depends on what you mean by spam. If you mean spam emails there are quite a bit of things you can do.

1. You can setup Ticket Filters to reject tickets that contain certain words/phrases, that come from a specific email address, etc. (Admin Panel > Manage > Filters)
2. You can ban email addresses so they can't create tickets (Admin Panel > Emails > Banlist).
3. You can setup filters in the mailbox itself to move spam emails out of the INBOX so that they aren't fetched.
4. You can setup filters in the mailbox itself to move real emails to a specific folder and have osTicket only fetch from that one folder.
5. You can configure osTicket to only allow emails from existing Users (Users with existing accounts in your helpdesk).

I'm sure there are more things but that's what I got off the top of my head.

As far as turning the system back Online you can login as an Admin and Enable the setting Helpdesk Status under Admin Panel > Settings > System. Or you can login to the db, go to the ost_config table, and set isonline to 1.

Cheers.

@avif2016

Either the session expired, is invalid, or doesn’t match. You can see it starts here with checkCsrfToken():

• https://github.com/osTicket/osTicket/blob/c4353efde620c32d9dc2942c830aa71e920bc97a/scp/login.php#L62
• https://github.com/osTicket/osTicket/blob/c4353efde620c32d9dc2942c830aa71e920bc97a/include/class.osticket.php#L115

This calls validateCSRFToken():

• https://github.com/osTicket/osTicket/blob/c4353efde620c32d9dc2942c830aa71e920bc97a/include/class.osticket.php#L118
• https://github.com/osTicket/osTicket/blob/c4353efde620c32d9dc2942c830aa71e920bc97a/include/class.osticket.php#L111

This function gets the token and calls validateToken():

• https://github.com/osTicket/osTicket/blob/c4353efde620c32d9dc2942c830aa71e920bc97a/include/class.osticket.php#L112
• https://github.com/osTicket/osTicket/blob/c4353efde620c32d9dc2942c830aa71e920bc97a/include/class.csrf.php#L73

In validateToken() it checks to see if the token you provided matches and if it has expired or not. I would do some var_dump()ing there to see if it’s not matching or if it expired.

Cheers.

@avif2016

Go to your osTicket files, open include/class.csrf.php in any text editor, find the function function validateToken($token) (should be line 73), and change it to the following:

    function validateToken($token) {
        var_dump('Token: ', trim($token), 'This Token: ', $this->getToken(), 'Not Expired: ', !$this->isExpired());die;
        return ($token && trim($token)==$this->getToken() && !$this->isExpired());
    }

Once you make and save those changes go to the /scp login page and pull up the browser's DevTools (Right Click the login page and select the option Inspect). Once you have the developer tools pulled up go to the Network Tab. Now you can attempt to login which should trigger the code. At this point you should see the modal spinning and spinning (this is good in this case). In the Network tab you should see a new entry called login.php that has a Method of POST. Click this entry, click Preview, copy the content, and post it here.

Cheers.

@avif2016

Okay so as you can see the two tokens don't match which is why you get Valid CSRF Token Required. I would suggest opening the DevTools in the browser, go to the Application tab, click Cookies in the sidebar, find OSTSESSID/PHPSESSID and delete them, login to the database, truncate the ost_session table (this will log everyone out of course), Force Refresh the login page (Mac: Shift + Command + R / Windows: Shift + Ctrl + R), and retest. Sometimes even a full browser close and reopen works or Incognito windows.

If it's still not working after that then something is obviously messing with the sessions causing them to be different. This could be browser extensions, the way PHP sessions are configured on your server, etc.

Cheers.

@avif2016

I doubt IP changes would have an effect on this but it could be possible.

You can truncate by running TRUNCATE TABLE ost_session; in MySQL. More information can be found in MySQL documentation:

• https://dev.mysql.com/doc/refman/8.0/en/truncate-table.html

Cheers.

@avif2016

I’m not fully convinced the IP change is causing the issue just yet. I would first try truncating the session table as described above. Then I would clear all cache and cookies in the browser and force refresh the page. This is usually what works in these cases.

In some cases the session table needed repairing. You can run ‘REPAIR TABLE ost_session; in MySQL to repair the table.

Also quick question, what version of PHP is the site running?

Cheers.

@avif2016

Thats just the easy way to clear the sessions from the database. You can try to delete just your sessions by going to the ost_staff table, finding your account and grab the id, go to the ost_session table, and delete all records that match user_id = id_you_copied.

Cheers.

What version of PHP are you running?

avif2016 coworker first signed in; he saw my profile. Is this common?

No sure what you mean. Screen shots or anything? Did you / He clear your web cache before going to the new old site?