Documentation

Certificate Renewal

Compatibility

  • ✅ 2.2 | ✅ 2.1 | ✅ 2.0 | ✅ 1.9 | ...

Background

  1. Renewals only. For new orders, see generate certificate steps instead.
  2. Any remaining days on your previous certificate will roll into the renewed certificate.
  3. Renewal discounts are applied automatically. Contact support with any questions.
  4. Multi-year discounts are applied automatically. Contact support with any questions.

Steps

Renew License

  1. Navigate to https://buy.qz.io/myaccount.asp (alternatively, https://buy.qz.io and click "My Account" at the top of the screen)

  2. Once signed in click "Buy Now" at the top of the screen.

  3. Select ADD TO CART on the appropriate product (Premium Support -- or -- Company Branded + Premium Support)

  4. Enter in the desired years you wish to purchase and select PROCEED TO CHECKOUT.


    Note: Price should be discounted for renewals, reach out to support if a discount does not display.

  5. IMPORTANT: Towards to bottom of the page, there will be a section to add in your current product key. After putting in your product key, along with all of the other required information, select CHECKOUT

  6. You will be emailed and assigned a new product key. Any remaining days on your previous certificate will roll into the renewal.

Renew Certificate

  1. Log in here https://qz.io/login/ using your email and newly assigned product key

  2. Select QZ Tray

    image
  3. If you do not need to change any of the information on the certificate from the previous year (e.g. Company Name), it is recommended to click the "Renew certificate" button at the top of the page. This is the recommended option, only digital-certificate.txt needs to be replaced on the server.

    image
  4. Alternately, if you need to change the information, click "Show other options" and take the default settings.

    image

Replacing Certificate

  • Use the digital-certificate.txt on your website in place of the old copy(s)

    • The certificate is generally located in a public directory accessible by JavaScript $.ajax() or fetch().
    • Find and replace digital-certificate.txt on your web server.
      • If the contents of this file were instead pasted directly into code, search project for -----BEGIN CERTIFICATE-----.
    • Since QZ Tray 2.0.8, simply replacing digital-certificate.txt is all that is needed.

    Replacing Certificate (Deprecated)

    Websites that were integrated prior to QZ Tray 2.0.8 may need to manually clear the cache.

    Click here to expand steps
    • ⚠️ WARNING: The ?modify_url technique is available for historical purposes and discouraged. Instead, please use a cache flag for $.ajax(), fetch(), etc.

    • You can force a reload of the cache by modifying the URL. e.g.

      - http://foo/bar/digital-certificate.txt
      + http://foo/bar/digital-certificate.txt?modify_url
    • If the above URL is referenced from a JavaScript file, the script file may need to be force refreshed as well, e.g:

      - <script src="foo/bar/myscript.js"></script>
      + <script src="foo/bar/myscript.js?modify_url"></script>

Verifying Certificate

To ensure that the certificate has been replaced properly, you must visit a webpage which uses QZ Tray.

  1. Visit a webpage which uses QZ Tray AND uses the recently deployed certificate.
  2. Ensure QZ Tray is functioning properly by listing printers or doing a test print.
    (You may also use serial, USB or file communication as a test.)
  3. ⚠️ IMPORTANT: From the QZ Tray menu:
    1. Click Advanced > Site Manager
    2. Ensure the "Valid To" date is correctly updated
      Screenshot 2023-07-27 at 12 57 52 PM
    3. If the certificate was replaced properly there will be no warnings when printing. If you receive a message Expired certificate or Invalid signature, please reach out to support immediately for assistance.

Replacing Private Key

Most renewals will re-use the old private-key.pem or private-key.pfx. These steps are provided ONLY in the event that the private-key.pem or private-key.pfx was replaced as part of the renewal process. Do NOT perform these steps unless you explicitly generated a new private key above.

Click here to expand steps
  • If a new private-key.pem or private-key.pfx was generated above replace this as well. This varies per-platform. Please contact a developer and place support@qz.io on copy of communications.
  • The private key is generally located in a non-public directory, used by a signing mechanism. This is generally referenced in a file named sign-message.php or similar.
  • If the contents of the private key were instead pasted directly into code, search project for -----BEGIN PRIVATE KEY-----.

Questions, comments or concerns, please contact support

Edit this page