Error installing Miro SFU

[nebulon]

The new package is released now also

[avatar1024]

@avatar1024 Just to add that the issue is also there with p2p version.

[jdaviescoates]

@jdaviescoates said in Error installing Miro SFU:

@jdaviescoates said in Error installing Miro SFU:

I just updated Cloudron to 7.7.1 and tried to install Miro SFU but I got this error:

An error occurred during the install operation: Docker Error: (HTTP code 500) server error - driver failed programming external connectivity on endpoint 45483bcf-5f54-47ef-b28d-a13d377e493c (947cbd4cbf34d00ad0c0e0a55e41113ab4505551212b3cffa5c45768c2f29908): listen udp4 0.0.0.0:40026: bind: address already in use

This no longer happens with the latest version.

Nor this:

Looking forward to trying this out in an actual meeting soon! Thanks all

Oh, strange. Actually whilst on 1.4.11 Cloudron package 0.4.0 it did still do the same thing again:

The configure operation failed with the following error:

Docker Error: (HTTP code 500) server error - driver failed programming external connectivity on endpoint dbe699a5-2cf0-46bc-80d8-2445c327f52c (20cbe800ec18f4d4e5ebc030db6fa822a5ec0d47d48172970d6dfff1f8fd096f): listen tcp4 0.0.0.0:40092: bind: address already in use

But then it worked again after hitting the Retry configure button.

Now going to update to the latest packages to test the auth issue people are having too...

[jdaviescoates]

@jdaviescoates the same thing happened when updating, so I just uninstalled and started again with the latest package which installed fine...

[IniBudi]

@avatar1024 Yes, I also have the same problem. I can't log in to the Miro website when I set the password for the host or users

[nebulon]

@jdaviescoates that error is known and mostly fixed in Cloudron pending a release, please stop reporting that.

[jdaviescoates]

@nebulon I was reporting the fact that the error had gone away, but then it came back again.

I figured the fix must've already been released (and hence why the error went away), but thanks for the update that the fix for that error hasn't actually been released yet!

(but something has obviously changed wrt to that error as before it always happened, whereas apparently now it's only intermittent).

[nebulon]

Right, so the issue is, that docker uses/used random free ports for logging on the system and sometimes those conflict with the port range for mirotalk. This is why it "randomly" happens. The fix is in the platform, pending a Cloudron release, not a mirotalk package.

[shrey]

@nebulon
Just tried setting up the MiroTalk SFU for the first time.

I'm a bit surprised that it's marked as stable, as currently, it's pretty impractical trying to get it to work.
Because:

1. I was able to get it to work only after repeated cycles of editing the port, and starting Installation.
2. Even when installed, when i try to restart the app after a modification in the config.js file, the same vicious cycle starts again.

Is there no workaround for now?

[jdaviescoates]

@shrey Are you on Cloudron 7.7.2? Because I think the port clash issue is supposed to have been fixed on that.

[shrey]

@jdaviescoates yes, I'm on 7.7.2

[nebulon]

If this happens again maybe you can run ss -lpn | grep 40092 (change the port depending on the reported port clash). Then check the process id and identify which process/container is occupying that port. So maybe there are other processes which randomly pick ports and caus the conflict, which are not tracked by the platform yet.

[jdaviescoates]

@nebulon said in Error installing Miro SFU:

If this happens again maybe you can run ss -lpn | grep 40092

Run that where exactly?

[nebulon]

on the host system. You may also use other tools like lsof to figure out which process is occupying that port by chance

[jdaviescoates]

@nebulon said in Error installing Miro SFU:

on the host system

That still isn't very clear, but I think you mean SSH into the server, and run it there, right?

I don't even have this problem at present, just asking for the greater good

[nebulon]

Yes sorry for the confusion, so I mean SSH into the Ubuntu server itself (in contrast to a webterminal into the app container).