Docker Container: ABS not accessible after update

[JakobTischler]

Hi all,

I'm running ABS using Docker on a Synology NAS. I was using v2.2.1, everything was working okay. I then updated to v2.2.2, and since then I can't access ABS anymore. The site is somehow there, but I'm getting

192.168.xxx.xx didn’t send any data.
ERR_EMPTY_RESPONSE

IP obfuscation by me. This is a "no data" error, not a "not found" error. Mind you, I'm trying to access it locally, so the port shouldn't be an issue.

---

The ABS log:

2022-11-07 14:50:00,stdout,npm ERR! path /
2022-11-07 14:50:00,stdout,npm ERR! command failed
2022-11-07 14:50:00,stdout,npm ERR! signal SIGTERM
2022-11-07 14:50:00,stdout,npm ERR! command sh -c -- node index.js
2022-11-07 14:50:00,stdout,
2022-11-07 14:50:00,stdout,npm ERR! A complete log of this run can be found in:
2022-11-07 14:50:00,stdout,npm ERR!     /root/.npm/_logs/2022-11-07T14_12_07_480Z-debug-0.log
2022-11-07 14:50:00,stdout,
2022-11-07 14:50:44,stdout,
2022-11-07 14:50:44,stdout,> [email protected] start
2022-11-07 14:50:44,stdout,> node index.js
2022-11-07 14:50:44,stdout,
2022-11-07 14:50:45,stdout,Config /config /metadata
2022-11-07 14:50:45,stdout,[2022-11-07 14:50:45]  INFO: === Starting Server ===
2022-11-07 14:50:45,stdout,[2022-11-07 14:50:45]  INFO: [Server] Init v2.2.2
2022-11-07 14:50:45,stdout,[2022-11-07 14:50:45]  INFO: [DB] 3 Libraries Loaded
2022-11-07 14:50:45,stdout,[2022-11-07 14:50:45]  INFO: [DB] 2 Collections Loaded
2022-11-07 14:50:45,stdout,[2022-11-07 14:50:45]  INFO: [DB] 227 Series Loaded
2022-11-07 14:50:45,stdout,[2022-11-07 14:50:45]  INFO: [DB] 867 Authors Loaded
2022-11-07 14:50:45,stdout,[2022-11-07 14:50:45]  INFO: [DB] 2 Users Loaded
2022-11-07 14:50:46,stdout,[2022-11-07 14:50:46]  INFO: [DB] 1761 Library Items Loaded
2022-11-07 14:50:47,stdout,[2022-11-07 14:50:47]  INFO: [BackupManager] 3 Backups Found
2022-11-07 14:50:47,stdout,[2022-11-07 14:50:47]  INFO: [LogManager] Init current daily log filename: 2022-11-07.txt
2022-11-07 14:50:47,stdout,[2022-11-07 14:50:47]  INFO: [RssFeedManager] Opened rss feed http://[serverUrl]/feed/li_7vuirnzmu1c5ptxlss
2022-11-07 14:50:47,stdout,[2022-11-07 14:50:47]  INFO: [Watcher] Initializing watcher for "Audiobooks".
2022-11-07 14:50:47,stdout,[2022-11-07 14:50:47]  INFO: [Watcher] Initializing watcher for "eBooks".
2022-11-07 14:50:47,stdout,[2022-11-07 14:50:47]  INFO: [Watcher] Initializing watcher for "Podcasts".
2022-11-07 14:50:47,stdout,[2022-11-07 14:50:47]  INFO: Listening on http://0.0.0.0:80
2022-11-07 14:50:48,stdout,[2022-11-07 14:50:48]  INFO: [Watcher] "Podcasts" Ready
2022-11-07 14:50:50,stdout,[2022-11-07 14:50:50]  INFO: [Watcher] "eBooks" Ready
2022-11-07 14:50:50,stdout,[2022-11-07 14:50:50]  INFO: [Watcher] "Audiobooks" Ready

There is a start-up error, but after that it still seems to start okay... So, it seems the server is running, but for some reason I get nothing. I'm not sure if the Listening on http://0.0.0.0:80 has always been there (in prior versions) and if that's okay, or somehow connected. I tried re-installing another container with v2.2.1 - same result.

---

Does anyone have any idea? Thank you.

[JakobTischler]

Well, three things:

1. I'm an idiot
2. Of course it was a port issue as I used the correct local port, but the wrong container port.
3. I'll see myself out...