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. Audiobookshelf
  3. Library scan failing

Library scan failing

Scheduled Pinned Locked Moved Solved Audiobookshelf
4 Posts 2 Posters 486 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.
  • B Offline
    B Offline
    bwag
    wrote on last edited by
    #1

    I am running into the same error message mentioned here: https://github.com/advplyr/audiobookshelf/issues/2854

    When I scan a library, the log gives:

    FATAL

    [Server] Unhandled rejection: ReferenceError: structuredClone is not defined, promise: Promise { <rejected> ReferenceError: structuredClone is not defined at LibraryItemScanData.checkLibraryItemData (/app/code/server/scanner/LibraryItemScanData.js:241:41) at LibraryScanner.scanLibrary (/app/code/server/scanner/LibraryScanner.js:188:60) at async LibraryScanner.scan (/app/code/server/scanner/LibraryScanner.js:82:22) }

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

      Looks like we have to update nodejs for the app to solve this. Will look into that.

      1 Reply Last reply
      0
      • nebulonN nebulon marked this topic as a question on
      • nebulonN Offline
        nebulonN Offline
        nebulon
        Staff
        wrote on last edited by
        #3

        The package is updated to use nodejs 18. Hopefully that bug is fixed then.

        1 Reply Last reply
        0
        • B Offline
          B Offline
          bwag
          wrote on last edited by
          #4

          Wow, thanks, that was fast! I'm not seeing the error any more.

          1 Reply Last reply
          1
          • J joseph has marked this topic as solved on
          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