MiroTalk is built with love to power seamless, secure, and open communication for everyone. If you find it valuable, please consider supporting the project — your contribution helps us:

• Keep the platform free and open
• Develop powerful new features
• Enhance performance and reliability
• Deliver timely updates and support

You can support MiroTalk in two impactful ways:

Donate – Every contribution, big or small, truly makes a difference
Purchase a License – Build with confidence in your private or commercial projects — and help us keep improving MiroTalk for everyone.

Donate Now
Get a License

Let’s build the future of communication together. Thank you for being part of the MiroTalk journey! ️

@robi said in Customizable front page + auth:

I'd also like to see an option to stop the telemetry and stats tracking by default. Didn't see an env var for thatI

I have made statistics configurable in this commit. To implement this feature, add the following variables to your .env file:

# Stats
# Umami: https://github.com/umami-software/umami
# We utilize our self-hosted Umami instance to track aggregated usage statistics for service improvement.

STATS_ENABLED=true # Set to true or false
STATS_SCR=YourUmamiEndpoint
STATS_ID=YourInstanceId

If you prefer not to share your statistics with us for service enhancement, set STATS_ENABLED=false.

Enjoy using MiroTalk P2P v.1.2.77!

@nebulon We're working on integrating OpenID Connect, and you can expect it to roll out with our upcoming release.

@cvachery Regarding room security, you have the option to set passwords for rooms directly from the Settings menu under Room/Lock Room.

When the broadcaster leaves or a viewer disconnects, the viewer will be redirected to a new page.

Users can now join MiroTalk SFU (v1.6.52) and MiroTalk P2P (v1.4.12) rooms by visiting a simplified URL, such as meet.mysite/allwelcome, which will automatically redirect them to meet.mysite/join?room=allwelcome.

The Docker images will be updated and available in about an hour.

@EXT-OWL said in What are the differences between Mirotalk and the SFU version?:

However, I have no idea what the difference between the normal one and SFU are

The key difference between MiroTalk P2P and MiroTalk SFU lies in the way they handle the transmission of media streams between participants in a video conferencing environment. Here's a breakdown:

---

1. MiroTalk P2P (Peer-to-Peer)

• Architecture: Directly connects each participant to every other participant in the session.
• How it works:
  • Each participant sends their audio/video stream directly to every other participant.
  • For example, in a 3-person room, each person sends their stream to 2 others and receives 2 streams.
• Pros:
  • Low latency due to direct connections.
  • No centralized server is required for media relay, reducing infrastructure costs.
  • Good for small group meetings (2-4 participants).
• Cons:
  • Not scalable: Bandwidth usage grows significantly with more participants since each participant must upload multiple streams (N-1 streams, where N is the number of participants).
  • Participants with limited upload bandwidth may experience performance issues in larger rooms.

---

2. MiroTalk SFU (Selective Forwarding Unit)

• Architecture: Uses a centralized server to manage media streams.
• How it works:
  • Each participant sends their audio/video stream to the MiroTalk SFU built in server, which then selectively forwards streams to other participants.
  • For example, in a 3-person room, each person sends 1 stream to the SFU, and the SFU distributes the streams to the others.
• Pros:
  • Scalable: Each participant uploads only one stream regardless of the number of participants, as the SFU handles distribution.
  • Better suited for larger meetings or when participants have limited upload bandwidth.
  • Allows for additional features like transcoding and quality control (e.g., adaptive bitrate).
• Cons:
  • Introduces some latency since streams are relayed through a server.
  • Requires server resources and maintenance, increasing infrastructure costs.

---

When to Use Each?

• MiroTalk P2P:

  • Ideal for small, private calls (e.g., 1-on-1 consultations or small meetings).
  • Lower infrastructure costs and simpler setup.

• MiroTalk SFU:

  • Suitable for larger rooms or scenarios where bandwidth efficiency and scalability are crucial.
  • Offers more advanced features compared to P2P.

---

We have developed a range of MiroTalk solutions, including SFU, P2P, C2C, BRO, and WEB, allowing users to select the most suitable option based on their specific use cases and requirements. For an in-depth look at our WebRTC architecture, please visit our documentation.

@girish said in Only one room available at a time:

@mirotalk-57bab571 do you think the default can be changed upstream ?

Hi, I just pushed the changes.
I might be a bit slow to reply as I'm currently on holiday.

All the best,
Miroslav

Hi @avatar1024,

I've made some improvements to the Socket.IO handling in MiroTalk SFU v1.8.64.

If you experience any disconnections, please let me know. It would be helpful if you could provide a screenshot of what you see on the device when it happens, and let me know whether you're reconnected to the room immediately or what exactly occurs.

Thank you!

Hello @luckow @robi,

I kindly request you to try our official live demo at https://p2p.mirotalk.com

Could you please share whether you have encountered any issues during your experience?

Additionally, it would be helpful if you could provide details on the operating system and browser you were using when you faced this problem. If possible, could you outline the steps to reproduce it?

Also checking the web console logs may help

Thank you!

@robi said in reconnecting to the meeting randomly:

grab some logs before you tag the dev?

I agree. If anyone believe something is not working as expected, please follow this template to report it to us.

Thank you for your collaboration.

Dear Cloudron,

We extend our gratitude for seamlessly integrating MiroTalk P2P into cloudron.io!

MiroTalk P2P boasts a WebRTC Mesh (Peer-to-Peer) architecture, finely tuned for small group video calls with 5 to 8 participants per room. Delve into the intricacies of our WebRTC architecture here

MiroTalk offers specialized variants to meet diverse video conferencing needs. Explore MiroTalk SFU for large-scale conferences, MiroTalk C2C for engaging cam-to-cam video calls, MiroTalk BRO for efficient P2P broadcasting, and MiroTalk WEB for a versatile solution.

Upon creating an account on MiroTalk WEB and confirming it via email, you gain direct access to all these versions. Effortlessly organize meeting rooms, send invitations, and relish the flexibility of our diverse solutions.

Privacy and Data Usage in MiroTalk: A Clarification

In adherence to our Privacy Policy, MiroTalk employs telemetry requests upstream for the sole purpose of tracking aggregated usage statistics. This information is crucial for enhancing our service, and it is important to note that the creator of MiroTalk has no intention of personally using or selling any of the collected data.

To further prioritize user control, a configuration option will be introduced in the .env file, allowing users to decide whether they want to track their specific instance of MiroTalk. This feature, already done in MiroTalk SFU, will be implemented in the near future also for MiroTalk P2P.

Screen Sharing issue

If you've encountered any issues with screen sharing, we recommend checking the behavior in our official live demo and providing some browsers console logs can help us to understand the issue, Additionally, ensure that your Turn server is configured correctly; detailed information can be found here.

Host Protection and User Authentication Settings

Discover the latest updates on MiroTalk's security measures, focusing on P2P host protection and user authentication. For detailed insights, refer to this official GitHub commit: MiroTalk Commit 285c9260.

Doubits or Questions

Should you have any doubts or questions, we encourage you to engage with our community on our dedicated forum: https://discord.gg/rgGYfeYW3N.

Thank you for being part of the MiroTalk experience, dedicated to catering to all your video conferencing needs!

Warm Regards,
Miroslav Pejic

Typically if there is a bug on our official live demo the template to follow to help us better understand the problem is the following:

# MiroTalk Version

Specify the MiroTalk version being used: P2P, SFU, C2C, BRO, or WEB.

# Bug Description

Provide a clear and concise description of the encountered bug.

# Steps to Reproduce

Outline the steps to reproduce the behavior:

1. Navigate to '...'
2. Click on '....'
3. Scroll down to '....'
4. Observe the error.

# Desktop - Mobile

Please complete the following information:

- Device or OS: [e.g., iPhone6, Android, Linux, Mac, Windows]
- Browser: [e.g., Chrome, Safari]
- Version: [e.g., 22]

# Expected Outcome

Clearly articulate what you expected to happen in contrast to the observed behavior.

# Screenshots

Include relevant screenshots if available to facilitate a better understanding of the issue.

## Additional Context

Share any supplementary information such as console logs or other relevant details that could assist in troubleshooting the problem.

Thank you!

@mdc773 said in when creating room no auth prompt:

all URLs should be protected not just the main root

In the OIDC settings, there is a parameter to make it possible

oidc: {
    config: {
        authRequired: true, // Set to true if authentication is required for all routes
    }
}

@jdaviescoates said in when creating room no auth prompt:

I'm not certain, but I think that license is probably mostly about the support you get from @MiroTalk

With the purchase of a license or for those who support the project in some way, my Direct support is included for any questions or concerns regarding MiroTalk. However, if your intention is to rebrand it by changing the logo, name, description, etc., a Regular License is required for personal, non-commercial projects. For commercial purposes or if you intend to charge end users, the Extended License is necessary.

Note: No monthly subscriptions are required; it's a one-time fee.

For more details about MiroTalk's licensing options, please visit: https://docs.mirotalk.com/license/licensing-options/

Thank you, and I take this opportunity to wish everyone a Happy 2025!

I’ve opened a thread here to discuss best strategies for handling unstable connections in mediasoup (built-in MiroTalk SFU server).

Coming in MiroTalk SFU v1.8.57
You’ll be able to configure the OIDC username behavior directly from your .env file. Simply add or update the following entries:

OIDC_FORCE_USERNAME=false
OIDC_EMAIL_AS_USERNAME=false
OIDC_NAME_AS_USERNAME=true

These settings give you full control over how usernames are derived from the OIDC provider, but allowing you to edit before join room.

Cheers,
Miroslav

@james said in Email as default username since update to new config set-up is NOT great :

I assume what @mirotalk-57bab571 wrote https://forum.cloudron.io/post/107999 was simply a typo or first draft of that variable names.

Yes, you're absolutely right — the way you explained it is correct. I actually updated it in my last commit to make it more readable.

OIDC_USERNAME_FORCE=false
OIDC_USERNAME_AS_EMAIL=false
OIDC_USERNAME_AS_NAME=true

And here’s a quick explanation of each default setup:

OIDC_USERNAME_FORCE=true        # Forces the username to match the OIDC email or name. 
                                # If true, the user won't be able to change their name when joining a room.

OIDC_USERNAME_AS_EMAIL=true     # Uses the OIDC email as the username.
OIDC_USERNAME_AS_NAME=false     # Uses the OIDC name as the username.

These options give you full control over how usernames are assigned during OIDC authentication for the meeting.

Note

By default, the email is used as the username when OIDC is enabled. This helps maintain user identity and trust, and also ensures that the correct Gravatar is displayed in the room (especially if the camera is off).

In this default setup, the username cannot be edited by the user when joining a room.

However, since MiroTalk SFU is designed to be flexible, this behavior is fully configurable. You can choose whether to use the email, the name, or allow users to set their own name — depending on your needs...

@alpro said in Only one room available at a time:

With only difference that I experience it with MiroTalk SFU 1.8.60.

Not sure how is handled there, but by default, OIDC_ENABLED is set to false in all MiroTalk projects.

When OIDC_ENABLED is set to true, any user authenticated via OIDC can create and share rooms. Previously, only one user had this ability, but now this behavior is enabled by default (when OIDC is active) and can be configured through the .env file.

OIDC_ALLOW_ROOMS_CREATION_FOR_AUTH_USERS=true  // true or false (default true)

So when you visit your MiroTalk SFU instance outside the cloudron panel, (e.g., https://cloudron.your-domain-name.com), the Cloudron OIDC authentication popup will appear. Simply enter the username and password you use for Cloudron login. Once authenticated, you—or your family members—will be able to access the instance, create rooms, and share them with guests.

---

Additionally, you can try another approach by updating your env file (via the Cloudron file manager) in MiroTalk SFU to enable HOST_PROTECTED mode and define a list of authorized users as follows:

OIDC_ENABLED=false
HOST_PROTECTED=true
HOST_USER_AUTH=false
HOST_USERS="username:password:User:*|admin:admin:Admin:room1,room2|guest:guest:Guest:room1,room1"

When HOST_PROTECTED or HOST_USER_AUTH enabled:

HOST_USERS – Define Authorized Host Users

The HOST_USERS environment variable is used to predefine a list of users who are allowed to log in as hosts in your application. Each user entry follows this format:

username:password:displayName:allowedRooms

Multiple users are separated by the pipe symbol |.

Format Breakdown:

• username: The login name of the user.
• password: The password used for authentication.
• displayName: The name that will be shown in the UI (e.g., in meetings).
• allowedRooms: A comma-separated list of room names this user is allowed to create or join as host. Use * to allow all rooms.

🧪 Example:

HOST_USERS="username:password:user:*|admin:admin:Admin:room1,room2|guest:guest:Guest:room1"

This defines 3 host users:

1. username with password password, display name user, can access any room (*).
2. admin with password admin, display name Admin, can access only room1 and room2.
3. guest with password guest, display name Guest, can access only room1.

---

For reference here.

@imc67 said in Room link gets lost after OIDC login:

Can this be solved?

OIDC support for WhoAreYou (waiting room) is now available in MiroTalk SFU v1.8.81!

Docker image build is in progress…

@nebulon

Hi and welcome here @MiroTalk
Deviating the discussion here a bit, but first of all, you have built something really great. Quite impressive!

Yes forgive me, Thank you and I'm very thrilled you like MiroTalk projects!

Given how MiroTalk has separated the backends neatly, our current plan was to package them individually, since they seem to cover slightly different use-cases.

We made a versatile solution for a variety of communication needs. We've crafted five distinct Mirotalk WebRTC projects, each designed to cater to specific requirements. Whether it's for virtual meetings, collaborative sessions, or any other communication purpose.

We also plan on packaging the web call scheduler, which allows to integrate those backends as standalone apps on Cloudron.

For detailed instructions on how to self-host MiroTalk WEB and integrate Mirotalk desired components, refer to our comprehensive documentation at https://docs.mirotalk.com/mirotalk-web/self-hosting/.

Initially I packaged them all at once, but that seemed a bit cumbersome, as on Cloudron it would require the user to allocate 5 (sub)domains for all to work, so we decided to split this, as we saw the main use-case to provide calls with say up to 10 people. Cloudron is not targeting audiences which require massive scaling, so that seemed fine. The initial package is the p2p flavor, since it works quite well and the SFU backend needs a port range, which is currently not supported by Cloudron. We hope to add this soon though if possible.

MiroTalk P2P boasts a WebRTC Mesh (Peer-to-Peer) architecture, optimized for small group video calls with 5 to 8 participants per room. On the other hand, MiroTalk SFU (Selective Forwarding Unit) offers scalability and robust performance, capable of handling approximately 100 concurrent participants with just a single CPU. Although it requires port ranges, the scalability ensures a seamless and efficient communication environment.

If you have any thoughts on that, very welcome and much appreciated, as you are the expert on your app.

Thanks a bunch for the kudos! I'm just a developer like you, passionate about what I do. It's awesome connecting with fellow devs who share the love for coding. If you ever want to chat or share cool dev stories, I'm all ears! Happy coding!