Open BrianJVarley opened 7 years ago
Hi @BrianJVarley, it seems that the automatic certificate generation breaks by using hostnames with a dash. Try dockertestingvm
as a hostname and it should work.
Hi @rroemhild editing my host and hostname file to dockertestingvm
instead of dockertestin-Virtual-Machine
fixed the issue. I'm now getting a valid self signed certificate for the ejabberd instance and connections are accepted.
Should the automatic certificate generation module be able to handle hostname with -
symbols?
According to this reference Linux uses the RFC952 spec for hostname definitions which defines a valid host as:
A "name" (Net, Host, Gateway, or Domain name) is a text string up to 24 characters drawn from the alphabet (A-Z), digits (0-9), minus sign (-), and period (.). Note that periods are only allowed when they serve to delimit components of "domain style names". [...] No blank or space characters are permitted as part of a name. No distinction is made between upper and lower case. The first character must be an alpha character. The last character must not be a minus sign or period.
In any case removing the dash from the hostname works but may be an enhancement to think about.
I'll let this open until I find the time to fix this issue or maybe someone else has the time.
hi @rroemhild
Issue:
Connecting to ejabberd server container from XMPP client throws a TLS cert error, causing the connection to close.
Error
18:04:15.437 [error] (tcp | <0.640.0>) Failed to secure c2s connection: TLS failed : no_certfile
Debugging
Checking the logs for the
ejabberd
container there are no installation err logs entries relating to ano_certfile
entry.I've tried multiple connection from the PIDGIN client onto the server but get the same no_certfile TLS error.
Docker args
Question
Is this an extra configuration required on the ejabberd server to accept the TLS connection or missing some detail during setup?