Are alias-domains possible for Mirotalk?

[msbt]

I have a Mirotalk instance that I use for my own stuff on miro.example.com. Is it possible to add alias domains, so a customer could use talk.customerdomain.com with the same instance as mine? Thus saving resources and not having to install the app several times. I know this is possible with Nextcloud (not on Cloudron though I believe), would be nice to have that possibility, if technically feasible.

[MiroTalk]

@msbt said in Are alias-domains possible for Mirotalk?:

I have a Mirotalk instance that I use for my own stuff on miro.example.com. Is it possible to add alias domains, so a customer could use talk.customerdomain.com with the same instance as mine?

You can embedding your MiroTalk instance into any website (talk.customerdomain.com) or app easily using an iframe:

<iframe 
  allow="camera; microphone; display-capture; fullscreen; clipboard-read; clipboard-write; web-share; autoplay"
  src="https://miro.example.com/newroom"
  style="width: 100vw; height: 100vh; border: 0px;">
</iframe>

You can check the MiroTalk SFU example here, or MiroTalk P2P example here.

This functionality would greatly streamline the management of multiple domains while maintaining a single instance.

[msbt]

@MiroTalk thanks for your work and input, maybe I should have explained why: This specific example would be for 1:1 sessions for a customer of mine (therapist), where the join-links are supposed to be sent via email (that's why the separate domain, for credibility's sake).

[MiroTalk]

MiroTalk with Alias Domains

I'm not tested but I think can be archived with something like this:

Use alias domains (e.g., talk.customerdomain.com) for your MiroTalk instance on the same server. Here's how:

1. DNS Configuration

• A Record: Point talk.customerdomain.com to your server's IPv4 address.
• CNAME Record: Alternatively, alias talk.customerdomain.com to miro.example.com.

2. Web Server Configuration

Nginx Configuration:

server {
    listen 80;
    server_name miro.example.com talk.customerdomain.com;

    location / {
        proxy_pass http://127.0.0.1:3000;
        proxy_set_header Host $host;
        proxy_set_header X-Real-IP $remote_addr;
    }
}

Apache Configuration:

<VirtualHost *:80>
    ServerName miro.example.com
    ServerAlias talk.customerdomain.com

    ProxyPreserveHost On
    ProxyPass / http://127.0.0.1:3000/
    ProxyPassReverse / http://127.0.0.1:3000/
</VirtualHost>

3. SSL Configuration

Generate SSL certificates for both domains using Certbot:

sudo certbot --nginx -d miro.example.com -d talk.customerdomain.com
# OR
sudo certbot --apache -d miro.example.com -d talk.customerdomain.com

Ensure your web server is configured to include SSL settings for both domains.

4. Cross-Origin Requests (CORS)

If necessary, adjust MiroTalk or web server settings to allow CORS for talk.customerdomain.com.

5. Testing

• Verify that talk.customerdomain.com resolves to your server.
• Access MiroTalk through both miro.example.com and talk.customerdomain.com to ensure everything works as expected.

---