Unable to run reports

Self-Hosted | v5
1

Version

5.11.6

Environment

Self-Hosted, .tar
I have used built-in update prompts to perform InvoiceNinja updates when prompted.
Debian 12, PHP 8.2, Nginx 1.22.1, MariaDB 15.1

Issue

I am attempting to run the Tax Summary Report, for any time frame, after some amount of time, roughly 2 minutes, the report fails to runs with the only error being “Something went wrong”

Almost all reports are doing this, however I was able to run an activity report, and that downloaded fine, but all others that I have tried have failed.

No errors logged in storage/logs

I have tried turning on APP_DEBUG to true, no additional information was provided or logged (that I could find).

I have attempted a clean install using .tar, no change.

Everything else appears to be functioning as expected.

Thank you for any help.

2

Hi,

If you see “Something went wrong” in the app there should be details about the error in either the web server error logs or in storage/logs.

3

I’ve double checked storage/logs, only laravel.log, nothing recent with DEBUG true or false.

Nothing in nginx error.log, looking closer in access.log showed multiple:
“POST /api/v1/exports/preview/20952c0d-9551-4c41-919f-d0ed400696d0 HTTP/1.1” 409 43
at the time of attempting to run the report.

I am only logged in on one machine/browser at a time.

I have attempted to run from multple browsers, no change.

4

Spoke to soon about issue be solved after making websocks change on reverse proxy. It only worked for the first report, then continues to fail.

Thanks

5

Update

I have made changes to bypass my reverse proxy all together and access locally via http and still can not run reports with the same POST 409 error in the nginx access logs. Nginx error and laravel logs are empty.

I have also removed (with purge) nginx and reinstall, and have attempted to use older versions InvoiceNinja with no luck, I do not remember the version being used when last run reports.

Thanks

6

You wrote “I’ve double checked storage/logs, only laravel.log”

Have you checked in laravel.log for details about the error?

7

Yes, i am reading the the log file, nothing recent.

8

I’m not sure, I suggest asking in a discussion on GitHub.