I guess I found the root cause. It can be reproduced using wkhtmltopdf 0.12.5 (with patched qt). Reference - https://github.com/wkhtmltopdf/wkhtmltopdf/issues/4545.
Anyway, thank you for the reply.

I have a template which has some links. When clicking on any of this link
<a href="{{:#data.links.linkId}}" target="new"> {{:linkId}}</a>
where linkId is http://localhost:3000/link.html?$url=http%3A%2F%2Flocalhost:3000%2Fdashboard%2Fitems%2Fid1%2Fdefault%2Fid2%2Fid3
the browser opens it as:
http://localhost:3000/link.html?$url=http%253A%2F%252Flocalhost:3000%252Fdashboard%252Fitems%252Fid1%252Fdefault%252Fid2%2Fid3
I.e. it does double encoding - %3A becomes %253A, %2F -> %252F and thus cann't find resource.
Is it a normal behaviour?
Previously, using jsreport 1.10.0 it was working without double encodings in same templates.

I uninstalled all wkhtmltopdf versions locally and then reinstall it by brew cask install wkhtmltopdf and npm install jsreport-wkhtmltopdf
It helped me. Thanks!

I've installed wkhtmltopdf globally wkhtmltopdf --version wkhtmltopdf 0.12.5 (with patched qt)
But UI still shows me only one possible option of wkhtmltopdf version 0.12.3

Yes, I already have got designed reports. Is it feasible to install a particular wkhtmltopdf binary version that can be used by jsreport?If yes, how can I do it?

command npm view wkhtmltopdf version gives me
0.3.4
while in jsreport GUI it is 0.12.3:
Which one does jsreport use?
Because I don't even have 0.12.3
npm view wkhtmltopdf versions outputs:

[ '0.1.0',
'0.1.1',
'0.1.2',
'0.1.3',
'0.1.4',
'0.1.5',
'0.1.6',
'0.2.0',
'0.3.0',
'0.3.1',
'0.3.3',
'0.3.4' ]

jsreport version: 2.6.1 and jsreport-wkhtmltopdf version 2.1.1

1. Will 'wkhtmltopdf' be supported in future ? Because I'm using 'wkhtmltopdf' as a recipe for jsreport:2.6.1 and maybe I need to switch to 'chrome-pdf' recipe.

2. I've got some errors in the 'last failed requests' section:
   But report is successfully rendered despite these errors. Is it something important or I can ignore it?

3. I've noticed that some of my reports generated much faster when I was using jsreport-cli@1.3.2 and jsreport-wkhtmltopdf@1.4.0 in comparison to jsreport-cli: 2.1.1 and jsreport-wkhtmltopdf:2.1.1. Is it related to some configuration of wkhtmltopdf? Any suggestion?

Thank you so much, now it works!

I'm trying to start jsreport using command:
jsreport --dataDirectory ~/projects/jsreport/reports/ start
but the console outputs:
2020-02-11T14:50:16.678Z - info: reporter initialized
2020-02-11T14:50:39.368Z - debug: OData query on templates
2020-02-11T14:50:39.375Z - debug: OData query on folders
2020-02-11T14:50:39.377Z - debug: OData query on tags
2020-02-11T14:50:39.380Z - debug: OData query on data
2020-02-11T14:50:39.381Z - debug: OData query on assets
2020-02-11T14:50:39.382Z - debug: OData query on scripts
2020-02-11T14:50:39.392Z - debug: OData query on xlsxTemplates
2020-02-11T14:50:39.394Z - debug: OData query on schedules
2020-02-11T14:50:39.410Z - debug: OData query on settings
Even going to http://localhost:5488/ there is only samples data. But inside ~/projects/jsreport/reports/ directory there are assets, templates, spripts, data, images, ... and so on.
Previously I was using jsreport-cli@1.3.2 and jsreport@1.10.0 and it worked like a charm using same command jsreport --dataDirectory ~/projects/jsreport/reports/ start
Are there any changes in running jsreport2x?