starred/audiobookshelf-advplyr

Fork 0

mirror of https://github.com/advplyr/audiobookshelf.git synced 2026-03-02 22:46:55 -05:00

[Bug]: Webserver dont respond #3139

New issue

Open

opened 2026-02-20 11:00:48 -05:00 by deekerman · 11 comments

deekerman commented

2026-02-20 11:00:48 -05:00

Owner

Originally created by @skolodziej on GitHub (Dec 6, 2025).

What happened?

Webserver dont respond anymore, service seems up, but no data was sent back, ABS sits behind NPM, tried also expose the port direct from the host, still tries to load

What did you expect to happen?

Webserver response

Steps to reproduce the issue

Nothing changed

Audiobookshelf version

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

Chrome

Logs

audiobookshelf    | Running in production mode.
audiobookshelf    | Options: CONFIG_PATH=/config, METADATA_PATH=/metadata, PORT=80, HOST=undefined, SOURCE=docker, ROUTER_BASE_PATH=/audiobookshelf
audiobookshelf    | [2025-12-06 17:00:17.733] INFO: === Starting Server ===
audiobookshelf    | [2025-12-06 17:00:17.735] INFO: [Server] Init v2.30.0
audiobookshelf    | [2025-12-06 17:00:17.735] INFO: [Server] Node.js Version: v20.19.5
audiobookshelf    | [2025-12-06 17:00:17.735] INFO: [Server] Platform: linux
audiobookshelf    | [2025-12-06 17:00:17.735] INFO: [Server] Arch: x64
audiobookshelf    | [2025-12-06 17:00:17.738] INFO: [Database] Initializing db at "/config/absdatabase.sqlite"
audiobookshelf    | [2025-12-06 17:00:17.758] INFO: [Database] Loading extension /usr/local/lib/nusqlite3/libnusqlite3.so
audiobookshelf    | [2025-12-06 17:00:17.758] INFO: [Database] Successfully loaded extension /usr/local/lib/nusqlite3/libnusqlite3.so
audiobookshelf    | [2025-12-06 17:00:17.759] INFO: [Database] Db supports unaccent and unicode foldings
audiobookshelf    | [2025-12-06 17:00:17.759] INFO: [Database] Db connection was successful
audiobookshelf    | [2025-12-06 17:00:17.763] INFO: [MigrationManager] Database is already up to date.
audiobookshelf    | [2025-12-06 17:00:17.855] INFO: [Database] Db initialized with models: 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
audiobookshelf    | [2025-12-06 17:00:17.885] INFO: [Database] running ANALYZE
audiobookshelf    | [2025-12-06 17:00:18.183] INFO: [Database] ANALYZE completed
audiobookshelf    | [2025-12-06 17:00:18.188] INFO: [LogManager] Init current daily log filename: 2025-12-06.txt
audiobookshelf    | [2025-12-06 17:00:18.206] INFO: [BackupManager] 0 Backups Found
audiobookshelf    | [2025-12-06 17:00:18.207] INFO: [BackupManager] Auto Backups are disabled
audiobookshelf    | [2025-12-06 17:00:18.229] INFO: [Watcher] Initializing watcher for "Hörbücher".
audiobookshelf    | [2025-12-06 17:00:18.230] INFO: [Watcher] Initializing watcher for "Podcasts".
audiobookshelf    | [2025-12-06 17:00:18.230] INFO: [Watcher] Initializing watcher for "Bücher".
audiobookshelf    | [2025-12-06 17:00:18.237] INFO: Listening on port :80

Additional Notes

No response

Originally created by @skolodziej on GitHub (Dec 6, 2025). ### What happened? Webserver dont respond anymore, service seems up, but no data was sent back, ABS sits behind NPM, tried also expose the port direct from the host, still tries to load ### What did you expect to happen? Webserver response ### Steps to reproduce the issue Nothing changed ### Audiobookshelf version v2.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? Chrome ### Logs ```shell audiobookshelf | Running in production mode. audiobookshelf | Options: CONFIG_PATH=/config, METADATA_PATH=/metadata, PORT=80, HOST=undefined, SOURCE=docker, ROUTER_BASE_PATH=/audiobookshelf audiobookshelf | [2025-12-06 17:00:17.733] INFO: === Starting Server === audiobookshelf | [2025-12-06 17:00:17.735] INFO: [Server] Init v2.30.0 audiobookshelf | [2025-12-06 17:00:17.735] INFO: [Server] Node.js Version: v20.19.5 audiobookshelf | [2025-12-06 17:00:17.735] INFO: [Server] Platform: linux audiobookshelf | [2025-12-06 17:00:17.735] INFO: [Server] Arch: x64 audiobookshelf | [2025-12-06 17:00:17.738] INFO: [Database] Initializing db at "/config/absdatabase.sqlite" audiobookshelf | [2025-12-06 17:00:17.758] INFO: [Database] Loading extension /usr/local/lib/nusqlite3/libnusqlite3.so audiobookshelf | [2025-12-06 17:00:17.758] INFO: [Database] Successfully loaded extension /usr/local/lib/nusqlite3/libnusqlite3.so audiobookshelf | [2025-12-06 17:00:17.759] INFO: [Database] Db supports unaccent and unicode foldings audiobookshelf | [2025-12-06 17:00:17.759] INFO: [Database] Db connection was successful audiobookshelf | [2025-12-06 17:00:17.763] INFO: [MigrationManager] Database is already up to date. audiobookshelf | [2025-12-06 17:00:17.855] INFO: [Database] Db initialized with models: 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 audiobookshelf | [2025-12-06 17:00:17.885] INFO: [Database] running ANALYZE audiobookshelf | [2025-12-06 17:00:18.183] INFO: [Database] ANALYZE completed audiobookshelf | [2025-12-06 17:00:18.188] INFO: [LogManager] Init current daily log filename: 2025-12-06.txt audiobookshelf | [2025-12-06 17:00:18.206] INFO: [BackupManager] 0 Backups Found audiobookshelf | [2025-12-06 17:00:18.207] INFO: [BackupManager] Auto Backups are disabled audiobookshelf | [2025-12-06 17:00:18.229] INFO: [Watcher] Initializing watcher for "Hörbücher". audiobookshelf | [2025-12-06 17:00:18.230] INFO: [Watcher] Initializing watcher for "Podcasts". audiobookshelf | [2025-12-06 17:00:18.230] INFO: [Watcher] Initializing watcher for "Bücher". audiobookshelf | [2025-12-06 17:00:18.237] INFO: Listening on port :80 ``` ### Additional Notes _No response_

deekerman added the

bug

waiting

unable to reproduce

labels

2026-02-20 11:00:49 -05:00

deekerman commented

2026-02-20 11:00:49 -05:00

Author

Owner

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

Did your IP address change? Firewall settings change? Does it work on the local network (no reverse proxy)?

@nichwall commented on GitHub (Dec 6, 2025): Did your IP address change? Firewall settings change? Does it work on the local network (no reverse proxy)?

deekerman commented

2026-02-20 11:00:50 -05:00

Author

Owner

@skolodziej commented on GitHub (Dec 6, 2025):

Nothing changed, just stopped working.

I tried a direct access in the compose file for test purposes, but no success

ports:
- 8181:80

Same behavior like behind the reserve proxy

@skolodziej commented on GitHub (Dec 6, 2025): Nothing changed, just stopped working. I tried a direct access in the compose file for test purposes, but no success ports: - 8181:80 Same behavior like behind the reserve proxy

deekerman commented

2026-02-20 11:00:50 -05:00

Author

Owner

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

What kind of error are you getting? No response, a spinning circle on a white background, something else?

What is the local IP of the server? Have you verified that has not changed?

We need more information to help debug this.

@nichwall commented on GitHub (Dec 6, 2025): What kind of error are you getting? No response, a spinning circle on a white background, something else? What is the local IP of the server? Have you verified that has not changed? We need more information to help debug this.

deekerman commented

2026-02-20 11:00:50 -05:00

Author

Owner

@skolodziej commented on GitHub (Dec 6, 2025):

Sure, just no answer from the server. I dont see any responses in the developer tools, local IP from the server is 10.254.0.23.
Only thing i changed today is to add a DNS suffix on my DNS server, what can impact it from the network side. But that dont explain why a direct access via IP also dont work. No changes on the host / docker side since a couple of days. Used it yesterday last time and worked great.

How i can create more debug logs to get more into this behavior?

@skolodziej commented on GitHub (Dec 6, 2025): Sure, just no answer from the server. I dont see any responses in the developer tools, local IP from the server is 10.254.0.23. Only thing i changed today is to add a DNS suffix on my DNS server, what can impact it from the network side. But that dont explain why a direct access via IP also dont work. No changes on the host / docker side since a couple of days. Used it yesterday last time and worked great. How i can create more debug logs to get more into this behavior?

deekerman commented

2026-02-20 11:00:50 -05:00

Author

Owner

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

If the server is never getting the request it won't be able to respond. I agree that changing DNS should not affect direct IP access, but it sounds like something else is going on with your network. Can you ping http://10.254.0.23:[port]/ping and see if anything is returned or if the server gets the request? This will also print out in the server logs at the Info level to show that a ping was received.

If the server does not even get the ping, there is something else wrong with your networking, possibly something else you changed when updating the local DNS.

@nichwall commented on GitHub (Dec 6, 2025): If the server is never getting the request it won't be able to respond. I agree that changing DNS should not affect direct IP access, but it sounds like something else is going on with your network. Can you ping `http://10.254.0.23:[port]/ping` and see if anything is returned or if the server gets the request? This will also print out in the server logs at the Info level to show that a ping was received. If the server does not even get the ping, there is something else wrong with your networking, possibly something else you changed when updating the local DNS.

deekerman commented

2026-02-20 11:00:50 -05:00

Author

Owner

@skolodziej commented on GitHub (Dec 6, 2025):

Also a request to http://10.254.0.23:8181/ping does not gave any responses. On this Host there a about 30 containers and about 10 behind the NPM, all of them works fine. I can access the ABS on container level and tried access the ping page from cli... no response:

/app # wget localhost/ping
Connecting to localhost ([::1]:80)

@skolodziej commented on GitHub (Dec 6, 2025): Also a request to http://10.254.0.23:8181/ping does not gave any responses. On this Host there a about 30 containers and about 10 behind the NPM, all of them works fine. I can access the ABS on container level and tried access the ping page from cli... no response: /app # wget localhost/ping Connecting to localhost ([::1]:80)

deekerman commented

2026-02-20 11:00:50 -05:00

Author

Owner

@skolodziej commented on GitHub (Dec 7, 2025):

After some investigation, there seems a problem with the absdatabase.sqlite database. I can open it with a SQLite DB Viewer, but that crashed sometimes if i browse through the structure and data.

If i replace it with a clean absdatabase.sqlite, webserver comes up and respond as expected

@skolodziej commented on GitHub (Dec 7, 2025): After some investigation, there seems a problem with the absdatabase.sqlite database. I can open it with a SQLite DB Viewer, but that crashed sometimes if i browse through the structure and data. If i replace it with a clean absdatabase.sqlite, webserver comes up and respond as expected

deekerman commented

2026-02-20 11:00:50 -05:00

Author

Owner

@nichwall commented on GitHub (Dec 7, 2025):

Oh nice. Do you know what table is causing the problem, or multiple tables?

@nichwall commented on GitHub (Dec 7, 2025): Oh nice. Do you know what table is causing the problem, or multiple tables?

deekerman commented

2026-02-20 11:00:50 -05:00

Author

Owner

@skolodziej commented on GitHub (Dec 7, 2025):

Not so far, i am not very familiar with SQLite but i can share the DB file with you privately

@skolodziej commented on GitHub (Dec 7, 2025): Not so far, i am not very familiar with SQLite but i can share the DB file with you privately

deekerman commented

2026-02-20 11:00:51 -05:00

Author

Owner

@nichwall commented on GitHub (Dec 7, 2025):

Yeah, I can take a look at it later today. You can e-mail the database to me directly or send a link to download it. Because the database is text, you can also compress it to be much smaller. My e-mail is in my GitHub profile, or nyxholas on the ABS Discord.

Thanks for helping narrow that down, pretty much every time someone can't access the server it is due to something else changing on their network and takes a while to get to that point in the debugging, so sorry if I wasn't too helpful with that.

@nichwall commented on GitHub (Dec 7, 2025): Yeah, I can take a look at it later today. You can e-mail the database to me directly or send a link to download it. Because the database is text, you can also compress it to be much smaller. My e-mail is in my GitHub profile, or nyxholas on the ABS Discord. Thanks for helping narrow that down, pretty much every time someone can't access the server it is due to something else changing on their network and takes a while to get to that point in the debugging, so sorry if I wasn't too helpful with that.

deekerman commented

2026-02-20 11:00:51 -05:00

Author

Owner

@nichwall commented on GitHub (Dec 8, 2025):

Thanks for sending the database. Using your database, I was able to start and access the server. I'm not seeing any problems using PRAGMA integrity_check;, what table were you looking at when your DB browser crashed? I have not been able to recreate that either, but I have not scrolled through every single row of every table.

@nichwall commented on GitHub (Dec 8, 2025): Thanks for sending the database. Using your database, I was able to start and access the server. I'm not seeing any problems using `PRAGMA integrity_check;`, what table were you looking at when your DB browser crashed? I have not been able to recreate that either, but I have not scrolled through every single row of every table.