You can use reportTimeout config, set the number of ms there, and pass it to the azure web app as an environment variable.
This can be done in the azure portal / web app / application settings.
https://jsreport.net/blog/render-reports-using-azure-app-service
Hm, maybe an antivirus is blocking the chrome executable.
Please try to change the line here.
new LocalReporting().KeepAlive(false).UseBinary(JsReportBinary.GetBinary()).KillRunningJsReportProcesses().AsUtility().Create()
Does it help?
Could you try to install full jsreport and render a pdf there? It's typically easier to troubleshoot there the first.
https://jsreport.net/on-prem
Hi,
thank you for the bug report. Two problems here.
The first is that the enum has values notAllowed, highResolution, lowResolution
The second problem is that we recently fixed a bug in the password protection which will be part of the next release jsreport 2.11. This should be released in the next few days. In summary, please wait for the 2.11 and use highResolution value then.
Thank you for the confirmation.
It will be part of the 2.11. We will start with preparations next week.
Maybe please delete or answer your duplicated question here
https://stackoverflow.com/questions/64889811/blank-pdf-output-using-jsreport
Thank you for the bug report. It's now fixed here
npm i jsreport/jsreport-pdf-utils#f48b64246b583273001ad5c0cd96a238642407ee
The performance and render time is based mainly on the report js/css/html complexity. You can render 1000pages in 3seconds but it can also take 3 minutes.
Try to increase the timeout (cfg.ReportTimeout) and see how it actually takes.
It could also help to check the logs, where is the rendering stuck. This is typically in the chrome-pdf html->pdf conversion, but I may be wrong.
I see. Does it provide a temp where you can write? I guess you can reach the same problems when running the AWS Lambda function.
Please try to read through the tutorial here
https://jsreport.net/learn/aws-lambda-serverless
In particular, check this config which disables writing to logs or redirects the writes to the temp
https://github.com/jsreport/jsreport-aws-lambda-starter-kit/blob/master/prod.config.json
How do I get hold of a trusted certificate for this use? Our regular SSL cert for the server API is issued by Amazon. I don't think they'll issue anything else but certificates for the domains we have registered with them.
I don't have any experience here. I see here some notes and option to purchase but haven't tried it
https://www.sslmarket.com/ssl/aatl-certificates-for-trusted-pdf-signing
I'm busy now to try this out, but if you go through the process, please write down notes and share it.
We will happily add it to the documentation then.
When problem 1 is solved: How do I embed enough information in the PDF so the verification can be done even after the certificate has expired? See "Establish long-term signature validation" at the following link:
It seems the long term validation is enabled by default. Am I missing something?
