QTSCloud c5.2.4.3041
We have been using LetsEncrypt certificates for years. renewing every 90 days or so.
Now we cannot renew… the NAS reports:
[Authentication Fails: Please check DNS server ot if the Port 80 is working.]
We CAN access the NAS via port 80 on the FQDN.
This is NOT unique to one NAS. We have the issue on Two separate NAS in two different locations.
The Firmware was updated in March and this is the first time we have tried to renew the certificate.
Could you please let us know which version of the QTS SSL Certificate you are currently using?
SteveKo, Many thanks for your reply:
myQNAPcloud: 1.1.69
SSL Certificate: 2.2.62
We do not use myQnapCloud as the certificate is for the NAS own FQDN.
Cheers
Do you have your NAS exposed to the public internet? That’s not something that is recommended. Lots of attacks have happened to NAS users who have their units exposed…
Same error message here! I have a ticked open on QNAP-Support. No helpful answers until now. My Lets Encrypt Certificate is for “MyServer.spdns.de”, not the QNAPcloud Certificate.
I have the same problem with my dyndns-domain. Until now my certificate is just valid until july 5th.
Since i pressed the renew button in Qnap the SSL-App tells me I even don’t have a certificate anymore.
To help clarify the issue you’re experiencing, please open a support ticket with us. Our Support Team will be able to assist you in troubleshooting and understanding the problem.
Support Ticket Raised.
I raised ticket Q-202506-18044 and by remote i got installed a *.myqnapcloud.com domain cert by a supporter even before I used a DynDNS.org domain.
Now all my connections of course don’t work anymore.
I tried by myself to set back everything and create a new dyndns-certificate again - but still the same behaviour.
When I tried to recreate the before myqnapcloud certificate again this was installed and running.
To me it seems there is a problem in creating or renewing at least with dyndns - maybe with all other domains beside myqnapcloud.com?
Hi @WeT-Klb,
We’ve been investigating this issue as well and found that Let’s Encrypt has recently made some changes to their certificate issuance process, which appear to affect how certificates are generated and renewed—especially when using custom DDNS domains.
The good news is that SSL Certificate version 2.2.63, which is scheduled for release this week, will include a fix that resolves the issue with importing and renewing Let’s Encrypt certificates for custom domains.
In the meantime, if necessary, use the temporary *.myqnapcloud.com certificate for access.
Thanks for this information. I am looking forward to try the new App.
It’s only pity to see the first problems with renewing custom domains already appeared in january.
@Andy2
Hello, I just wanted to ask if the new app still is scheduled for this week. Today it’s already thursday and still nothing new out yet.
Hi @Andy2 ,
We are also experiencing the same issue on multiple Qnap devices. Looking forward to seeing if the 2.2.63 release fixes the issue.
Thank you
All of our Qnap NASes are also failing to update the LetsEncrypt certificates. Any word on when this will be fixed?
Same here, I have 2 QNAP NAS, both can´t renew let`s encrypt certificates. It was working for years and nothing besides QTS Updates was changed.
PS:
I am using the “normal” renew option in the control panel, no separate app.
I do not use an SSL App, just the “renew option” in the control panel. Will this also get fixed? Also I do not use and do not want to use QNAP Cloud or QNAP SSL, just Let´s Encrypt.
Same here, waiting for QTS SSL 2.2.63
Same problem this morning my renewall periode is 7/6 and today i have ssl error. ssl version is 2.2.62 i rebooted , i stop and start services nothing append, alaways same error with the 80 port . The stability of Qnap cause me a lot of trouble . i will finish to change for concurent . i can’t establish a company strategie based on this type of product . the support is more than random, or vegas money machine. i have something like 10 qnap in production i have 3 ssl error and of course all services based on it in error . i have on the side a truenas project comparativly i never reboot it since 500 days , ssl always up , upgrade done by maintenance , exactly like qnap .
Same here, waiting for QTS SSL 2.2.63
Just when I need to deploy Nextcloud on my own domain…what’s taking so long?