Certificate Renewal - sdon2/thermal-printer-tray GitHub Wiki

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

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 [email protected] with any questions.
4. Multi-year discounts are applied automatically. Contact [email protected] with any questions.

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 [email protected] 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.

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

   

2. Select QZ Tray

   

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 easiest option, as only 1 file (digital-certificate.txt) needs to be replaced on the server.

   

4. Alternately, if you need to change the information and still have the public-key.txt, follow these steps:

   Change Certificate Information Using Public Key

   Click here to expand steps

   • These steps should ONLY be required if you wish to change information on the certificate.
   • Click "Please generate the CSR for me"
   • Click "I already have a public/private key pair that I want to use for signing."
   • Copy and paste the contents of the public-key.txt into the box.
     • ⚠️ WARNING: Do NOT paste your private-key.pem, it will result in a bad certificate!
   • Fill out the required information, then hit Submit request
   • After a few seconds a new field will appear at the bottom of the page. Download the public key, private key, and certificate
     • Note: PKCS#12 format is required for .NET, while PEM format is required by most other environments

5. Alternately, if you need to change the information and do NOT have the public-key.txt, follow these steps:

   Change Certificate Information Without Public Key

   Click here to expand steps

   • These steps should ONLY be required if the public-key.txt is lost AND you wish to change information on the certificate.
   • Click "Please generate the CSR for me."
   • Click "I don't have a key pair yet. Please generate one for me."
   • Fill out the required information, then hit Submit request
   • After a few seconds a new field will appear at the bottom of the page. Download the public key, private key, and certificate
     • Note: PKCS#12 format is required for .NET, while PEM format is required by most other environments

• 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>

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 [email protected] 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-----.

• The public-key.txt does not need to be replaced as it is not needed for signing or licensing. Hang onto this file for edge-case reissuance.

Questions, comments or concerns, please contact [email protected].