Qnap Dom Replacement

[Gigí Ruais]

QNAPprovides limited hardware warranty service that covers all our products. The standard warranty comes with no hidden fees or additional costs. Users who want to avail standard warranty services only need to call or email their nearest QNAP retailer.

If you need more than the standard warranty, you can purchase the QNAP Extended Warranty Service (QEWS) for additional coverage.

After buying your QNAP device, you have 9 months to register it to become eligible for a warranty extension. Purchasing an extension can stretch your warranty coverage to up to 5 years.

QNAP's Advanced Replacement Service (ARS) is an optional warranty service that provides advanced product replacement with expedited shipping for up to 5 years. With ARS, QNAP will ship you a replacement device within 48 hours before you send your device to us. The advanced replacement plan is a great option for customers who are seeking for minimized downtime. You can now purchase ARS for your device from any of our authorized resellers.

Users are responsible for backing up all the data stored on their storage devices before returning their products to QNAP as part of the Return Merchandise Authorization (RMA) service. QNAP will not be liable for any data loss during the RMA process.

Please read carefully the terms and conditions of the QNAP Systems, Inc. and its affiliates (hereinafter referred to as "QNAP") official website (link) and Warranty Terms and Conditions (hereinafter referred to as "Term") before purchasing a QNAP product (hereinafter referred to as "Product").

- You can purchase, register and activate an extension warranty on the QNAP official website within 9 months of your Product purchase. Otherwise, you cannot purchase a warranty extension but can still register your Product on the QNAP official website. An original Product invoice is required for a warranty purchase. You must upload your invoice to complete the warranty process.

- QNAP changed the standard warranty period for QNAP devices purchased from January 16th 2019.

Any disputes, claims, or controversies in connection with or arising from the Terms, its construction, existence, interpretation, validity, or any breach hereof which cannot be amicably settled between you and QNAP, will be finally and exclusively resolved by arbitration under the laws of Taiwan, R.O.C. and shall be subject to the jurisdiction of the District Court of Taipei, Taiwan, R.O.C. unless other terms and conditions are applicable in your country.

Please read carefully the terms and conditions of QNAP Systems, Inc. and its affiliates (hereinafter referred to as "QNAP") official website and Warranty Extension Terms and Conditions (hereinafter referred to as "Term") before purchasing a QNAP product (hereinafter referred to as "Product").

Any disputes, claims, or controversies in connection with or arising from the Terms, its construction, existence, interpretation, validity, or any breach hereof which cannot be amicably settled between you and QNAP, will be finally and exclusively resolved by arbitration under the laws of Taiwan, R.O.C. and shall be subject to the jurisdiction of the District Court of Taipei, Taiwan, R.O.C.. unless other terms and conditions are applicable in your country.

QNAP offers a limited warranty service on all of our products, and now provides an extensive 5-year warranty and a free Advanced Replacement service to expedite hardware replacement for selected models. There are no hidden fees and no extra costs; QNAP support is only a phone call or email away.

Please fill out the fields below so we can help you better. Note: you must provide your domain name to get help. Domain names for issued certificates are all made public in Certificate Transparency logs (e.g. crt.sh example.com), so withholding your domain name here does not increase secrecy, but only makes it harder for us to provide help.

There is a problem with your mcnas123.mycloud.com domain. Maybe this is causing your QNAP problem? You are missing an A record in your DNS for this name. You have an A record for your other two names pointing to the same IP. You will need to fix the DNS for this domain if you want to use it from the public internet in any case.

I understand that the message is from QNAP QTS certificate management software.

I have successfully registered a certificate with the QNAP software, but want to add an alternate domain name, so I am trying to replace it unsuccessfully.

I have monitored the traffic with wireshark while I try and register the new replacement certificate.

There is no port 80 traffic, all traffic with the ACME Server is TLS and a around 100+ packets. (possible TLS challenge)

I realise that allsky is not part of the domain name, I added it so anyone can check the domain is accessible. I have nothing at the web root.

nslookup works for me on both domain names and both domains are accessible from the internet.

MPMacMini ddclient % nslookup

My fault Mike, the message I posted first was not correct. I am only using the domain names when attempting to register. I already have a certificate registered to mcnas123.myqnapcloud.com and I am trying to add an alternate name nas.microconcepts.com.au. /allsky is a web site.

The QNAP certificate ssl log reported the following.

It appears the new certificates are being downloaded to temp files and waiting for the challenge to succeed.

check_for_myqnapcloud():check_can_request_cert failed with error code -3006e

get_letsencrypt_download_status():download letsencrypt certificate error with code:-4003

Are these frequency errors?

Of course I see the various failure message they just are too vague to know what they mean. Maybe the QNAP forum has seen these. Or, if they can even describe exactly what the error means. It just looks like: some error, do something, do something, another error, yet another error, do something. As if it does not know how to handle the series of errors and just continues anyway.

I can reach your domains using HTTP and so can Let's Debug test site (link here). So, it's nothing inherent with HTTP (port 80) or the format of the ACME HTTP Challenge. Both your domains respond with the same expected 404 (not found) to these tests

I have been debugging there certficate managment bash shell and python scripts to try and find out why I cannot register a new certificate. I was just checking with the forum if these errors -3006 & -4003 were from the ACME Server, obviously not. There scripts use a letsencrypt_agent_cli binary with no source code.

Both domains work fine on http and https. I have a Lets Encrypt certificate associated with the mcnas123.myqnapcloud.com domain only and it works well, auto renews via crontab.

I am attempting to register without much success another certificate associated with both the qnap and my own domains.

The Web server is built in to QNAPS QTS (a custom linux) I do have control over the apache server via conf files, virtual host files and can restart on demand.

Similar to the previous log, below is all the log entries from 1 attempt to create a certificate.

The QNAP Gui reports "A domain challenge was not received from the ACME Server"

There is no traffic to the ACME server, I watch with wireshark, so it must be an internal limit to stay inside the Lets Encrypt frequency requirements.

I don't know why I forgot to mention this before but you could consider using the mod_md feature in Apache. You just configure a few things right in Apache and it manages and renews the Cert automatically. I am not certain it works in your qnap but I don't know why it would not.

I backed up the exsiting /etc/stunnel/stunnel.pem.

The script "renew_certificate.sh" creates a new combined certificate and overwrites it.

I also added the renewal crontab job as instructed will see if it renews ok on 60 days.

I quickly got a new disk. The old disk was a WD Red 6TB WD60EFRX, the new one is a WD Red 6TB WD60AFEX. I hot-swapped the disks. According to the documentation, the new disk should be detected automatically, and the storage pool should automatically start rebuilding ("Rebuilding" state). But nothing happened.

I checked the UI, Storage & Snapshots tool. The storage pool was still in degraded state, but all four disks were now green and healthy. However, disk 3 was listed as "not a member" of the storage pool. When I selected to Manage the pool, I could do nothing. The only action that was not disabled was "Rebuild RAID Group", but when I tried that there were no free disks to add to the RAID group.

So the problem appeared to be that disk 3 had been detected and was in use, but still it was listed as "not a member" of the storage pool. No actions were available in the UI to fix the situation. Pulling out the disk and inserting it again did not change anything. Googling for help showed that others have encountered similar situations, but no solutions helped me.

For some reason the NAS did not correctly add the /dev/sdc3 disk partition to the storage pool. The disk had been correctly partitioned and the partitions formatted, and the other RAID arrays had apparently recovered, but not /dev/md1. Adding /dev/sdc3 manually to /dev/md1 fixed the problem.

One more thing: it looks like /etc/config/mdadm.conf and /etc/config/raidtab are missing. /etc/mdadm.conf and /etc/raidtab existed as symbolic links to the non-existent files. I'm not sure that they are needed, but as a precaution I created them. mdadm.conf is created like this:

I meet the same problem with my raid 1 (two ssd). When I restart my ts551, one ssd failed. The light is on and the system can read notice this disk, but raise "not a member" error when i try to rebuild raid 1. Neither can i erase it. Then I followed these instructions and it worked!

Thanks for your blog!!!

I had all the same issus as described in the post on QNAP 431P-1. One of the disks (disk 2) had failed, that the storage pool was in a "Degraded" state. Disk 2 shoud have been ok, SMART info all ok. Ran a scan for bad blocks, overnight. Came back ok & disk was green. However the raid would not rebuild & that there were no free disks to add to the RAID group. I would have followed the instructions here, but I was unable to configure SSH on in step 3 below - Unable to get a browser connection to enable SSH. By the time I followed steps 4 through 6 it had started rebuilding.

3a8082e126