HTTPS Certificate Configuration (Version 4.x and newer)

Xela

Well-Known Member
Oct 12, 2017
98
2
48
Hi there,

I followed first the instructions from the Wiki for Web Interface Via Nginx Proxy.
After that I moved over to the HTTPS Certificate Configuration.
1) Install acme.sh = ok
2) Run the install script = ok
3) Check the account config = ok
4) Make sure port 80 is open from the public = has a redirect to https 443
5) Issue your first certificate:

[Sat 14 Oct 12:16:54 UTC 2017] Standalone mode.
[Sat 14 Oct 12:16:54 UTC 2017] LISTEN 0 128 *:80 *:* users:(("nginx",pid=10072,fd=6),("nginx",pid=10071,fd=6),("nginx",pid=10070,fd=6),("nginx",pid=10069,fd=6),("nginx",pid=10068,fd=6),("nginx",pid=10067,fd=6),("nginx",pid=10066,fd=6),("nginx",pid=10065,fd=6),("nginx",pid=10064,fd=6),("nginx",pid=10063,fd=6),("nginx",pid=10062,fd=6),("nginx",pid=10061,fd=6),("nginx",pid=10060,fd=6),("nginx",pid=10059,fd=6),("nginx",pid=10058,fd=6),("nginx",pid=10057,fd=6),("nginx",pid=10056,fd=6))
[Sat 14 Oct 12:16:54 UTC 2017] tcp port 80 is already used by (("nginx",pid=10072,fd=6),("nginx",pid=10071,fd=6),("nginx",pid=10070,fd=6),("nginx",pid=10069,fd=6),("nginx",pid=10068,fd=6),("nginx",pid=10067,fd=6),("nginx",pid=10066,fd=6),("nginx",pid=10065,fd=6),("nginx",pid=10064,fd=6),("nginx",pid=10063,fd=6),("nginx",pid=10062,fd=6),("nginx",pid=10061,fd=6),("nginx",pid=10060,fd=6),("nginx",pid=10059,fd=6),("nginx",pid=10058,fd=6),("nginx",pid=10057,fd=6),("nginx",pid=10056,fd=6))
[Sat 14 Oct 12:16:54 UTC 2017] Please stop it first
[Sat 14 Oct 12:16:54 UTC 2017] _on_before_issue.

What do I have to do that the certificate gets issued?
 
Your HTTP port 80 is currently used by nginx. Please check your nginx configurations or stop it by
Code:
service nginx stop

After successful issue certification, you can bring nginx back
Code:
service nginx start

I've tried it, this process just takes about several seconds.
 
Dear quocbao,
thank you very much for your help.

The main problem is, that HSTS is implemented and the server listens only for encrypted communication. Is there a way to issue the certificate over 443 instead of 80?
 
Dear quocbao,
thank you very much for your help.

The main problem is, that HSTS is implemented and the server listens only for encrypted communication. Is there a way to issue the certificate over 443 instead of 80?

sure, check the acme.sh documentation (I'd recommend nginx or DNS mode in your case)