@joseph said in Error installing Miro SFU:
I think this issue was boiled down to the usage of ephermeral ports . That port which you are trying to install mirotalk in is in use by some other process . See https://forum.cloudron.io/topic/14259/sftpgo-or-mirotalk-sfu-not-starting-because-they-use-ephemeral-ports/ . In essence, use ports < 32767 . The coming version already shows a warning when you try this range.
In case MiroTalk SFU support also WebRTCServer mode:
How to Enable WebRTCServer Mode in MiroTalk SFU (Use Fewer Ports)
If you want to reduce the number of ports used by MiroTalk SFU and make it easier to scale, you can enable the WebRTCServer Mode. This mode lets the internal WebRTC server handle all the media traffic, meaning you don’t need big port ranges anymore.
️ Step-by-Step Setup
Open your environment file
In your file manager (or terminal), open the env file for your MiroTalk SFU instance.
Add the following line
SFU_SERVER=true
Understand the new port behavior
If you start from port 25000, here’s what happens:
1 CPU → 1 worker → uses port 25000
2 CPUs → 2 workers → use ports 25000–25001
and so on…
Each worker uses only one port, not a whole range.
The WebRTCServer manages all internal media traffic automatically.
MiroTalk SFU keeps working just like before only the port handling changes.
Restart your instance
After saving the env file, restart your MiroTalk SFU instance.
Benefits
Fewer open ports → simpler firewall setup
Less chance of port conflicts
Better scalability → easy to scale by CPU count
Cleaner and more secure port configuration
🧠 Notes
This mode is still being tested, but early results look promising.
You can learn more about the WebRTCServer concept here:
Mediasoup Discussion: WebRTCServer and Port Binding