Cloudron makes it easy to run web apps like WordPress, Nextcloud, GitLab on your server. Find out more or install now.


Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • Bookmarks
  • Search
Skins
  • Light
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (No Skin)
  • No Skin
Collapse
Brand Logo

Cloudron Forum

Apps | Demo | Docs | Install
  1. Cloudron Forum
  2. MiroTalk
  3. Error installing Miro SFU

Error installing Miro SFU

Scheduled Pinned Locked Moved MiroTalk
64 Posts 9 Posters 11.4k Views 8 Watching
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • avatar1024A avatar1024

    @MiroTalk Yes I just treid again last night and still have the issues:

    Steps are:

    1. go and edit the config.js file
    2. set protected: true (but leave user_auth: false)
    3. uncomment the lines regarding usernames and passwords
    4. Restart the app
    5. launch the app, there I am prompt for a login
    6. login using details set in the config.js file
    7. Create a room
    8. take another computer (or my phone in 5g), try to connect to the room (e.g. talksfu.chourmo.net/join/test), but there I land on a login page and I have to login to be able to join.

    my config.js file:

    // All options at https://github.com/miroslavpejic85/mirotalksfu/blob/main/app/src/config.template.js
    
    module.exports = {
        host: {
            /*
                Host Protection (default: false)
                To enhance host security, enable host protection - user auth and provide valid
                usernames and passwords in the users array.
            */
            protected: true,
            user_auth: false,
            users: [
                
                {
                    username: 'gusername',
                    password: 'password',
                },
                {
                    username: 'username2',
                    password: 'password2',
                },
                
            ]
        },
        presenters: {
            /*
                By default, the presenter is identified as the first participant to join the room, distinguished by their username and UUID.
                Additional layers can be added to specify valid presenters and co-presenters by setting designated usernames.
            */
            list: [],
            join_first: true, // Set to true for traditional behavior, false to prioritize presenters
        }
    };
    

    I'll leave the test room open for a while if you wanna try to join (you can use username2 if you like, username1 won't work though)

    avatar1024A Offline
    avatar1024A Offline
    avatar1024
    wrote on last edited by
    #48

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

    1 Reply Last reply
    1
    • jdaviescoatesJ jdaviescoates

      @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:

      Screenshot from 2024-03-28 18-30-12.png

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

      jdaviescoatesJ Offline
      jdaviescoatesJ Offline
      jdaviescoates
      wrote on last edited by
      #49

      @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:

      Screenshot from 2024-03-28 18-30-12.png

      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
      
      

      5a22f574-8e8d-4ac7-8592-34f169cfe266-image.png

      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...

      I use Cloudron with Gandi & Hetzner

      jdaviescoatesJ nebulonN 2 Replies Last reply
      0
      • jdaviescoatesJ 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:

        Screenshot from 2024-03-28 18-30-12.png

        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
        
        

        5a22f574-8e8d-4ac7-8592-34f169cfe266-image.png

        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...

        jdaviescoatesJ Offline
        jdaviescoatesJ Offline
        jdaviescoates
        wrote on last edited by
        #50

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

        I use Cloudron with Gandi & Hetzner

        1 Reply Last reply
        0
        • avatar1024A avatar1024

          @MiroTalk Yes I just treid again last night and still have the issues:

          Steps are:

          1. go and edit the config.js file
          2. set protected: true (but leave user_auth: false)
          3. uncomment the lines regarding usernames and passwords
          4. Restart the app
          5. launch the app, there I am prompt for a login
          6. login using details set in the config.js file
          7. Create a room
          8. take another computer (or my phone in 5g), try to connect to the room (e.g. talksfu.chourmo.net/join/test), but there I land on a login page and I have to login to be able to join.

          my config.js file:

          // All options at https://github.com/miroslavpejic85/mirotalksfu/blob/main/app/src/config.template.js
          
          module.exports = {
              host: {
                  /*
                      Host Protection (default: false)
                      To enhance host security, enable host protection - user auth and provide valid
                      usernames and passwords in the users array.
                  */
                  protected: true,
                  user_auth: false,
                  users: [
                      
                      {
                          username: 'gusername',
                          password: 'password',
                      },
                      {
                          username: 'username2',
                          password: 'password2',
                      },
                      
                  ]
              },
              presenters: {
                  /*
                      By default, the presenter is identified as the first participant to join the room, distinguished by their username and UUID.
                      Additional layers can be added to specify valid presenters and co-presenters by setting designated usernames.
                  */
                  list: [],
                  join_first: true, // Set to true for traditional behavior, false to prioritize presenters
              }
          };
          

          I'll leave the test room open for a while if you wanna try to join (you can use username2 if you like, username1 won't work though)

          I Offline
          I Offline
          IniBudi
          wrote on last edited by
          #51

          @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

          1 Reply Last reply
          0
          • jdaviescoatesJ 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:

            Screenshot from 2024-03-28 18-30-12.png

            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
            
            

            5a22f574-8e8d-4ac7-8592-34f169cfe266-image.png

            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...

            nebulonN Offline
            nebulonN Offline
            nebulon
            Staff
            wrote on last edited by
            #52

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

            jdaviescoatesJ 1 Reply Last reply
            0
            • nebulonN nebulon

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

              jdaviescoatesJ Offline
              jdaviescoatesJ Offline
              jdaviescoates
              wrote on last edited by
              #53

              @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).

              I use Cloudron with Gandi & Hetzner

              1 Reply Last reply
              0
              • nebulonN Offline
                nebulonN Offline
                nebulon
                Staff
                wrote on last edited by
                #54

                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.

                1 Reply Last reply
                2
                • S Offline
                  S Offline
                  shrey
                  wrote on last edited by
                  #55

                  @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?

                  jdaviescoatesJ 1 Reply Last reply
                  0
                  • S 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?

                    jdaviescoatesJ Offline
                    jdaviescoatesJ Offline
                    jdaviescoates
                    wrote on last edited by
                    #56

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

                    I use Cloudron with Gandi & Hetzner

                    S 1 Reply Last reply
                    1
                    • jdaviescoatesJ jdaviescoates

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

                      S Offline
                      S Offline
                      shrey
                      wrote on last edited by
                      #57

                      @jdaviescoates yes, I'm on 7.7.2

                      1 Reply Last reply
                      0
                      • nebulonN Offline
                        nebulonN Offline
                        nebulon
                        Staff
                        wrote on last edited by
                        #58

                        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.

                        jdaviescoatesJ 1 Reply Last reply
                        0
                        • nebulonN 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.

                          jdaviescoatesJ Offline
                          jdaviescoatesJ Offline
                          jdaviescoates
                          wrote on last edited by
                          #59

                          @nebulon said in Error installing Miro SFU:

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

                          Run that where exactly?

                          I use Cloudron with Gandi & Hetzner

                          1 Reply Last reply
                          0
                          • nebulonN Offline
                            nebulonN Offline
                            nebulon
                            Staff
                            wrote on last edited by
                            #60

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

                            jdaviescoatesJ 1 Reply Last reply
                            0
                            • nebulonN nebulon

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

                              jdaviescoatesJ Offline
                              jdaviescoatesJ Offline
                              jdaviescoates
                              wrote on last edited by
                              #61

                              @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 🙂

                              I use Cloudron with Gandi & Hetzner

                              1 Reply Last reply
                              0
                              • nebulonN Offline
                                nebulonN Offline
                                nebulon
                                Staff
                                wrote on last edited by
                                #62

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

                                1 Reply Last reply
                                1
                                • nebulonN nebulon forked this topic on
                                • jdaviescoatesJ Offline
                                  jdaviescoatesJ Offline
                                  jdaviescoates
                                  wrote on last edited by
                                  #63

                                  I just spotted that my MiroTalk has errored out with this again:

                                  Docker Error: (HTTP code 500) server error - driver failed programming external connectivity on endpoint 16628ecd-d520-4174-ab00-d1eee973101a (8041bbc62efcf050c988cabb0c91fb4d516ac1b3076532b1d284c4f34fadf506): failed to bind port 0.0.0.0:40020/tcp: listen tcp4 0.0.0.0:40020: bind: address already in use
                                  

                                  Hitting the retry button in repair didn't work the first time, but it did work the second time 🤷

                                  I use Cloudron with Gandi & Hetzner

                                  1 Reply Last reply
                                  0
                                  • nebulonN Offline
                                    nebulonN Offline
                                    nebulon
                                    Staff
                                    wrote on last edited by
                                    #64

                                    Yes this is a known issue we have seen rarely. Somehow docker hasn't freed up the port yet. A retry fixes the issue, but we haven't been able to reproduce this reliably for debugging and fixing.

                                    1 Reply Last reply
                                    1
                                    Reply
                                    • Reply as topic
                                    Log in to reply
                                    • Oldest to Newest
                                    • Newest to Oldest
                                    • Most Votes


                                    • Login

                                    • Don't have an account? Register

                                    • Login or register to search.
                                    • First post
                                      Last post
                                    0
                                    • Categories
                                    • Recent
                                    • Tags
                                    • Popular
                                    • Bookmarks
                                    • Search