[Bug]: Server not reachable after Update to 2.30.0 #3012

Open
opened 2026-04-25 00:12:58 +02:00 by adam · 4 comments
Owner

Originally created by @Vortilion on GitHub (Sep 17, 2025).

What happened?

I am running audio bookshelf via docker-compose since a few weeks and started with version 2.28.0. My docker-compose service is:

    audiobookshelf:
      image: ghcr.io/advplyr/audiobookshelf:latest
      container_name: audiobookshelf
      networks:
        qnet-static-eth0:
          ipv4_address: 192.168.178.240
      environment:
        - PUID=1002
        - PGID=1002
        - TZ=Europe/Berlin
      ports:
        - 13378:80
      volumes:
        - /share/homes/my.name/media/AudioBooks:/audiobooks
        - /share/homes/my.name/media/podcasts:/podcasts
        - ./configs:/config
        - ./audiobookshelfmetadata:/metadata
      restart: always

[..]more services running here[...]

    networks:
      qnet-static-eth0:
        name: qnet-static-eth0
        driver: qnet
        ipam:
          driver: qnet
          options:
            iface: "eth0"
          config:
            - subnet: 192.168.178.0/24
            - gateway: 192.168.178.1

It was running perfectly and was reachable via 192.168.178.240/audiobookshelf. Today I wanted to update to 2.30.0 via

docker-compose pull audio bookshelf
docker-compose down audiobookshelf
docker-compose up -d audio bookshelf

Like I am doing for all my running containers, always the same way. But audiobookshelf is not reachable anymore. The log looks like it started up as usual, no errors here. But I am not able to reach it as before. Any ideas what is happening here? :-(

What did you expect to happen?

Audiobookshelf running again on the same url, as before!

Steps to reproduce the issue

  1. update via docker-compose to the latest version (2.30.0)
  2. calling the url in the browser

Audiobookshelf version

2.30.0

How are you running audiobookshelf?

Docker

What OS is your Audiobookshelf server hosted from?

Linux

If the issue is being seen in the UI, what browsers are you seeing the problem on?

None

Logs

{"timestamp":"2025-09-17 15:28:54.610","source":"Server.js:220","message":"=== Starting Server ===","levelName":"INFO","level":2}
{"timestamp":"2025-09-17 15:28:54.612","source":"Server.js:143","message":"[Server] Init v2.29.0","levelName":"INFO","level":2}
{"timestamp":"2025-09-17 15:28:54.613","source":"Server.js:144","message":"[Server] Node.js Version: v20.19.4","levelName":"INFO","level":2}
{"timestamp":"2025-09-17 15:28:54.614","source":"Server.js:145","message":"[Server] Platform: linux","levelName":"INFO","level":2}
{"timestamp":"2025-09-17 15:28:54.615","source":"Server.js:146","message":"[Server] Arch: x64","levelName":"INFO","level":2}
{"timestamp":"2025-09-17 15:28:54.628","source":"Database.js:217","message":"[Database] Initializing db at \"/config/absdatabase.sqlite\"","levelName":"INFO","level":2}
{"timestamp":"2025-09-17 15:28:54.730","source":"Database.js:292","message":"[Database] Loading extension /usr/local/lib/nusqlite3/libnusqlite3.so","levelName":"INFO","level":2}
{"timestamp":"2025-09-17 15:28:54.732","source":"Database.js:300","message":"[Database] Successfully loaded extension /usr/local/lib/nusqlite3/libnusqlite3.so","levelName":"INFO","level":2}
{"timestamp":"2025-09-17 15:28:54.733","source":"Database.js:269","message":"[Database] Db supports unaccent and unicode foldings","levelName":"INFO","level":2}
{"timestamp":"2025-09-17 15:28:54.735","source":"Database.js:273","message":"[Database] Db connection was successful","levelName":"INFO","level":2}
{"timestamp":"2025-09-17 15:28:54.824","source":"MigrationManager.js:125","message":"[MigrationManager] No migrations to run.","levelName":"INFO","level":2}
{"timestamp":"2025-09-17 15:28:55.371","source":"Database.js:201","message":"[Database] Db initialized with models: SequelizeMeta, user, session, apiKey, library, libraryFolder, book, podcast, podcastEpisode, libraryItem, mediaProgress, series, bookSeries, author, bookAuthor, collection, collectionBook, playlist, playlistMediaItem, device, playbackSession, feed, feedEpisode, setting, customMetadataProvider, mediaItemShare","levelName":"INFO","level":2}
{"timestamp":"2025-09-17 15:28:55.499","source":"Database.js:405","message":"[Database] Server upgrade detected from 2.28.0 to 2.29.0","levelName":"INFO","level":2}
{"timestamp":"2025-09-17 15:28:55.642","source":"Database.js:207","message":"[Database] running ANALYZE","levelName":"INFO","level":2}
{"timestamp":"2025-09-17 15:28:55.787","source":"Database.js:209","message":"[Database] ANALYZE completed","levelName":"INFO","level":2}
{"timestamp":"2025-09-17 15:28:55.791","source":"LogManager.js:66","message":"[LogManager] Init current daily log filename: 2025-09-17.txt","levelName":"INFO","level":2}
{"timestamp":"2025-09-17 15:28:55.823","source":"BackupManager.js:285","message":"[BackupManager] 0 Backups Found","levelName":"INFO","level":2}
{"timestamp":"2025-09-17 15:28:55.824","source":"BackupManager.js:72","message":"[BackupManager] Auto Backups are disabled","levelName":"INFO","level":2}
{"timestamp":"2025-09-17 15:28:55.892","source":"Watcher.js:58","message":"[Watcher] Initializing watcher for \"Audio books\".","levelName":"INFO","level":2}
{"timestamp":"2025-09-17 15:28:55.931","source":"Server.js:424","message":"Listening on port :80","levelName":"INFO","level":2}
{"timestamp":"2025-09-17 15:28:56.209","source":"Watcher.js:89","message":"[Watcher] \"Audio books\" Ready","levelName":"INFO","level":2}

Additional Notes

No response

Originally created by @Vortilion on GitHub (Sep 17, 2025). ### What happened? I am running audio bookshelf via docker-compose since a few weeks and started with version 2.28.0. My docker-compose service is: ``` audiobookshelf: image: ghcr.io/advplyr/audiobookshelf:latest container_name: audiobookshelf networks: qnet-static-eth0: ipv4_address: 192.168.178.240 environment: - PUID=1002 - PGID=1002 - TZ=Europe/Berlin ports: - 13378:80 volumes: - /share/homes/my.name/media/AudioBooks:/audiobooks - /share/homes/my.name/media/podcasts:/podcasts - ./configs:/config - ./audiobookshelfmetadata:/metadata restart: always [..]more services running here[...] networks: qnet-static-eth0: name: qnet-static-eth0 driver: qnet ipam: driver: qnet options: iface: "eth0" config: - subnet: 192.168.178.0/24 - gateway: 192.168.178.1 ``` It was running perfectly and was reachable via 192.168.178.240/audiobookshelf. Today I wanted to update to 2.30.0 via ``` docker-compose pull audio bookshelf docker-compose down audiobookshelf docker-compose up -d audio bookshelf ``` Like I am doing for all my running containers, always the same way. But audiobookshelf is not reachable anymore. The log looks like it started up as usual, no errors here. But I am not able to reach it as before. Any ideas what is happening here? :-( ### What did you expect to happen? Audiobookshelf running again on the same url, as before! ### Steps to reproduce the issue 1. update via docker-compose to the latest version (2.30.0) 2. calling the url in the browser ### Audiobookshelf version 2.30.0 ### How are you running audiobookshelf? Docker ### What OS is your Audiobookshelf server hosted from? Linux ### If the issue is being seen in the UI, what browsers are you seeing the problem on? None ### Logs ```shell {"timestamp":"2025-09-17 15:28:54.610","source":"Server.js:220","message":"=== Starting Server ===","levelName":"INFO","level":2} {"timestamp":"2025-09-17 15:28:54.612","source":"Server.js:143","message":"[Server] Init v2.29.0","levelName":"INFO","level":2} {"timestamp":"2025-09-17 15:28:54.613","source":"Server.js:144","message":"[Server] Node.js Version: v20.19.4","levelName":"INFO","level":2} {"timestamp":"2025-09-17 15:28:54.614","source":"Server.js:145","message":"[Server] Platform: linux","levelName":"INFO","level":2} {"timestamp":"2025-09-17 15:28:54.615","source":"Server.js:146","message":"[Server] Arch: x64","levelName":"INFO","level":2} {"timestamp":"2025-09-17 15:28:54.628","source":"Database.js:217","message":"[Database] Initializing db at \"/config/absdatabase.sqlite\"","levelName":"INFO","level":2} {"timestamp":"2025-09-17 15:28:54.730","source":"Database.js:292","message":"[Database] Loading extension /usr/local/lib/nusqlite3/libnusqlite3.so","levelName":"INFO","level":2} {"timestamp":"2025-09-17 15:28:54.732","source":"Database.js:300","message":"[Database] Successfully loaded extension /usr/local/lib/nusqlite3/libnusqlite3.so","levelName":"INFO","level":2} {"timestamp":"2025-09-17 15:28:54.733","source":"Database.js:269","message":"[Database] Db supports unaccent and unicode foldings","levelName":"INFO","level":2} {"timestamp":"2025-09-17 15:28:54.735","source":"Database.js:273","message":"[Database] Db connection was successful","levelName":"INFO","level":2} {"timestamp":"2025-09-17 15:28:54.824","source":"MigrationManager.js:125","message":"[MigrationManager] No migrations to run.","levelName":"INFO","level":2} {"timestamp":"2025-09-17 15:28:55.371","source":"Database.js:201","message":"[Database] Db initialized with models: SequelizeMeta, user, session, apiKey, library, libraryFolder, book, podcast, podcastEpisode, libraryItem, mediaProgress, series, bookSeries, author, bookAuthor, collection, collectionBook, playlist, playlistMediaItem, device, playbackSession, feed, feedEpisode, setting, customMetadataProvider, mediaItemShare","levelName":"INFO","level":2} {"timestamp":"2025-09-17 15:28:55.499","source":"Database.js:405","message":"[Database] Server upgrade detected from 2.28.0 to 2.29.0","levelName":"INFO","level":2} {"timestamp":"2025-09-17 15:28:55.642","source":"Database.js:207","message":"[Database] running ANALYZE","levelName":"INFO","level":2} {"timestamp":"2025-09-17 15:28:55.787","source":"Database.js:209","message":"[Database] ANALYZE completed","levelName":"INFO","level":2} {"timestamp":"2025-09-17 15:28:55.791","source":"LogManager.js:66","message":"[LogManager] Init current daily log filename: 2025-09-17.txt","levelName":"INFO","level":2} {"timestamp":"2025-09-17 15:28:55.823","source":"BackupManager.js:285","message":"[BackupManager] 0 Backups Found","levelName":"INFO","level":2} {"timestamp":"2025-09-17 15:28:55.824","source":"BackupManager.js:72","message":"[BackupManager] Auto Backups are disabled","levelName":"INFO","level":2} {"timestamp":"2025-09-17 15:28:55.892","source":"Watcher.js:58","message":"[Watcher] Initializing watcher for \"Audio books\".","levelName":"INFO","level":2} {"timestamp":"2025-09-17 15:28:55.931","source":"Server.js:424","message":"Listening on port :80","levelName":"INFO","level":2} {"timestamp":"2025-09-17 15:28:56.209","source":"Watcher.js:89","message":"[Watcher] \"Audio books\" Ready","levelName":"INFO","level":2} ``` ### Additional Notes _No response_
adam added the bug label 2026-04-25 00:12:58 +02:00
Author
Owner

@philhaz commented on GitHub (Sep 27, 2025):

@Vortilion I'm having the exact same issue - what was the solution?

@philhaz commented on GitHub (Sep 27, 2025): @Vortilion I'm having the exact same issue - what was the solution?
Author
Owner

@Vortilion commented on GitHub (Sep 27, 2025):

@Vortilion I'm having the exact same issue - what was the solution?

Hey, it suddenly started working again after I tried changing ports, changed the network to another network, changed everything back to as it was, then it worked again. Crazy… hope it does the same for you!

@Vortilion commented on GitHub (Sep 27, 2025): > [@Vortilion](https://github.com/Vortilion) I'm having the exact same issue - what was the solution? Hey, it suddenly started working again after I tried changing ports, changed the network to another network, changed everything back to as it was, then it worked again. Crazy… hope it does the same for you!
Author
Owner

@Vortilion commented on GitHub (Nov 5, 2025):

Having the same issue again after updating to 2.30.0... What is going in here?

@Vortilion commented on GitHub (Nov 5, 2025): Having the same issue again after updating to 2.30.0... What is going in here?
Author
Owner

@nichwall commented on GitHub (Nov 6, 2025):

Do you have a static IP for the server? There isn't a lot of information to go on here, but this is likely a networking issue.

@nichwall commented on GitHub (Nov 6, 2025): Do you have a static IP for the server? There isn't a lot of information to go on here, but this is likely a networking issue.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/audiobookshelf#3012