Loading external files fails when printing from in-memory HTML about chromic_pdf HOT 2 CLOSED

Hey @Zelzahn,

the error sure looks like Chromium isn't loading your asset due to the failed TLS peer verification. I would also expect --ignore-certificate-errors in :chrome_args to fix this, but I've never tried this and can't say why it doesn't work. Perhaps it conflicts with one of our default command line args, but not sure.

Besides debugging --ignore-certificate-errors and making it work with ChromicPDF), here are a few options to solve your issue differently:

1. Make Chromium accept your self-signed certificate. However, Chromium uses its own certificate store instead of your OS's, and the recommended method to add self-signed certificates is quite cumbersome, so this path may turn out expensive given you don't gain much besides a local TLS connection.
2. Don't use a local TLS connection. For instance, you can give chromium its own (non-https) Phoenix endpoint to connect to. You should be able to reuse your existing routers + views for this (i.e. share them with your public https endpoint). Make sure to bind to 127.0.0.1 only if this is a public host.
3. Serve the assets differently, e.g. use file:/// paths or embed them as data-uris.

Personally, I'd explore option 2 first. Hope this helps.

malte

from chromic_pdf.

Thanks for the swift reply! I'll try the second option, hopefully it'll then work 😄

from chromic_pdf.