Mar 30 09:06:14 [3/30/2026, 16:06:14:098] [Server] Failed to detect IP from http://api.ipify.org 'getaddrinfo EAI_AGAIN api.ipify.org' Mar 30 09:06:14 [3/30/2026, 16:06:14:101] [Server] Failed to detect IP from http://ipinfo.io/ip 'getaddrinfo EAI_AGAIN ipinfo.io' Mar 30 09:06:14 [3/30/2026, 16:06:14:102] [Server] Failed to detect IP from http://ifconfig.me/ip 'getaddrinfo EAI_AGAIN ifconfig.me' Mar 30 09:06:14 [3/30/2026, 16:06:14:103] [Server] Public IP detection failed 'All public IP detection services failed! Please check your network connection' This looks like a network-related issue rather than something specific to MiroTalk. If SFU_ANNOUNCED_IP is not configured, the system will automatically rely on three external services to determine the instance’s public IPv4 address. Is there a firewall or network filter in between that might be blocking traffic? NOTE: As I can see, on Cloudron this is handled by the command in: https://git.cloudron.io/packages/mirotalksfu-app/-/blob/main/start.sh#L39 If it fails (mean not set SFU_ANNOUNCED_IP), MiroTalk SFU uses an internal fallback mechanism that queries three external services in sequence to determine a valid public IPv4 address for the instance.

Discount period again active, ending 22/03/2026 https://codecanyon.net/item/mirotalk-webrtc-ultimate-bundle-for-seamless-live-smart-communication/47976343

wow that is fast, Thanks!

@pdurante1981 said in Mirotalk SFU remote room control: Awesome! Thanks for the quick reply and implementation! You're welcome! Just a quick reminder to please purchase a license if you plan to use this in a commercial production environment.

You might be on to something here. When I tried to set up a call with myself just now, the issue occurred, but when I switched to mobile hotspot, I could connect. It could be that the co-working I am usually in blocks this, and I didn't realise this pattern, so I assumed this was an irregular failure. I'll test this again later, just to be sure, but you might have solved the mystery, thanks a bunch! @james said in Mirotalk - Participants can't see each other 2: Also, did you set SFU_SERVER=true in your /app/data/env file as suggested by @mirotalk? Yes!

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/

@timconsidine said in Thank you, Cloudron!: Tried out Mirotalk P2P and very pleased with it. Thank you for a great product. Thanks for the kind words! Glad you’re enjoying MiroTalk P2P. For larger meetings, you can also check out our MiroTalk SFU variant.

Ops: [Server] Rec Finalization error 'Invalid room ID' Edit: Done in MiroTalk SFU v2.0.24

@james said in Allow Invited Users to Access MiroTalk: But, maybe your client (phone) can simply not share the screen. At the moment, the getDisplayMedia API is not supported on mobile devices. Support may be introduced in future browser versions. For up-to-date information, see the MDN browser compatibility table.

@slfhstng said in "read-only" - can't edit static page in MiroTalk: @MiroTalk Thank you for such a detailed overview! I'm really enjoying MiroTalk (I'm telling everyone about it). Thanks again! You're welcome! and Thank you!

Thank you everyone for your responses. I'm trying to configure Mirotalk SFU to only allow logged in Cloudron users to join a room. Realised that the solution was far simpler than I thought - I just needed to add a single line to the .env file: OIDC_AUTH_REQUIRED=true Thank you deeply to everyone working on Cloudron and all associated apps... I'm in awe of this community! Ads

@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

It’s very important that the RTC port range you configure is: Not already in use by any other application Not blocked by your firewall or ISP For testing purposes, you can enable the SFU server mode by editing the env file (via the File Manager) and setting: SFU_SERVER=true After saving the change, restart the service and check if anything improves. In this mode, MiroTalk SFU uses fewer ports while maintaining nearly the same functionality. For more details, see the discussion here: Mediasoup: WebRTCServer – Firewall Settings and Port Binding Note: MiroTalk SFU can handle approximately 100 concurrent participants per CPU core, depending on your hardware and network conditions.

I have just freshly reinstalled the app, because I ran into the issue. However, although the port has been set to 25000 automatically, I still have the issue.

@james Apologies, I missed that one entirely! It was indeed the problem.

@james it's a Hetzner VPS (CPX51) and I admit, I'm trying to figure out the limits a bit, there are ~70 apps installed on that one, but none of those seem to be hogging a lot of RAM. Backups run at 1:00 in the morning, crash happened at ~8:00ish. I'll keep monitoring to figure out if there's a pattern, but so far I couldn't spot it. system graphs: [image: 1757515965695-fbd8f402-e1e2-4cd8-a331-3b3a134924d3-image-resized.png] htop: [image: 1757515744655-3ad7f6bc-c975-4dbd-925a-03eea8faf6c0-image-resized.png]

@mirotalk-57bab571 FYI this is still happening. I'm freshly back from holidays and had several disconnections on my first meeting. It clearly has to do with my internet set-up at home which must favour packet losses given I have no problems when using MiroTalk on Wifi elsewhere. I also have random disconnections when using my mobile internet outside. However it is also clearly specific to MiroTalk since I have this using using the MiroTalk on Cloudron (always latest package), your MiroTalk demo, but no issues when using Jitsi, mediasoup demo, Google Meet, MS Teams, Zoom. PS: the behaviour has improved since my last message though (above), now it's back to what it used to be, which is I get kicked out but the reconnection happens automatically within about 3-5s seconds and my camera settings (mainly blur background) are conserved.

@nostrdev good catch. I have fixed our CI script to update it correctly from the next release.