John, thanks a lot!
really the are two nuances:
1. certificates must be in any subdir of /etc/opensips/tls/
2. it should be a real files, not symlinks.
I already thought about subdir, but put symlinks in it :)
I wonder why in the tutorial
https://www.opensips.org/Documentation/Tutorials-WebSocket-2-2 there is
a wrong example:
# modparam our certificate information
modparam("tls_mgm", "certificate","/etc/letsencrypt/live/acme.com/cert.pem")
modparam("tls_mgm", "private_key","/etc/letsencrypt/live/acme.com/privkey.pem")
may be that was right for the previous opensips versions?
Laba Mikhail
29.04.2019 20:51, John Kiniston пишет:
On Mon, Apr 29, 2019 at 4:28 AM Mikhail <[email protected]
<mailto:[email protected]>> wrote:
modparam("tls_mgm",
"certificate","/etc/letsencrypt/live/ws.mysite.com/fullchain.pem
<http://ws.mysite.com/fullchain.pem>")
modparam("tls_mgm",
"private_key","/etc/letsencrypt/live/ws.mysite.com/privkey.pem
<http://ws.mysite.com/privkey.pem>")
Try copying the fullchain.pem and privkey.pem to /etc/opensips/tls and
changing the path to find them there.
I believe I had issues trying to use letsencrypt certificates, I think
it had to do with the symlinks in /etc/letsencrypt causing problems.
_______________________________________________
Users mailing list
[email protected]
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
_______________________________________________
Users mailing list
[email protected]
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
