https://bugs.contribs.org/show_bug.cgi?id=10399
--- Comment #12 from John Crisp <[email protected]> ---
We really need to see the domains you are trying to resolve. Obfuscating
publicly available domains doesn't help us, particularly as it looks like you
are using a dynamic IP so it keeps shifting.
SSL is not enabled on Primary by default (as far as I remember)
You have to manually set it.
It doesn't disable http but just redirects any http queries to https.
However, as long as it resolves to that directory and letsencrypt can see the
contents then you will not have a problem.
This resolves OK:
http://87.140.117.154/.well-known/acme-challenge/
It actually redirects to:
https://87.140.117.154/.well-known/acme-challenge/
Which is correct if you have:
Primary=ibay
SSL=enabled
I can see the directory from here, so theoretically letsencrypt should be able
to.
Note that you can enable letsencrypt per host but you do not actually need to
'disable' it as it defaults to disabled. It is handy so set 'disabled' if you
want to be able to temporarily disable a host without deleting the key
entirely.
So for your wpad, ftp & proxy hosts just delete the key entirely.
Last re #c11 it seems the issue is trying to resolve mail.xxx.de
Can you please advise the full host so we can take a look.
--
You are receiving this mail because:
You are the QA Contact for the bug._______________________________________________
Mail for each SME Contribs bug report
To unsubscribe, e-mail [email protected]
Searchable archive at https://lists.contribs.org/mailman/public/contribteam/
