Reg: Enquiry Regarding QZ Tray Stability Issues and Free Usage Terms.

[Rajeev Kiran S P]

Dear QZ Tray Team,

We are using QZ Tray in one of our php web applications and would like to seek your guidance regarding a stability issue that has recently started occurring.

Our environment consists of a PHP-based web application that communicates with QZ Tray using the official QZ Tray JavaScript library. Print jobs are sent by passing document URLs to QZ Tray, and the setup has been operating reliably for approximately 2 years. We are currently using a self-generated certificate for signing print requests.

However, over the last two months, we have observed that QZ Tray frequently terminates or deactivates in the system tray while processing print jobs. Restarting QZ Tray restores functionality temporarily, but after a few print operations the issue reoccurs. We have already updated and replaced our certificate, but the behavior remains unchanged.

We would like to understand:

1. Whether there have been any recent changes to QZ Tray's free usage policies, licensing terms, certificate requirements, or security validations that could affect long-running deployments.
2. Whether the observed behavior could be related to the use of a self-generated certificate.
3. If there are any known issues, logs, diagnostic procedures, or recommended troubleshooting steps that could help us identify the root cause.
4. Whether continued use of QZ Tray in a production environment under the free licensing model is still supported without a paid support subscription.

Although we do not currently have a support package, we would appreciate any guidance you can provide regarding this issue and the current usage conditions.

Thank you for your time and assistance. We look forward to your response.

--

Rajeevkiran S P Chief Technical Architect Entro Labs IT Solutions Pvt Ltd +91 7288877889  |  entrolabs.com raj...@entrolabs.com First Floor, Plot No:479,Road No:10, Kakatiya Hills, Madhapur, Hyderabad, Telangana 500081

[Tres Finocchiaro]

Crashes are usually due to bugs with print drivers.

The tip of master branch has a way to show more verbose messaging when printers are crawled:

https://github.com/qzind/tray/issues/830#issuecomment-4240020631

This is available with v2.2.6 though, you'll need to either build the software yourself or snag a build from our CI pipeline (not digitally signed).

Example (these artifacts will disappear after 90 days)

https://github.com/qzind/tray/actions/runs/25874077651#artifacts

--
You received this message because you are subscribed to the Google Groups "qz-print" group.
To unsubscribe from this group and stop receiving emails from it, send an email to qz-print+u...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/qz-print/CAGj5GXL%2Bit3sqz3OXGcjZTmxQC85H24Fv3neYOOMzVgMTJPSdQ%40mail.gmail.com.

[Tres Finocchiaro]

*This is NOT available with v2.2.6 though

[Sireesha Thogunta]

Dear QZ Tray Team,

Thank you for your response.

We performed additional testing on one of our systems. We completely uninstalled QZ Tray, reinstalled it, generated a new certificate, and uploaded the same certificate to our server.

After reinstalling, printing worked normally for some time. We were able to process approximately 25–26 tickets continuously. However, after that, we started experiencing the following issue:

"WebSocket connection to QZ Tray is being closed before the print job completes."

From the browser console, we can see the following sequence:

Established connection with QZ Tray on wss://localhost:8181
Connected to QZ Tray
Printing: ...
Closed connection with QZ Tray
Failed to print document: Error: Connection closed before response received
at qz.websocket.connection.onclose

Once this occurs, printing fails. Restarting QZ Tray restores functionality temporarily, but after several print operations, the same issue reoccurs.

We would appreciate any guidance or troubleshooting steps you can suggest. Please let us know if you require any additional information or logs from our side.

Thank you for your support.

Best regards,
T.Sireesha
Entrolabs It Solutions Pvt. Ltd.

[Tres Finocchiaro]

I'll repeat that crashes are usually due to bugs with print drivers.  My previous reply is still the best advice.

The tip of master branch has a way to show more verbose messaging when printers are crawled: 

https://github.com/qzind/tray/issues/830#issuecomment-4240020631 

 

This is NOT available with v2.2.6 yet though, you'll need to either build the software yourself or snag a build from our CI pipeline (not digitally signed). 

 

Example (these artifacts will disappear after 90 days) 

https://github.com/qzind/tray/actions/runs/25874077651#artifacts

Please reach out to sa...@qz.io about purchasing a support plan if you require more fine grained investigation.

To view this discussion visit https://groups.google.com/d/msgid/qz-print/9fe92080-b70a-411a-b9e4-e82d01fe121cn%40googlegroups.com.