Cloudron Forum

As a token of appreciation for your continuous support of MiroTalk, we’ve also added a dedicated section to our official documentation:

https://docs.mirotalk.com/cloudron/cloudron/

We’ve also included acknowledgments on both of our GitHub repositories.

Sometimes it’s important to say thank you to those who truly deserve.

Wishing the entire Cloudron team and all MiroTalk supporters a great weekend ahead!

Best,
Miroslav

MiroTalk projects is built with love to power, 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 three impactful ways:

Purchase a License: Build with confidence in your private or commercial projects.
Support with a Donation: Every contribution, big or small, truly makes a difference
Support us via GitHub Sponsors: Choose from different sponsorship tiers, each offering unique perks and ways to get involved. Your support helps us maintain, improve, and grow MiroTalk.

CodeCanyon
PayPal
Stripe
GitHub Sponsors

Stay tuned! Join the community forum: https://discord.gg/rgGYfeYW3N

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!

@slfhstng said in "read-only" - can't edit static page in MiroTalk:

I wanted to edit some of the text on this page, but it wouldn't let me save when using Cloudron console. The message said it was read-only.

With MiroTalk SFU, everything is possible!

By editing the env file via the Cloudron App file manager:

1. Open the MiroTalk SFU settings.

2. Navigate to the File Manager.

3. Open the env file (double-click to edit), make your changes, save, and then restart the instance for the changes to take effect.

you can fully rebrand MiroTalk, including changing the app name, logo, description, language, and even customizing which buttons appear in the meeting interface, among many other options:

env example

Here’s an example of a simple landing page rebranding, without touching the source code. Everything is centralized in a single env file, which is injected into config.js for documentation purposes:

# App
UI_LANGUAGE=en                                    # Interface language (en, es, fr, etc.)
APP_NAME=YOUR-APP-NAME                            # Application name
APP_TITLE=YOUR-APP-TITLE                          # Custom HTML title (leave empty for default)
APP_DESCRIPTION=YOUR-APP-DESC                     # Application description
JOIN_DESCRIPTION=JOIN-DESC                        # Join screen description
JOIN_BUTTON_LABEL=JOIN ROOM                       # Join button text
JOIN_LAST_LABEL=Your recent room:                 # Recent room label text

# OG
OG_TYPE=app-webrtc                                # OpenGraph type
OG_SITE_NAME=YOUR-APP-NAME                        # OG site name
OG_TITLE=                                         # OG title
OG_DESCRIPTION=                                   # OG description
OG_IMAGE_URL=https://MIROTALK-CLOUDRON-URL/images/mirotalksfu.png # OG image
OG_URL=https://MIROTALK-CLOUDRON-URL              # OG URL

# HTML
SHOW_TOP_SPONSORS=false                            # Show top sponsors section (true|false)
SHOW_FEATURES=false                                # Show features section (true|false)
SHOW_TEAMS=false                                   # Show teams section (true|false)
SHOW_TRY_EASIER=false                              # Show "try easier" section (true|false)
SHOW_POWERED_BY=false                              # Show powered by (true|false)
SHOW_SPONSORS=false                                # Show sponsors (true|false)
SHOW_ADVERTISERS=false                             # Show advertisers (true|false)
SHOW_FOOTER=false                                  # Show footer (true|false)

---

For the Who Are You page (which I believe you’re referring to), you can customize the following environment variables in the env file as well to adapt the page to your preferences:

# Who Are You
WHO_ARE_YOU_TITLE="Who are you?"  
WHO_ARE_YOU_DESCRIPTION="If you're the presenter, please log in now.<br />Otherwise, please wait for the presenter to join."  
WHO_ARE_YOU_BUTTON_LOGIN_LABEL="LOGIN"  
WHO_ARE_YOU_JOIN_LABEL="JOIN ROOM"

---

️ Important: To use these rebranding and customization features, a Regular License is required. This ensures legal compliance and supports the ongoing development and deployment of MiroTalk.

You can purchase the license directly from CodeCanyon here:

MiroTalk SFU – WebRTC Real-time Video Conferences

One-time payment for a lifetime license, including all updates.

Thank you for your support!

@nebulon @James @shrey

Implemented in MiroTalk SFU v2.0.14 — Docker image is building now (available in ~1 hour).

• Commit
• Build

For Cloudron deployments, server-side recording should now work using the following configuration:

Recording

RECORDING_ENABLED=true
RECORDING_DIR='../data/rec'            # Path relative to /app/code → resolves to /app/data/rec
RECORDING_MAX_FILE_SIZE=1073741824     # Max file size in bytes (default: 1GB)

RTMP

RTMP_DIR='../data/rtmp'                # Path relative to /app/code → resolves to /app/data/rtmp

Note

If the target directories do not exist, MiroTalk SFU will automatically create them at runtime, just like before.

Cloudron automatically mounts /app/data, so using ../data/... ensures the app writes to the persistent, writable directory.

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.

Thank you, @canadaduane for the great analysis!

In case it’s helpful, here are some examples of API usage in different languages:

• JavaScript
• PHP
• Python
• Bash

You can find full working examples here:
https://docs.mirotalk.com/mirotalk-sfu/api/

@james Thanks a lot for the clarification and the kind words, much appreciated.

I'm agree, maybe I overdid it a bit with emojis and the AI style .

In any case, I’m always happy to help here, and thank you for the trust you place in the MiroTalk projects!

@marcusquinn No worries at all, and thank you for the kind words

I usually don’t post promotional content here. This was just a one-off post in case anyone felt like contributing or getting involved. I completely understand the need to stay vigilant about spam, and I appreciate you taking the time to explain.

Thanks again for the understanding and encouragement, it really means a lot. Keep up the great work, and I’m always happy to help and contribute here as well!

@lucidfox said in MIROTALK ULTIMATE BUNDLE — LIMITED-TIME SALE — ENDS 23/01/2026! :

@mirotalk it's unclear to me what this bundle offers that's not already available on cloudron? it would be nice to support your project, but i'm just wondering what this 'unlocks' on cloudron.

Hey @lucidfox, thanks a lot for the question, and also for even considering supporting the project. I really appreciate that

Let me try to explain it a bit more clearly and in a simple way.

All MiroTalk projects are fully open source under the AGPLv3 license. This means you’re absolutely free to use them as they are, including on Cloudron. However, any modification, customization, or rebranding of the codebase must remain open source and be publicly documented.

What the bundle really “unlocks” is flexibility and peace of mind.

With a Regular or Extended License, you’re allowed to:

• Use MiroTalk in closed-source projects
• Customize and rebrand it (remove logos, change UI/UX, integrate it into your own product or Cloudron)
• Use it commercially without AGPL obligations

In terms of features, Cloudron already includes MiroTalk P2P, SFU, and BRO. The bundle also includes MiroTalk WEB, C2C and ADM, which are not part of the standard Cloudron setup.

One important clarification specifically about Cloudron: even there, if you modify the original MiroTalk codebase in any way, for example rebranding in from the env, changing the UI, or adapting it for your own project, a Regular License is required to stay compliant. Using MiroTalk as-is is totally fine under AGPL, but once you start customizing or removing the original branding, the license is what gives you that right.

Also, if you only want to rebrand or customize a single MiroTalk instance, you don’t necessarily need the full bundle. You can purchase a license for a single form/project directly here as well:
https://codecanyon.net/user/miroslavpejic85/portfolio

Beyond licensing, purchasing the bundle is also a direct way to support ongoing development, maintenance, and future improvements of MiroTalk. It really helps keep the project alive and moving forward.

So if you’re happy using the open-source version as-is on Cloudron, that’s perfectly fine. But if you want more freedom, commercial usage, or simply want to support the work behind it, the bundle is there for that.

Reference:

• About: https://docs.mirotalk.com/about
• Licensing options: https://docs.mirotalk.com/license/licensing-options/
• Cloudron: https://docs.mirotalk.com/cloudron/cloudron/
• Repo: https://github.com/miroslavpejic85

Thanks again for your interest, and feel free to ask if anything is still unclear.

Thank you all,
Miroslav

Great news @pdurante1981 @nebulon

The Meeting END API has been implemented in MiroTalk SFU v2.1.20.

This allows you to remotely terminate an active meeting by room name, perfect for billable minutes or subscription-based systems.

---

New Endpoint

DELETE /api/v1/meeting/:room

What it does:

• Disconnects all connected peers
• Optionally redirects them to a custom URL
• Disables the “beforeunload” confirmation popup when ended via API
• Protected via API secret key
• Fully documented in Swagger
• Includes example scripts (JS, Shell, Python, PHP)
• Covered by unit tests

---

Enable the Feature

In your env file:

API_KEY_SECRET=mirotalksfu_default_secret
API_ALLOW_MEETING_END=true

By default, this endpoint is disabled for security reasons.

---

Quick Examples

End meeting (peers return to home page)

curl -X DELETE http://localhost:3010/api/v1/meeting/test \
  -H "authorization: mirotalksfu_default_secret" \
  -H "Content-Type: application/json"

End meeting with custom redirect

curl -X DELETE http://localhost:3010/api/v1/meeting/test \
  -H "authorization: mirotalksfu_default_secret" \
  -H "Content-Type: application/json" \
  -d '{"redirect": "https://docs.mirotalk.com/about"}'

---

Documentation

Full API reference:
https://docs.mirotalk.com/mirotalk-sfu/api/#meeting-end-entry-point

---

This should now fully cover your use case for remotely ending meetings when user minutes expire

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!