Hello,
I want to use Browser Print soft for and label print from my website.
I notices it works only when website is accessible with HTTP protocol.
If I use HTTPS, even BrowserPrint.getDefaultDevice fires an error.
I can see in BrowserPrint-1.0.4.min.js code that when this library is called from the website with "https://" url,
it tries to connect with https://localhost:9101/
But there is no SSL certificate on https://localhost:9101/ and I guess browser refuses connection.
Can you help me to configure SSL certificate for https://localhost:9101/ in Browser Print service?
Best regards,
Jakub
HTTPS and Browser Print |
3 Replies
In my case, Able to print the labels when connected to the printer from development server which is using http protocol.
But when tried to print from the server which is using https protocol, receiving the error
Failed to write to device: connection refused
Tried clearing chrome cache but still getting the same error.
Can't we connect to printer from server using https. If we can connect from https server then what are steps that need to be followed to make it work.
Hi Jakub,
The SSL certificate is supposed to be installed automatically after you accept the EULA at installation. From the user guide page 6:
If there was an issue with the initial installation and you did not see this, you can navigate to the following page to manually allow it locally.
https://localhost:9101/ssl_support
You can also try to uninstall and reinstall Browser Print.
Hi Jakub,
Has the problem solved? Able print label in https?
Recently I have similar issue about unable to print label in https, but able to print in http.
I also have tried the suggestion above, to reinstall the Browser Print, accept the SSL certificate prompt and manually browse the URL https://localhost:9101/ssl_support. Both of them result to the page "SSL Certificate Has been accepted. Retry connection." but the URL is still Not Secure and I am unable to print label. I am using latest Browser Print version 1.3.1.445 and Chrome version 110.0.5481.177. I am not sure the suggestion above still applied to the latest version and Chrome browser.
Patrick