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. Jitsi
  3. Installation: First attempt with an error. Second attempt without a problem

Installation: First attempt with an error. Second attempt without a problem

Scheduled Pinned Locked Moved Solved Jitsi
2 Posts 2 Posters 328 Views 2 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.
  • luckowL Offline
    luckowL Offline
    luckow
    translator
    wrote on last edited by
    #1
    An error occurred during the install operation: Task Error: Task 9940 crashed with code 1 and signal null
    

    Maybe this from the logs?!

    BoxError: ER_DUP_ENTRY: Duplicate entry '172.18.16.18' for key 'containerIp'
        at updateWithConstraints (/home/yellowtent/box/src/apps.js:865:55)
        at processTicksAndRejections (internal/process/task_queues.js:95:5)
        at async Object.update (/home/yellowtent/box/src/apps.js:874:5)
        at async updateApp (/home/yellowtent/box/src/apptask.js:64:5)
    

    Pronouns: he/him | Primary language: German

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

      Ah that is actually not a jitsi issue, but a platform bug. I have seen that sometimes during e2e tests, but so far I wasn't able to reproduce this reliably. As you mentioned a retry usually works then. Something with docker recycling container IPs.

      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