The email inviting you to the email showed you the --server option (highlighted in yellow even – at least mine was); it’s also here in the Beta Announcements post.
Hello
kelunik and Kromey, thx for help. I am now one step further.
I reinstalled centos 7 and started from scratch.
(Yes with the reinstall, I deleted the /etc/letsencrypt/accounts folder)
I stoped apache (service httpd stop)
I ran the command
Congratulations! Your certificate and chain have been saved at /etc/letsencrypt/live/myserver.de/fullchain.pem. Your cert will expire on 2016-02-12. To obtain a new version of the certificate in the future, simply run Let’s Encrypt again.”
After starting the apache (service httpd start).
There is still no https available, just http.
Using nmap localhost from the machine. I get the following results
Starting
Nmap 6.40 ( http://nmap.org ) at 2015-11-14 11:24 MET
Nmap scan
report for localhost (127.0.0.1)
Host is up
(0.000014s latency).
Other
addresses for localhost (not scanned): 127.0.0.1
rDNS record
for 127.0.0.1: localhost.localdomain
Not shown:
997 closed ports
PORT STATE SERVICE 22/tcp open ssh 25/tcp open smtp 80/tcp open http
There is no port 443 open!
service iptables status
Redirecting to /bin/systemctl status iptables.service
iptables.service - IPv4 firewall with iptables
Loaded:
loaded (/usr/lib/systemd/system/iptables.service; disabled)
Active: inactive (dead) since Sat 2015-11-14 11:12:42 MET; 13min ago
Process:
1167 ExecStop=/usr/libexec/iptables/iptables.init stop (code=exited,
status=0/SUCCESS)
Ok, I created a single vhost. I tried starting apache
and it tells me AH00526: Syntax error on line 7 of /etc/httpd/sites-enabled/myserver.de.conf:
The command in line 7 is SSLEngine on
Invalid command ‘SSLEngine’, perhaps misspelled
or defined by a module not included in the server configuration
Is there am apache/ssl
modul on centos 7 which needs to be enable in addition to letsencrypt?
I got the
email regarding the beta program on November the 10th.
Thanks for pointing out the typo. That was introduced in a recent revision of the invite email, and it’s now fixed.
Yes, the Let’s Encrypt client supports automated configuration of your web server: that’s the first example command (the “Apache plugin”) under “How to use the client” in your beta invite email. The command line you ran is for the standalone mode, which doesn’t do automated configuration.