[BUG] Issue accessing Baby Buddy on :v2.6.3-ls168/v2.6.3-ls169

[Dinth]

Is there an existing issue for this?

• I have searched the existing issues

Current Behavior

Since the update to :v2.6.3-ls168 Baby Buddy web interface stopped working. API access still works fine.
When trying to access Baby Buddy through a web browser, usually its just spinning for a couple of minutes before showing 502 Bad Gateway error. Sometimes (very rarely) it shows the login window without any CSS (502 error on CSS files according to Developer Tools in the web browser).
No mention of the access attempt (ones ending with 502 error) in container's log, nor in the built in nginx's access or error.log.
The issue disappears after reverting to v2.6.1-167.

Expected Behavior

Baby buddy web interface should show up

Steps To Reproduce

The issue started after the upgrade and server restart, im not sure how to reproduce it.
Right now v2.6.1-ls167 works, but ls168 and ls169 dont work, pulling the image doesnt help either

Environment

- OS: Debian 6.1.90
- How docker service was installed: Portainer

CPU architecture

x86-64

Docker creation

Container logs

[migrations] started

[migrations] 01-nginx-site-confs-default: skipped

[migrations] 02-default-location: skipped

[migrations] done

usermod: no changes

───────────────────────────────────────

      ██╗     ███████╗██╗ ██████╗

      ██║     ██╔════╝██║██╔═══██╗

      ██║     ███████╗██║██║   ██║

      ██║     ╚════██║██║██║   ██║

      ███████╗███████║██║╚██████╔╝

      ╚══════╝╚══════╝╚═╝ ╚═════╝

   Brought to you by linuxserver.io

───────────────────────────────────────

To support the app dev(s) visit:

BabyBuddy: https://github.com/sponsors/cdubz

To support LSIO projects visit:

https://www.linuxserver.io/donate/

───────────────────────────────────────

GID/UID

───────────────────────────────────────

User UID:    911

User GID:    911

───────────────────────────────────────

Linuxserver.io version: v2.6.3-ls168

Build-date: 2024-11-07T03:49:41+00:00

───────────────────────────────────────

    

using keys found in /config/keys

Operations to perform:

  Apply all migrations: admin, auth, authtoken, axes, babybuddy, contenttypes, core, dbsettings, sessions

Running migrations:

  No migrations to apply.

  Your models in app(s): 'babybuddy' have changes that are not yet reflected in a migration, and so won't be applied.

  Run 'manage.py makemigrations' to make new migrations, and then re-run 'manage.py migrate' to apply them.

Cache table 'cache_default' already exists.

**** The following active confs have different version dates than the samples that are shipped. ****

**** This may be due to user customization or an update to the samples. ****

**** You should compare the following files to the samples in the same folder and update them. ****

**** Use the link at the top of the file to view the changelog. ****

┌────────────┬────────────┬────────────────────────────────────────────────────────────────────────┐

│  old date  │  new date  │ path                                                                   │

├────────────┼────────────┼────────────────────────────────────────────────────────────────────────┤

│ 2023-07-05 │ 2024-07-16 │ /config/nginx/site-confs/default.conf                                  │

│ 2023-06-24 │ 2023-08-13 │ /config/nginx/ssl.conf                                                 │

│ 2023-04-13 │ 2024-05-27 │ /config/nginx/nginx.conf                                               │

└────────────┴────────────┴────────────────────────────────────────────────────────────────────────┘

[custom-init] No custom files found, skipping...

nginx: [warn] the "listen ... http2" directive is deprecated, use the "http2" directive instead in /config/nginx/site-confs/default.conf:7

nginx: [warn] the "listen ... http2" directive is deprecated, use the "http2" directive instead in /config/nginx/site-confs/default.conf:8

[2024-11-14 09:49:00 +0000] [263] [INFO] Starting gunicorn 23.0.0

[2024-11-14 09:49:00 +0000] [263] [INFO] Listening at: http://127.0.0.1:3000 (263)

[2024-11-14 09:49:00 +0000] [263] [INFO] Using worker: gthread

[2024-11-14 09:49:00 +0000] [284] [INFO] Booting worker with pid: 284

[2024-11-14 09:49:00 +0000] [285] [INFO] Booting worker with pid: 285

Connection to localhost (127.0.0.1) 3000 port [tcp/*] succeeded!

[ls.io-init] done.

[github-actions]

Thanks for opening your first issue here! Be sure to follow the relevant issue templates, or risk having this issue marked as invalid.

[j0nnymoe]

The container logs are telling you that your nginx configs need updating. The container is starting fine in our test so that could be your problem: https://ci-tests.linuxserver.io/linuxserver/babybuddy/v2.6.3-ls169/index.html

Also worth noting we do not support/recommend portainer for deploying our containers. https://docs.linuxserver.io/misc/support-policy/#unsupported

[Dinth]

Unfortunately updating nginx config files and restarting the container has not changed anything.
I think that potentially the issue may be with the caching service (it seems that there's something running on port 3000 within the container), as those 502 requests never reach nginx (they are not logged in access/error log), im just not sure how to troubleshoot it?

[Dinth]

Dont mind me, i found the root cause and it has nothing to do with this container.
For some reasons, docker was spinning up two different containers (incl Baby Buddy) with the same automatically assigned mac address