Hi,

Are you encountering an error or is it just not responding? Have you also tried checking the logs? 

In our projects we have always used UltimatePDF. You might want to try it out as well.

If HTML2PDF works correctly in lower environments but fails only in Production using the same payload, then the issue is usually environment-related rather than payload-related.

Check if the HTML2PDF service/API endpoint is reachable from Production.Verify firewall, proxy, or network restrictions in Production.Confirm Production has the same site properties, API keys, licenses, and environment variables as lower environments.Check if there are SSL/TLS certificate issues in Production.Review Production logs for timeout, memory, permission, or authentication errors.If external assets (images, CSS, fonts) are used in the HTML, ensure they are publicly accessible from Production.Compare the HTML2PDF component/library version between environments.Verify if Production has stricter Content Security Policy (CSP) or security headers blocking resources.Check server resource limits because large HTML payloads may fail only under Production load.

Since the same Production payload works successfully in the lower environment, the payload itself is most likely not the problem. The root cause is probably Production configuration, connectivity, or security restrictions.

I have solved the issue.

The root cause is that the file that will be downloaded to the server path (wkhtmltopdf.exe) was corrupted it was under 30MB compare to 39.6MB from github.

Solution was to delete the corrupted (wkhtmltopdf.exe) and rerun the converter as we use the default configuration it will re-download the (wkhtmltopdf.exe) to the server.

Best Regards