Hi Giuseppe,
The new certificate files should be copy under ssl folder (/usr/local/elog/ssl or /usr/share/elog/ssl by example, closed to templates and script directories) in place of the embedded (autosigned) certificate files enclosed with ELOG source.
It seems that there is no parameter to set a custom path.
SSL = <0 | 1>
Turn on Secure Socket Layer transport. If SSL is on, one can connect via https://... to the elogd daemon. If the URL = directive is used, make sure to use https://... instead of http://... there. The ELOG distribution contains a simple self-signed certificate in the ssl subdirectory. One can replace this certificate and key with a real ceritficate to avoid browser pop-up windows warning about the self-signed certificate. The default for this option is 0.
| Giuseppe Cucinotta wrote: |
|
We obtained a certificate from let's encrypt in order to replace the self signed certificate provided with elog. We copied the new certificates replacing the older server.crt
The problem is that when restarted elog raises an error related to the fact it is looking for server.crt and it doesn't find it anymore.
I searched in elog config file in order to find a way to indicate the new certificate but I didn't find how to manage this issue.
Any suggestion?
|
|