Jitsi and other Nginx server blocks (Certificate name mismatch)


I’m having some real issues with my setup, could someone help me out please ?

I have a fresh debian 10 server on which I have a working Jitsi Meet instance (e.g. meet.example.com). I followed the quick install guide to set it up, before installing other services. In order to have a valid certificate, I used the install-letsencrypt-cert.sh script.

After that, on the same server, I set up another Nginx server block for my personnal website (e.g. exemple com), which I validated with the following command:
sudo certbot --nginx -d exemple.com
(I’ve changed the default 443 port to 4444)

At first, everything seemed to work and both services are accessible over HTTPS. However my personnal website cannot be indexed. When I do a SSL Server Test, I get a certificate name mismatch. The domain name extracted form the certificate seems to be from the meet domain…

I’m wondering if my question is relevant on this forum. Installing first Jitsi configurated so much Nginx that i’m totally lost. Does anybody have some solutions, tricks or others to help me?

Thanks a lot in advance for your help guys


After working days on this issue, I found a solution.

It wasn’t a certificate name mismatch that was preventing my personnal website from being indexed. However, I still decided to produce a wildcard certificate with the following command:

sudo certbot certonly --dns-ovh --dns-ovh-credentials .ovhapi --deploy-hook /etc/letsencrypt/renewal-hooks/deploy/0000-coturn-certbot-deploy.sh -d example.com -d *.example.com

And install this SSL certificate manually on both Nginx server block

The indexing problem came from the “60-jitsi-meet.conf” nginx config file. Indexing requests was redirect to “default” (turn server) in the “$ssl_preread_alpn_protocols” map. On another post, I found this solution:

map $ssl_preread_alpn_protocols $upstream {
~\bstun.turn\b turn;
default web;

What do you think of this workaround?

Bst rgds

Sorry for my poor English :wink: