Ticket Export Fails in 1.18.x

lcscolussi

Hi everyone, I hope you are doing well!

I need your help as I am not able to export tickets from OsTicket 1.18.x.

I performed the clean installation using Installatron (cPanel) in PHP 8.1, everything works perfectly, I even have oAuth for login with 365, but this failure kills me since I cannot generate reports and information.

The strange thing is that there is no problem with the export of users, only the tickets export fail.

Error:

Console details:

When clicking in console details:

Server Info:

KevinTheJedi

lcscolussi

Look at your PHP error logs for any related errors.

Cheers.

KevinTheJedi

lcscolussi

I would also not recommend Installatron. I'd HIGHLY recommend re-installing osTicket the traditional way.

https://docs.osticket.com/en/latest/Getting%20Started/Installation.html

(we need to remove the Fantastico section from those docs; just follow the Installation Script section)

Cheers.

lcscolussi

KevinTheJedi Hi and thanks for the quick answer, there isn't any lines about this issue in the PHP error_log. It seems to be another thing.

By the other hand, i already did a clean installation by the traditional way downloading it from the official webpage you shared, and the issue stills remains with the same error:

Any ideas?

lcscolussi

KevinTheJedi Here is a detail from the console

KevinTheJedi

lcscolussi

There is a 404 which means URL not found. Have you contacted your host to see if they have security rules enabled blocking the request?

Cheers.

lcscolussi

KevinTheJedi

The host (Godaddy) indicates that there is no rule that could block the request.
A permissions problem perhaps? But I tried giving 777 access to the entire osticket folder and the same thing happens.

Here is some more info from the navigator:

I'm running out of ideas 🙁

KevinTheJedi

lcscolussi

Comment these two lines out and retest:

So in this case 404 actually means "No such export" which means it can’t find the export file. This either means it’s having trouble with their server's temp directory (ie. unable to create or read from the temp file) or the file is being deleted before it pushes it to the browser. Commenting out the lines above should stop it from deleting the file if this is the case.

If that doesn’t help I’d recommend creating your own temp folder with all appropriate permissions for PHP or webserver user:group, updating your sys_temp_dir setting in your PHP INI file to include the full path to the new temp directory, restart the webserver (and PHP-FPM if you’re running it) to clear any potential file cache, and retest.

Cheers.

lcscolussi

KevinTheJedi

Indeed, // those lines ended up generating the report correctly!!
Thanks a LOT for your help, I really admire the collaboration of the OpenSource community. You're the best!

Have a great day and week!

KevinTheJedi

lcscolussi

I will say that commenting out those lines will not delete the temp files so you will need to periodically delete the temp files yourself. You can look at the temp directory, list the files, create an export, list the files again, see what new file was added, and write a cron script or something to delete all files with that specific naming convention that are older than 24 hours. This way your server storage doesn’t build and build and eventually fill up the disk space crashing the server.

Cheers.