and most of my users use old gov PCs

if you have any other suggestion I will be thankful
this is my email: alfaqihrafeeq@gmail.com

Anyway, try to set the jsreport temp directory explicitely to /tmp/something.

In general, you can install the font to the OS, or use a webfont from cdn, or embed font in base64

The jsreport.Linux.Binary includes the chrome binary but you typically need some extra dependencies installed on the running system.

The list of required dependencies for a particular Linux distro can be found here
https://pptr.dev/troubleshooting#chrome-doesnt-launch-on-linux

In the past, the list was changing and often incomplete. Therefore our red-hat install guide rather installs chrome from rpm package, which assures the required dependencies are installed along with the chrome binary. You should be good to for jsreport.Linux.Binary with the mentioned guide.

Note I typically recommend running jsreport standalone. For example in an extra container with docker compose. In this case you can simply use our official images.

At this moment, you can replace the folder with Chrome with your one. It should be here

this is likely because the OSX binary we deliver is for arm processors.
I've added to the back log task to add also x86 binary to the build process so we can ship it also in the .net Nuget packages.
https://github.com/jsreport/jsreport/issues/1142

Jan

Try to update to the latest or remove the Options.RenderOptions.Timeout config.

Are you sure this properly resolves /lib/bootstrap/dist/css/bootstrap.css ? The same is in both result and cover when you inspect it?

Are use sure the bootstrap isn't applied? The bootstrap has different styles for printing and normal browser display. jsreport by default uses media print, so the pdf output may look differently than in the browser.
You can use Template.Chrome.MediaType prop for setting the screen media that browsers use for display.
https://github.com/jsreport/jsreport-dotnet-types/blob/master/jsreport.Types/Request/Chrome.cs#L29

Based on this playground
https://playground.jsreport.net/w/admin/tV6sVKbV

However, I am not sure if it is the right approach to have jsreport locally in the .net app. It is quite complex and it looks to me like you should rather have a full-blown jsreport server doing this and you communicate with it using jsreport.Client.

I've pushed a fix to support adding multiple pdf with bookmarks
https://github.com/jsreport/jsreport/commit/f2b3e0e53b177d4a0d684803c5f612b1477e5e6e
It will be part of the v4.3.0 coming in the next weeks.

Thanks it works very well
But I want to create a toc based on the page created above.

.net core code

var pdfReport = await JsReportMVCService.RenderAsync(new RenderRequest
{

 Template = new Template()
 {
     Content = result,
     Engine = Engine.Handlebars,
     Recipe = Recipe.ChromePdf,
     PdfOperations = new List<PdfOperation>()
     {
         new PdfOperation()
       {
           Template = new Template
           {
                 Content = toc,
                Engine = Engine.Handlebars,
                Recipe = Recipe.ChromePdf
            },
            Type = PdfOperationType.Prepend
         },
         new PdfOperation()
         {
             Type = PdfOperationType.Merge,
             MergeWholeDocument = true,
             Template = new Template
             {
                 Content = header,
                 Helpers = @"
                                 function getPageNumber (pageIndex) {
                                 if (pageIndex == null) {
                                         return ''
                                 }
                                 const pageNumber = pageIndex + 1
                                 return pageNumber
                             }

                             function getTotalPages (pages) {
                                 if (!pages) {
                                     return ''
                                 }
                                 return pages.length
                             }",
                 Engine = Engine.Handlebars,
                 Recipe = Recipe.ChromePdf,
             }
         }
     },
 }

});

This lines from the v2 doc could help

In general it is typically better to run standalone jsreport and communicate with it with jsreport.Client nuget. The standalone installation guides can be found here
https://jsreport.net/on-prem

Just an update, I successfully got this working by using the overrides capability of the .Net Client.

For anyone else trying to do the same thing, here is an example:

it keeps returning the template instead of the rendered document

Do you mean it returns xlsx file, but the original exceltemplate template without changed cells?
This would be expected, because you provide no calls here Content = "{{{xlsxPrint}}}",

What you can do is use pdf utils to merge footer with page numbers.
https://jsreport.net/learn/dotnet-client#pdf-utils
https://playground.jsreport.net/w/admin/kMI4FBmw

The other option is to boot the whole jsreport in the next docker container and communicate with it with jsreport.Client nuget. This option typically scales the best. Example:
https://github.com/jsreport/jsreport-dotnet-example-docker-compose

So we can clean files rapidly, we don't get any implementation and related search for Cleanup Extensions.Reports in latest Jsreport version.

Do you actually use the reports extension and persist reports? Its not very common and you may not need to deal with the mentioned configs.
https://jsreport.net/learn/reports