bug: Reports not generating

[whiterabb17]

Is there an existing issue for this?

• I have searched the existing issues

Current Behavior

Hey, I've looked through issues for a while to see if i could find something similar but i havent been able to find it.
After finishing scans, i go to generate the report in version 2.2.0 (which used to be fine, no issues). One day i build the cluster and launched and then everytime i click create report, no matter which option i choose (Executive, Risk, etc) and no matter which template it just redirects me to a blank page with Server Error (500)

If i stop the cluster and change into rengine-2.1.3 directory and restart the cluster i can then export a report (using only the old template with formatting issues) but no matter what i do, cleaning the environment, starting from windows docker, linux docker, even creating a whole new fresh VM and using both the cloned source and the v2.2.0 release source both still leave me with the Server Error (500) when trying to generate the reports.

I havent been able to find anything in any of the container logs that would indicate why this is happening and I've been looking forever 😅

Expected Behavior

Reports to generate instead of Server Error (500) when trying to preview.
When trying to download the report it will download a PDF file but corrupted and unable to work

Steps To Reproduce

From fresh install on Windows or Linux
Version 2.2.0
Full Scan
Reports fail generation

Environment

- reNgine: 2.2.0
- OS: Ubuntu 20.04 / Windows 11 / Ubuntu 22 & 24
- Python: 3.11.0
- Docker Engine: Latest default using install.sh 
- Docker Compose: Latest default using install.sh
- Browser: Chrome (Windows) / Firefox (Ubuntu)

Anything else?

No response

[github-actions]

Hey @whiterabb17! 👋 Thanks for flagging this bug! 🐛🔍

You're our superhero bug hunter! 🦸‍♂️🦸‍♀️ Before we suit up to squash this bug, could you please:

📚 Double-check our documentation: https://rengine.wiki
🕵️ Make sure it's not a known issue
📝 Provide all the juicy details about this sneaky bug

Once again - thanks for your vigilance! 🛠️🚀

[dmchaledev]

Hey good morning @whiterabb17 thank you for filing report, could you please pull the overall logs as well as the celery logs specifically?

I'm working on a re-architecture for the celery workers/queue distribution where we are using while() and sleep() anti-pattern instead of chords/callbacks in celery and I'm a little bit suspicious the report generation is impacted by similar underlying issue.

Could you attach the output from these commands?

docker-compose logs > rengine_all_logs.txt
docker-compose logs celery > celery_logs.txt
docker-compose exec celery celery -A reNgine.celery inspect active > celery_active_tasks.txt

[whiterabb17]

Hey i tried again from a fresh VM and still the same issues.
Here are the attached files you asked for

Active tasks were empty though, the fresh scan was finished and i had tried to generate the report and the 500 error again.
Then I exported the logs and then stopped the containers

rengine_all_logs.txt
celery_logs.txt
celery_active_tasks.txt

[boukhrisssaber]

Hello,
i'm having this issue as well, first i though it was because of my setup (Ubuntu 24 vps that runs multiple dockerised services like Node Proxy manager and Portainer.. in addition to reNgine) but it seems not.
This is the preview

And The downloaded PDF reports appear to be corrupted

And upon taking a closer look with NP++ this is the content

I wanted to know if there's any workaround solution or any upcoming fixes !

[whiterabb17]

Hello,
i'm having this issue as well, first i though it was because of my setup (Ubuntu 24 vps that runs multiple dockerised services like Node Proxy manager and Portainer.. in addition to reNgine) but it seems not.
This is the preview

And The downloaded PDF reports appear to be corrupted

And upon taking a closer look with NP++ this is the content

I wanted to know if there's any workaround solution or any upcoming fixes !

Hey there, I think the Devs are working on some permanent fixes.
But what I can suggest for now - though it is a bit of a mission..
Do your scans and whatever else you need on v2.2.0, then stop your containers (eg. make stop) then if you don't already have it download the v2.1.3 release.
Then from the 2.1.3 directory start your containers again (eg. make up)
All your data should still be in the dashboard then print your report using the 2.1.3 dashboard.

Note the 2.1.3 release used the old report template. If you want to use the new one then copy the modern.html template from web/templates directory of the 2.2.0 folder and replace the base.html in web/templates/report folder of 2.1.3

[boukhrisssaber]

Hello,
i'm having this issue as well, first i though it was because of my setup (Ubuntu 24 vps that runs multiple dockerised services like Node Proxy manager and Portainer.. in addition to reNgine) but it seems not.
This is the preview

And The downloaded PDF reports appear to be corrupted

And upon taking a closer look with NP++ this is the content

I wanted to know if there's any workaround solution or any upcoming fixes !

Hey there, I think the Devs are working on some permanent fixes. But what I can suggest for now - though it is a bit of a mission.. Do your scans and whatever else you need on v2.2.0, then stop your containers (eg. make stop) then if you don't already have it download the v2.1.3 release. Then from the 2.1.3 directory start your containers again (eg. make up) All your data should still be in the dashboard then print your report using the 2.1.3 dashboard.

Note the 2.1.3 release used the old report template. If you want to use the new one then copy the modern.html template from web/templates directory of the 2.2.0 folder and replace the base.html in web/templates/report folder of 2.1.3

Will do, thank you

[Alexandrudiun]

Hi! I had the same problem as you. Please check: this #1522