Topics created by MKuenzi

I figured it out, I had to go under EC2 to Load Balancers and set the load balancer timeout to a higher value. Thanks for helping me troubleshoot!

After a day of tinkering around with this I realize this is an issue I am running into with Amazon Elastic Beanstalk. I tried to do everything to invalidate the Dockerfile (I'm not pulling the image from a docker repository to avoid the additional complexity, I am simply uploading to EBS from my jsreport folder). I tried creating a new environment under my existing EBS application, that didn't work.

The best solution seems to be to just start a new application up from scratch in EBS, which did work on the first try.

Thanks Jan

I am using Amazon Elastic Beanstalk to host the jsreport docker image. I didn't realize Elastic Beanstalk itself was using nginx, so I will resolve it by looking at the Amazon documentation.

Thanks for pointing me in the right direction!

Thanks Jan,

I ended up doing a deploy to production with the Enterprise license applied. For some reason, the deploy fixed it.

I'll look into this further on this thread with your suggestions if I run into this again!

@vadnala I think this is when I ended up moving the jsreport server to Amazon EBS and it worked fine. So I never figured it out, I just moved to a new environment, I'm using Docker in conjunction with jsreport and deploying with EBS.

Nevermind after looking through your source code it turned out to be easier than I thought (I thought I had to pass the template etc based on the documentation)

var rs = new ReportingService("http://localhost:5488"); var report = await rs.RenderAsync(new RenderRequest() { Template = new Template() { Name = "sales-order" }, Data = data, Options = new RenderOptions() { Debug = new DebugOptions() { LogsToResponseHeader = false } } });

Just a thought, if the Name property said something about the name of the template to render I would have intuitively tried it. (Right now it says "Readable name, does not need to be unique")

Thanks a lot I will try that in the future. I actually realized I can just use the native Chrome footer for this after reading https://forum.jsreport.net/topic/1116/jsreport-native-header-footer-issue (I wasn't seeing the footer because I didn't set the margin like the OP) so that solution is working for me, but I will check that out if I need a more advanced solution.

Ah, okay I ran jsrpeport init again in an empty directory and I saw the start script does get created. Sorry about that, I must have screwed something up along the way.

Love the product by the way keep up the good work!