Assistance Requested: Resolving net::ERR_CERT_COMMON_NAME_INVALID with Zebra Browser Print on Localhost

// Expert user has replied.
B Ben Waters 6 months 2 weeks ago
150 2 0


I am currently engaged in developing a web application that interfaces with Zebra Browser Print to dispatch print jobs via ports 9101/9100. However, I am encountering a persistent issue related to SSL certificate validation.

Issue Description:

Whenever my application initiates a request to localhost:9101, it results in a net::ERR_CERT_COMMON_NAME_INVALID error. This occurs across various methods invoked within the application.

Steps Taken:

  1. Certificate Inspection: On examining the SSL certificate provided by Zebra, I noticed that the Common Name (CN) is set to "BrowserPrint".
  2. Hosts File Modification: I attempted to map "BrowserPrint" to in my hosts file, then accessed the service using this domain name, but this did not resolve the issue.
  3. Certificate Installation: I exported the Zebra-provided certificate and installed it into my system's trusted certificates store. Despite this, the ERR_CERT_COMMON_NAME_INVALID error persists.
  4. Temporary Workaround: Currently, to temporarily bypass the issue, I manually navigate to localhost:9101/ssl_support during each session, which is not a feasible long-term solution.
  5. Certificate Regeneration: I have also tried deleting the existing key in the BrowserPrint folder to trigger certificate regeneration, but this did not rectify the problem.

Request for Assistance:

I am seeking insights or solutions from anyone who has successfully integrated Zebra Browser Print in a similar environment or has expertise in handling such SSL certificate issues in a development setting. Any guidance on how to permanently resolve this certificate error would be greatly appreciated.

Thank you for your time and assistance.

Best regards,


Please register or login to post a reply

2 Replies

A Ajay Patel

I am also facing the same issue. try to fix with custom generated ceritificate but it is not working for me either.

S Steven Si

To use the Browser Print, a Browser Print client app is required to be installed on a local computer or Android device. The Browser Print client app acts as a mini webserver, so that the customer web application can interact with the Browser Print client app via the JavaScript API calls provided in the Browser Print JavaScript library for the server. During the installation of the Browser Print client app, a new certificate is created automatically. When the certificate expires after 2 years, a new certificate will be generated automatically if we delete the keystore.jks file and relaunch the Browser Print client app. This certificate is transparent from the user and user's web application, and should not be tempered with. The application only needs to call the JavaScript API provided by the Browser Print JavaScript library. To test how the Browser Print works, just install the Browser Print client app on a computer or Android device, and then open the, hosted as HTTPS, from the browser.

Can’t find what you’re looking for?