Skip to content

myQNAPcloud certificate deadline has passed: verify replacement

QNAP's November 4 notice scheduled revocation of TWCA's previous intermediate certificates for November 5, 2026 at 16:00 UTC. That scheduled time has passed; we have not independently confirmed completion. QNAP notice.

Who needs to check

QNAP identifies certificates purchased through QNAP for xxxx.myqnapcloud.com or xxxx.mycloudnas.com and issued before November 1, 2026 at 00:00 UTC. Update SSL Certificate to 2.2.80 or newer, including after the deadline. QNAP says replacement runs automatically within 0–4 hours while online. Let's Encrypt, manually uploaded and default self-signed certificates are excluded. QNAP scope and recovery FAQ.

Verify the certificate being served

At your myQNAPcloud domain, check the certificate's issue date: November 1, 2026, 00:00 UTC or later. The new Authority Key Identifier (AKI) starts 93:44:9A:89; issuer name alone is insufficient. QNAP verification instructions.

TWCA attributes the change to certificate serial-number randomness requirements, not intrusion or leaked private keys. TWCA explanation.

Suggested checks after the update

The practical goal is to confirm what users actually reach. These are our suggested checks, not a report of testing:

  1. List the affected connections. Record which NAS name each browser, sync client and scheduled job uses. Assign someone to check each route.
  2. Keep a small change record. Record the app version, update time, certificate details and observed connection result. Keep credentials and private keys out of tickets and screenshots.
  3. Test a representative workflow. Confirm a routine, non-sensitive read or sync works from a normal client. An installed app update alone does not demonstrate that every dependent workflow has recovered.
  4. Keep certificate validation enabled. If a warning blocks access, use an already trusted management route or seek support. Do not bypass warnings, downgrade to HTTP or open new inbound ports to get around the problem.

We reviewed the published notices; we have not inspected a reader's NAS, observed the revocation or tested replacement. Diagnose any continuing failure rather than assuming this notice explains every connection error.

לקריאה בעברית

Post a Comment

Previous Post Next Post