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.
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.
- Certificate Inspection: On examining the SSL certificate provided by Zebra, I noticed that the Common Name (CN) is set to "BrowserPrint".
- Hosts File Modification: I attempted to map "BrowserPrint" to 127.0.0.1 in my hosts file, then accessed the service using this domain name, but this did not resolve the issue.
- 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.
- 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.
- 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.