Thanks!
Very good news : build against 2.4.41 a certificate was generated
with the domains in MDomain.
When no certificate was specified global, the Apache does not start.
After adding a valid other certificate a new certificate is created
with the domains in MDomain. Then I replaced th
Hi Steffen,
could you check the v2.1.1 I just released? I fixed the recognition of the
"amce-tls/1" protocol when using it in the base server. Hope this works for you
as well.
- Stefan
> Am 06.08.2019 um 10:48 schrieb Steffen :
>
> Forget to attached the log.
>
> On 5-8-2019 15:19, Steffen w
Forget to attached the log.
On 5-8-2019 15:19, Steffen wrote:
Thanks,
Same, also get again :
The https: challenge 'tls-alpn-01' is disabled because the Protocols
configuration does not include the 'acme-tls/1' protocol.
It is in the protocols directive:
ProtocolsHonorOrder On
Protoc
Thanks,
Same, also get again :
The https: challenge 'tls-alpn-01' is disabled because the Protocols
configuration does not include the 'acme-tls/1' protocol.
It is in the protocols directive:
ProtocolsHonorOrder On
Protocols h2 http/1.1 acme-tls/1
MDomain apachelounge.nl www.apache
I think mod_md is not particularly suited to server setups without any
VirtualHosts. I have at least no tests for this.
You can try (with a 2.4.40):
# the new, shorter form
MDCertificateAgreement accepted
# we want the base server to be managed
MDBaseServer on
# the list of domains, including on
I read in the new docu that you can generate a certificate for
domains(s) that does not appear in any host.
So I did a try to generate one certificate for two domains (in Subject
Alternative Name)
Configuration
SSL only on port 443
No vhosts
Listen 443
Protocols h2 http/1.1 acme-tls/
