I deployed the openvidu 2.14 on the ubuntu server.
The letsencrypt certificate is failed.
I configured the subdomain a record correctly.
What’s the problem?
Best regards,
I deployed the openvidu 2.14 on the ubuntu server.
The letsencrypt certificate is failed.
I configured the subdomain a record correctly.
What’s the problem?
Best regards,
Please try with 2.15.
Great Sensei,
I was in his shoes not long ago, but i figured it out. Is it owk for me to support him? or is there any governing policy.
Thank you.
Of course you can help, @hsmltuge. Any kind of help is greatly welcome.
I tried 2.15
But its same yet.
Hi, hsmltuge, can you help me please?
Thank you
Can you help me please?
I checked at openvidu.wematcher.com
certificate you are using is issued to admin.wematcher.com
Do following:
The correct url: https://openvidu.wematcher.com:4443/#/
But this certificate is my own-made certificate, and this is valid only for 3 months.
( in the .env file, I used “owncert” mode. )
But I want to use “letsencrypt” mode, when I use this mode, the above error triggers.
Try with letsencrypt and share with us the NGINX logs.
Regards
I think there is some miscommunication.
I checked again your present SSL is already from letsencrypt even it is put as own certificate.
Error what you posted above is changing from own certificate to letsencrypt for same domain.
Since you have same domain name issue may be from letsencrypt.
Can you please confirm if you want your own certificate not from letsencrypt but from some other provider?
When I change the certificate mode as “letsencrypt”, then the nginx trigger error, and my OpenVidu server cannot reach.
Please check these screenshot.
And I must leave the certificate mode as “owncert”, because I must operate my website.
Hi @lihuapeng,
I think I have the root of the problem. If I do curl -Ik http://openvidu.wematcher.com
I see that you have running an Apache server at port 80. It is mandatory for letsencrypt to have port 80 available to validate the certificate through the path http://openvidu.wematcher.com/.well-known/acme-challenge/...
You need to stop Apache at this port to let the let’s encrypt operation works in our nginx container.