Open Unit981 opened 3 months ago
Can you confirm that you have a report that matches the Team and Assessment Type of the Assessment?
For instance, if you click edit in the assessment it may look something like this:
Then ensure you have a report template in the Report Designer that matches as shown below:
Hi @summitt - confirming that I have got the correct details matching up, the team name and report templates are matching to those seen inside Report Designer.
Issues still persist.
Would you mind trying to upload a new template from here: https://github.com/factionsecurity/report_templates.
Maybe the default template got corrupted somehow.
Hi @summitt - Just tried this and found the issue persists (even after regenerating report). I tried the 2 report templates available at the link provided above.
I think that my multiple redeployments of faction would rule this out as being an issue anyway.
Is there anything in the logs that indicate an error (catalina.out).
@Unit981 The other thing might be the memory in your VMs. Can you confirm how much memory is available?
@Unit981 There has been another issue reported (#61) that may be the same issue you experienced. This has been fixed in july24-updates branch. It's part of a bunch a fixes and ui updates that will be released to main in a few weeks.
If you have the cycles check out the july24-updates branch and see if this fixes your issue.
The issue still persists. Is it possible to get a proper solution soon?
@eLcapitanoBD are you also using the default templates and it fails on report generation?
I have recently redeployed a faction server and I can't seem to download my reports. I've tried to download sample reports and custom reports, default template and custom template - all to no avail. The image below demonstrates that my report is showing as successfully generated, however when i click download - it opens a new tab and does not download anything.
Screenshot also shows version number
To confirm that it wasn't a simple case of 'PEBKAC', I've redeployed on both 2 separate VPS's and locally in VM's - the issue replicates every time.