Re: Lets Encrypt Port 80 issue
Posted: Sat Mar 28, 2020 5:59 am
Hey,
I came across this thread whilst looking into this problem myself and I can say that after much frustration I have managed to get a valid Lets Encrypt certificate using the "certificate & keys" section.
My nas has both port 80 and 443 forwarded, always has done, so I know thats not the problem. I had the UI listening on 80 and 443 with HTTPS forced, however to fix the certs I had to change that.
To get it working I had to set the built in web server (under network & file services) to run on port 80 (no need to enable SSL) then run this tool, it took a while to get the certificate the first time but eventually worked (it was likely checking for each of my aliases I presume).
I can repeat this with success, I currently have my "qnapcloud" domain as the common name, then 3 aliases separated by commas in the alt name field, works like a charm so far.
Hope this helps anyone having similar issues!
I came across this thread whilst looking into this problem myself and I can say that after much frustration I have managed to get a valid Lets Encrypt certificate using the "certificate & keys" section.
My nas has both port 80 and 443 forwarded, always has done, so I know thats not the problem. I had the UI listening on 80 and 443 with HTTPS forced, however to fix the certs I had to change that.
To get it working I had to set the built in web server (under network & file services) to run on port 80 (no need to enable SSL) then run this tool, it took a while to get the certificate the first time but eventually worked (it was likely checking for each of my aliases I presume).
I can repeat this with success, I currently have my "qnapcloud" domain as the common name, then 3 aliases separated by commas in the alt name field, works like a charm so far.
Hope this helps anyone having similar issues!