Just wanted to report that this was not caused by JsReport but by the pdf viewer I was using. Arggghhhh.

After rereading error messages ... I thinking that Chrome was not installed or not installed properly or path is amiss. Checking to insure Chrome was installed and code is able to find path.

Posting just a portion as it said I did not have permission to upload the file.

2023-11-06T13:49:02.173Z - info: Using general timeout for rendering (reportTimeout: 60000)
2023-11-06T13:49:02.173Z - info: Using fs provider for template store.
2023-11-06T13:49:02.177Z - info: fs store is persisting using fs for /opt/[redacted]/exchange/jobs/services/afc3bce1581e9d63da970c823e33ea03/tmp/data
2023-11-06T13:49:02.183Z - info: fs store is loading data
2023-11-06T13:49:02.199Z - info: fs store is initialized successfully
2023-11-06T13:49:02.209Z - info: Creating default express app.
2023-11-06T13:49:02.215Z - info: jsreport server successfully started on http port: 5488
2023-11-06T13:49:02.215Z - info: Verifying license key 2ABXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX399
2023-11-06T13:49:02.216Z - info: License key for perpetual license verified against /opt/[redacted]/exchange/jobs/services/afc3bce1581e9d63da970c823e33ea03/tmp/jsreport.license.json file
2023-11-06T13:49:05.536Z - info: Initializing worker threads
2023-11-06T13:49:05.836Z - info: 2 worker threads initialized in 299ms
2023-11-06T13:49:05.836Z - info: Starting temp files cleanup with 180000ms threshold
2023-11-06T13:49:05.836Z - info: reporter initialized
2023-11-13T13:07:44.430Z - info: Initializing jsreport (version: 3.8.0, configuration file: jsreport.config.json, nodejs: 16.12.0)
2023-11-13T13:07:44.472Z - info: Using extension base@local:/home/runner/work/jsreport/jsreport/packages/jsreport-base:3.0.1
2023-11-13T13:07:44.477Z - info: Using extension child-templates@local:/home/runner/work/jsreport/jsreport/packages/jsreport-child-templates:3.0.3
2023-11-13T13:07:44.480Z - info: Using extension cli@local:/home/runner/work/jsreport/jsreport/packages/jsreport-cli:3.2.2
2023-11-13T13:07:44.481Z - info: Using extension components@local:/home/runner/work/jsreport/jsreport/packages/jsreport-components:3.2.1
2023-11-13T13:07:44.482Z - info: Using extension data@local:/home/runner/work/jsreport/jsreport/packages/jsreport-data:3.0.1
2023-11-13T13:07:44.482Z - info: Using extension express@local:/home/runner/work/jsreport/jsreport/packages/jsreport-express:3.4.2
2023-11-13T13:07:44.551Z - info: Using extension freeze@local:/home/runner/work/jsreport/jsreport/packages/jsreport-freeze:3.0.1
2023-11-13T13:07:44.552Z - info: Using extension fs-store@local:/home/runner/work/jsreport/jsreport/packages/jsreport-fs-store:3.2.3
2023-11-13T13:07:44.600Z - info: Using extension handlebars@local:/home/runner/work/jsreport/jsreport/packages/jsreport-handlebars:3.2.1
2023-11-13T13:07:44.601Z - info: Using extension import-export@local:/home/runner/work/jsreport/jsreport/packages/jsreport-import-export:3.1.3
2023-11-13T13:07:44.602Z - info: Using extension jsrender@local:/home/runner/work/jsreport/jsreport/packages/jsreport-jsrender:3.0.0
2023-11-13T13:07:44.603Z - info: Using extension licensing@local:/home/runner/work/jsreport/jsreport/packages/jsreport-licensing:3.0.2
2023-11-13T13:07:44.604Z - info: Using extension localization@local:/home/runner/work/jsreport/jsreport/packages/jsreport-localization:3.2.1
2023-11-13T13:07:44.604Z - info: Using extension npm@local:/home/runner/work/jsreport/jsreport/packages/jsreport-npm:3.1.2
2023-11-13T13:07:44.609Z - info: Using extension pdf-utils@local:/home/runner/work/jsreport/jsreport/packages/jsreport-pdf-utils:3.5.0
2023-11-13T13:07:44.610Z - info: Using extension puppeteer-compile@local:/home/runner/work/jsreport/jsreport/packages/jsreport-puppeteer-compile:3.0.2
2023-11-13T13:07:44.611Z - info: Using extension reports@local:/home/runner/work/jsreport/jsreport/packages/jsreport-reports:3.0.7
2023-11-13T13:07:44.613Z - info: Using extension tags@local:/home/runner/work/jsreport/jsreport/packages/jsreport-tags:3.1.1
2023-11-13T13:07:44.614Z - info: Using extension text@local:/home/runner/work/jsreport/jsreport/packages/jsreport-text:3.0.0
2023-11-13T13:07:44.615Z - info: Using extension version-control@local:/home/runner/work/jsreport/jsreport/packages/jsreport-version-control:3.1.2
2023-11-13T13:07:44.622Z - info: Using extension assets@local:/home/runner/work/jsreport/jsreport/packages/jsreport-assets:3.4.4
2023-11-13T13:07:44.630Z - info: Using extension authorization@local:/home/runner/work/jsreport/jsreport/packages/jsreport-authorization:3.2.2
2023-11-13T13:07:44.632Z - info: Using extension browser-client@local:/home/runner/work/jsreport/jsreport/packages/jsreport-browser-client:3.1.1
2023-11-13T13:07:44.633Z - info: Using extension chrome-pdf@local:/home/runner/work/jsreport/jsreport/packages/jsreport-chrome-pdf:3.2.0
2023-11-13T13:07:44.636Z - info: Using extension docx@local:/home/runner/work/jsreport/jsreport/packages/jsreport-docx:3.5.1
2023-11-13T13:07:44.638Z - info: Using extension html-to-xlsx@local:/home/runner/work/jsreport/jsreport/packages/jsreport-html-to-xlsx:3.2.3
2023-11-13T13:07:44.642Z - info: html-to-xlsx detected chrome as available html engine
2023-11-13T13:07:44.642Z - info: html-to-xlsx detected phantom as available html engine
2023-11-13T13:07:44.642Z - info: Using extension pptx@local:/home/runner/work/jsreport/jsreport/packages/jsreport-pptx:3.2.1
2023-11-13T13:07:44.643Z - info: Using extension scheduling@local:/home/runner/work/jsreport/jsreport/packages/jsreport-scheduling:3.0.3
2023-11-13T13:07:44.665Z - info: Using extension scripts@local:/home/runner/work/jsreport/jsreport/packages/jsreport-scripts:3.2.1
2023-11-13T13:07:44.665Z - info: Using extension static-pdf@local:/home/runner/work/jsreport/jsreport/packages/jsreport-static-pdf:3.0.0
2023-11-13T13:07:44.666Z - info: Using extension xlsx@local:/home/runner/work/jsreport/jsreport/packages/jsreport-xlsx:3.2.3
2023-11-13T13:07:44.679Z - info: Using extension public-templates@local:/home/runner/work/jsreport/jsreport/packages/jsreport-public-templates:3.0.0
2023-11-13T13:07:44.680Z - info: Using extension sample-template@local:/home/runner/work/jsreport/jsreport/packages/jsreport-sample-template:3.2.1
2023-11-13T13:07:44.681Z - info: Using extension studio-theme-dark@local:/home/runner/work/jsreport/jsreport/packages/jsreport-studio-theme-dark:3.0.1
2023-11-13T13:07:44.681Z - info: Code sandboxing is disabled, users can potentially penetrate the local system if you allow code from external users to be part of your reports
2023-11-13T13:07:44.681Z - info: Using general timeout for rendering (reportTimeout: 60000)
2023-11-13T13:07:44.681Z - info: Using fs provider for template store.
2023-11-13T13:07:44.685Z - info: fs store is persisting using fs for /opt/[redacted]/exchange/jobs/services/afc3bce1581e9d63da970c823e33ea03/tmp/data
2023-11-13T13:07:44.688Z - info: fs store is loading data
2023-11-13T13:07:44.705Z - info: fs store is initialized successfully
2023-11-13T13:07:44.715Z - info: Creating default express app.
2023-11-13T13:07:44.721Z - info: jsreport server successfully started on http port: 5488
2023-11-13T13:07:44.722Z - info: Verifying license key 2ABXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX399
2023-11-13T13:07:44.723Z - info: License key for perpetual license verified against /opt/[redacted]/exchange/jobs/services/afc3bce1581e9d63da970c823e33ea03/tmp/jsreport.license.json file
2023-11-13T13:07:44.726Z - info: Initializing worker threads
2023-11-13T13:07:45.068Z - info: 2 worker threads initialized in 342ms
2023-11-13T13:07:45.069Z - info: Starting temp files cleanup with 180000ms threshold
2023-11-13T13:07:45.069Z - info: reporter initialized
2023-11-20T09:04:38.340Z - info: Render request 1 queued for execution and waiting for available worker fromEmitProfile=true, rootId=zuboxr2wfw58doj, id=zuboxr2wfw58doj
2023-11-20T09:04:38.402Z - info: Starting rendering request 1 (user: null) rootId=zuboxr2wfw58doj, id=zuboxr2wfw58doj, fromEmitProfile=true
2023-11-20T09:04:38.403Z - info: Rendering anonymous template { recipe: chrome-pdf, engine: handlebars } rootId=zuboxr2wfw58doj, id=zuboxr2wfw58doj, fromEmitProfile=true
2023-11-20T09:04:38.981Z - error: Error when processing render request 1 Failed to launch the browser process! spawn /tmp/jsreport/compile/jsreport-3.8.0-woqH9PT5c/chrome/chrome ENOENT


TROUBLESHOOTING: https://github.com/puppeteer/puppeteer/blob/main/docs/troubleshooting.md
 Error: Failed to launch the browser process! spawn /tmp/jsreport/compile/jsreport-3.8.0-woqH9PT5c/chrome/chrome ENOENT


TROUBLESHOOTING: https://github.com/puppeteer/puppeteer/blob/main/docs/troubleshooting.md

    at onClose (/snapshot/jsreport/node_modules/puppeteer/lib/cjs/puppeteer/node/BrowserRunner.js:289:20)
    at ChildProcess.<anonymous> (/snapshot/jsreport/node_modules/puppeteer/lib/cjs/puppeteer/node/BrowserRunner.js:283:24)
    at ChildProcess.emit (node:events:390:28)
    at ChildProcess.emit (node:domain:475:12)
    at Process.ChildProcess._handle.onexit (node:internal/child_process:288:12)
    at onErrorNT (node:internal/child_process:477:16)
    at processTicksAndRejections (node:internal/process/task_queues:83:21) rootId=zuboxr2wfw58doj, id=zuboxr2wfw58doj, fromEmitProfile=true
2023-11-20T09:04:38.982Z - error: Rendering request 1 finished with error in 643 ms rootId=zuboxr2wfw58doj, id=zuboxr2wfw58doj, fromEmitProfile=true
2023-11-20T09:04:38.984Z - error: Error during processing request at http://localhost:5488/api/report
2023-11-20T09:10:31.563Z - info: Render request 2 queued for execution and waiting for available worker fromEmitProfile=true, rootId=uvnbcncmdn04yyj, id=uvnbcncmdn04yyj
2023-11-20T09:10:31.582Z - info: Starting rendering request 2 (user: null) rootId=uvnbcncmdn04yyj, id=uvnbcncmdn04yyj, fromEmitProfile=true
2023-11-20T09:10:31.583Z - info: Rendering anonymous template { recipe: chrome-pdf, engine: handlebars } rootId=uvnbcncmdn04yyj, id=uvnbcncmdn04yyj, fromEmitProfile=true
2023-11-20T09:10:31.640Z - error: Error when processing render request 2 Failed to launch the browser process! spawn /tmp/jsreport/compile/jsreport-3.8.0-woqH9PT5c/chrome/chrome ENOENT


TROUBLESHOOTING: https://github.com/puppeteer/puppeteer/blob/main/docs/troubleshooting.md
 Error: Failed to launch the browser process! spawn /tmp/jsreport/compile/jsreport-3.8.0-woqH9PT5c/chrome/chrome ENOENT


TROUBLESHOOTING: https://github.com/puppeteer/puppeteer/blob/main/docs/troubleshooting.md

    at onClose (/snapshot/jsreport/node_modules/puppeteer/lib/cjs/puppeteer/node/BrowserRunner.js:289:20)
    at ChildProcess.<anonymous> (/snapshot/jsreport/node_modules/puppeteer/lib/cjs/puppeteer/node/BrowserRunner.js:283:24)
    at ChildProcess.emit (node:events:390:28)
    at ChildProcess.emit (node:domain:475:12)
    at Process.ChildProcess._handle.onexit (node:internal/child_process:288:12)
    at onErrorNT (node:internal/child_process:477:16)
    at processTicksAndRejections (node:internal/process/task_queues:83:21) rootId=uvnbcncmdn04yyj, id=uvnbcncmdn04yyj, fromEmitProfile=true
2023-11-20T09:10:31.641Z - error: Rendering request 2 finished with error in 77 ms rootId=uvnbcncmdn04yyj, id=uvnbcncmdn04yyj, fromEmitProfile=true
2023-11-20T09:10:31.643Z - error: Error during processing request at http://localhost:5488/api/report

It seems JsReport is not working if air gapped. I am getting a failure from jsreport as it cannot reach
https://cdn.jsdelivr.net/npm/pdfjs-dist@2.13.216/legacy/build/pdf.worker.min.js

This is on a server so I just installed Chrome. Thus can I either tell jsReport to tell Chrome not to reach out to go get that file or maybe install Chrome so it does not need it or does not go looking for it.

Thanks, James

<a href="javascript:void(0)">https://www.jsreport.net</a>

Definitely another good solution. Thanks again for your help.

I think I have found a couple of solutions playing around in playground. Seems to work ... not perfect as it still acts like it is a link but I think I can use some css to prevent that also.

Should have given you a playground. https://playground.jsreport.net/w/jamesstacyjones/Xl8QbEht.

We defang our links as our reports will have malicious links for an analyst to review ... but we defang then so they are not clickable in the html.

In my testing sometimes the pdf software that opens up the pdf obeys the html sometimes it does not:
Chrome : converted to hyperlink:

• Edge: converted to hyperlink
• Firefox: defanged hyperlink
• Mac Preview: converted to hyperlink
• Adobe Acrobat: defanged hyperlink

And in the playground I made above ... they are converted to hyperlinks. Was wondering if there is a way to prevent them from being clickable or converted.

I am trying to prevent links in my pdf ... so I defanged all my hyperlinks to just be text like https://www.something.com ... took away the href tag in the html. Works when printing out html and also in the pdf viewer. But as soon as I open the pdf with Chrome or Mac Preview the link is back.

Is there setting under pdf utilities I am missing to prevent this or some other trick to prevent hyperlinks from working.