Installing Jitsi-Meet twice on one server with two subdomains


I have the following Situation:
one Server Ubuntu 18.04 LTS headless with nginx and one public IP
Two domains are directed to this server, now both want to have video conferences.
I have created two subdomains: and

I installed jitsi-meet on one subdomain without any problem, but now how can I have another jitsi-meet on the other subdomain?



Just copy the nginx config of the configured domain, change just server_name, change the proxy host: Let’s say you when installing the packages you use
proxy_set_header Host $http_host; to be proxy_set_header Host;.
Probably you will need to generate new certificates and update the nginx file for the new cert files:
This should make the same deployment visible under two domains.


Thanks, I made the changes.
It opens up the jitsi-meet, and it lets me create conferences, but I cannot activate the mic or video and it disconnects an reconnects again and again without mic or video, only on the second domain, the first domain is fine.
any other settings that I need to do?


What is the error you see in the console? Are you accessing it using http or https?


Where do I find the error logs? I have full root access. I am using https.


In the browser, developer tools -> javascript console.


Access to XMLHttpRequest at ‘’ from origin ‘’ has been blocked by CORS policy: Response to preflight request doesn’t pass access control check: No ‘Access-Control-Allow-Origin’ header is present on the requested resource.
Logger.js:125 [JitsiMeetJS.js] <Object.getGlobalOnErrorHandler>: UnhandledError: null Script: null Line: null Column: null StackTrace: Error: Strophe: request id 2.2 error 0 happened
at Object.i.Strophe.log (strophe.util.js:89)
at Object.error (strophe.js:2083)
at e.Bosh._onRequestStateChange (strophe.js:5565)
Logger.js:125 [modules/xmpp/strophe.util.js] <Object.i.Strophe.log>: Strophe: request id 2.2 error 0 happened


Hi I have added the following lines in the main nginx domain and it works:

add_header 'Access-Control-Allow-Headers' 'Authorization,Content-Type,Accept,Origin,User-Agent,DNT,Cache-Control,X-Mx-ReqToken,Keep-Alive,X-Requested-With,If-Modified-Since';


add_header 'Access-Control-Allow-Origin' '*';

but is it the right way?


Your domain accessing the deployment is different from the domain configured for bosh connections: bosh: '//',