Closed UjjualUSspericorn closed 2 years ago
I have the same issue
Same problem, but from my Heroku instance. Locally on the dev server it's ok.
Does not solve the issue on my side.
localUrlAccess: true
I have remote images from CDN, instead of them I see "?" question marks.
Probably relates more to phantomJS/Node version. Any advice on where to dig it?
I am facing the same issue. My html-pdf package is locked at 2.1.0
I have the same issue does anyone have a resolve for this?
This might be linked to the recent expiry of letsencrypt root certificate. In our experiments, we found out that using request.get()
with node version v6.10.0 was throwing the error certificate has expired
but it was working fine with node version v14.17.1.
I believe that older version of node might be using some old certificates.
For a quick fix, you can set phantomArgs
to --ignore-ssl-errors=yes
in the config object passed to create()
.
@ashishmadeti be prepared for a lot of thumbs up 👍
For a quick fix, you can set
phantomArgs
to--ignore-ssl-errors=yes
in the config object passed tocreate()
.
@ashishmadeti I really appreciate you for you tip. It helped me in my case.
But update to Node v14.18.0 didn't help me. Only --ignore-ssl-errors=yes
saved my day.
@TrumanRu where do we add this can you show some code?
"phantomArgs": [], // array of strings used as phantomjs args e.g. ["--ignore-ssl-errors=yes"]
@TrumanRu where do we add this can you show some code?
htmlPdf.create(html, {
type: 'png',
quality: 75,
zoomFactor: 0.5,
timeout: 120000,
phantomArgs: ['--ignore-ssl-errors=yes'],
});
This might be linked to the recent expiry of letsencrypt root certificate. In our experiments, we found out that using
request.get()
with node version v6.10.0 was throwing the errorcertificate has expired
but it was working fine with node version v14.17.1. I believe that older version of node might be using some old certificates.For a quick fix, you can set
phantomArgs
to--ignore-ssl-errors=yes
in the config object passed tocreate()
.
Saved our day
It worked.!
It worked! +1
It was working fine till few weeks ago .Now the image appears like this. I have checked whether the url is valid.
@alexbor