Printing from web ExpressCheck 7.8 using QZ Tray

Our library is moving from on-premise hosted Polaris 7.5 to cloud hosted 7.8. We’ve been using Leap for a while but this is our first experience moving away from local app-based ExpressCheck to the new web based version.

Currently our test server is set up and we’re trying to get things configured. The best instructions I’ve found so far are here. I got QZ Tray installed on a test machine, added our printer cert, got into the web admin and set the Direct to Printer defaults, then popped over to Leap and looked at the settings.

When I check ‘Direct to printer’ and click CONNECT it returns QZ Tray successfully connected. I can print a test receipt, and when I check an item out it prints a receipt as expected.

Then I jumped over to the ExpressCheck preferences page and see a very similar setup, where ‘localhost’ is in the Connect to host text box. Only here when I click CONNECT I get ‘Error getting printer certificate from API.’

Anyone successfully navigated this? Do I just need to install a single certificate into QZ Tray that should work for both? Or does ExpressCheck need its own? Is there some config setting in the web admin that I’m missing similar to the one I had to turn on for Leap?

Any help would be appreciated.

Hi Gabe,

We did get ExpressCheck (web) setup and tested with the certificate that Innovative provided. When we engaged with them for a certificate for use with Leap - Direct to Printer, they said it was the same certificate we used with ExpressCheck. We are still testing but it does appear to work but oh my, what a pain to deploy…

Hope you get it all setup, and it works for you!

We have been talking with QZ about using their premium support program, which might allow you to streamline the certificate deployment. It might cost some $$$ annually, but is likely to save a lot in terms of deployment headaches. We’re still in early stages of the process, but will share any updates as we move forward with the process.

2 Likes

In case other folks end up going through the same issue… Turns out the problem was on the server end. Something needed to get copied over, and it seems like maybe there were multiple locations for both Leap and ExpressCheck. The first worked but the second didn’t copy correctly. The Polaris tech working with us fixed it on his end and printing started working without me doing anything else.

Aside from that issue the process was smoother than I would have thought. If the server side was all set up correctly it was just a case of installing QZ tray on the machine, adding the certificate, and then in the Leap and ExpressCheck settings just hitting the ‘Connect’ button and picking the receipt printer from a list. They both seem to be working correctly. (Fingers crossed they stay that way)

1 Like