Private PDF generation module error

0
Hi Team, I am using PDF generation module (version 2.1.4). My application is deployed in mendix private cloud and I am trying to use the private pdf generation service hosted in the private cloud. I am getting below error in the acceptance environment while calling the javaaction 'Generate PDF from Page'. DOCGEN_NAVIGATION_ERROR: Failed to navigate to page due to an error: net::ERR_BLOCKED_BY_CLIENT at http://xxxxx-mx.siemens-energy.cloud/docgen/generate?id=xxxxxxxxxxxxxxxxxxx. Does anyone have any idea about this error?   Regards, Megha  
asked
1 answers
0

Hi Megha,


The error DOCGEN_NAVIGATION_ERROR: net::ERR_BLOCKED_BY_CLIENT indicates that the Chromium browser used by the PDF generation service could not navigate to the specified /docgen/generate URL. The error alone does not identify exactly what blocked the request.


Since you are using the Private PDF Document Generation Service, I would check these items in order:


1. Verify the application URL and HTTPS configuration

The URL in the error appears to use http://. Check whether this is the actual URL configured for your Acceptance application.

  • If Acceptance is intended to use HTTPS, ensure the application URL and reverse-proxy configuration use the correct HTTPS address.
  • If the private service connects through a custom or self-signed certificate, ensure the service trusts that certificate.
  • Check whether the application URL redirects to another host or URL.


2. Verify that the /docgen/ endpoint is accessible

Check your reverse proxy, ingress, or gateway configuration to ensure that requests to /docgen/ are forwarded correctly to the Mendix runtime.

Also verify that the PDF generation container can reach the Acceptance application's hostname and that network rules permit the required communication in both directions.


3. Verify the private service configuration

In the Mendix application, check these constants:

  • DocumentGeneration.OverrideServiceType = Private
  • DocumentGeneration.ServiceEndpoint = the reachable address of the private PDF generation service, including its port where applicable.

For example, the service endpoint might be http://document-generation:8085 when the container is reachable through that hostname on the application network.

Do not use localhost unless the service and application genuinely share the same network namespace and the endpoint is reachable there.


4. Inspect the PDF generation service logs

Reproduce the issue and inspect the private PDF generation container logs. Look for the original navigation error, failed requests, DNS failures, TLS errors, and any proxy or network restrictions.

You can also test the service's health endpoint at /health to confirm that the container is running. A healthy container alone does not prove that it can reach your Mendix application.


5. Test the same page directly

Open the page being generated in a browser using the same application environment and verify that it loads without authentication redirects or other navigation changes. Check that the configured document user has the necessary permissions.


Official references:


My recommendation: Start by verifying the URL scheme and the /docgen/ reverse-proxy/network configuration, then inspect the service logs. These checks will help identify whether the issue is caused by URL redirection, certificate trust, or connectivity between the private service and the Acceptance environment.


Hope this helps!

answered