[BUG] Fail to upload child picture, error 500

[rikrdo89]

Is there an existing issue for this?

• I have searched the existing issues

Current Behavior

I used to be able to upload pictures for the childrens' profile, but as of version 2.0.2 (docker container), uploading photos throws error 500, and no photos are shown in the web app.

When I go to the webapp under [Home] >[Children] > [Joe Doe] > Update , it shows a path for the photo I was trying to upload, despite having thrown an error earlier:

Currently: child/picture/myphoto.jpg

On the server side, that path does correspond to the correct file, but the CACHE folder does not have the file I just uploaded, it only has a folder for an old photo I uploaded before the upgrade.

$  ls media/child/picture/
myphoto.jpg
previousPhoto.jpg

$ ls media/CACHE/images/child/picture/
previousPhoto/previousPhoto.jpg

My compose.yaml looks like this (domain and port are obscured)

version: "2.1"
services:
  babybuddy:
    image: lscr.io/linuxserver/babybuddy:latest
    container_name: babybuddy
    environment:
      - TZ=EST
      - PUID=1000
      - PGID=1000
      - CSRF_TRUSTED_ORIGINS=http://127.0.0.1:MYPORT,https://MY.DOMAIN.com
      - SECURE_PROXY_SSL_HEADER=True
    volumes:
      - /home/docker_apps/babybuddy:/config
    ports:
      - MYPORT:8000
    restart: unless-stopped

I have an Apache server running in the same machine that proxies requests from https://MY.DOMAIN.com to the babbybuddy docker app. I tested uploading different photos, both within my LAN and outside my LAN and I get the same error.

In the web app, all the the child profile pictures that have a reference url as: https://MY.DOMAIN.com/media/CACHE/images/child/picture/previousPhoto.jpg show the image just fine. But the profiles pictures that have a reference url as: https://MY.DOMAIN.com/children/children_name/ does not show any image.

Otherwise babybuddy works without issues.

Expected Behavior

No response

Steps To Reproduce

see above.

Environment

- OS:Ubuntu 20.04

CPU architecture

x86-64

Docker creation

see above

Container logs

using keys found in /config/keys
Operations to perform:
  Apply all migrations: admin, auth, authtoken, axes, babybuddy, contenttypes, core, dbsettings, sessions
Running migrations:
  Applying babybuddy.0028_alter_settings_language_alter_settings_timezone... OK
  Applying dbsettings.0001_initial... OK
  Applying core.0026_alter_feeding_end_alter_feeding_start_and_more... OK
  Applying core.0027_alter_timer_options_remove_timer_duration_and_more... OK
  Applying core.0028_alter_sleep_options_remove_sleep_napping_sleep_nap... OK
  Applying core.0029_alter_pumping_options_remove_pumping_time_and_more... OK
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                                                                   │
├────────────┼────────────┼────────────────────────────────────────────────────────────────────────┤
│ 2022-08-16 │ 2023-04-13 │ /config/nginx/nginx.conf                                               │
│ 2022-11-23 │ 2023-07-05 │ /config/nginx/site-confs/default.conf                                  │
│ 2022-08-20 │ 2023-06-24 │ /config/nginx/ssl.conf                                                 │
└────────────┴────────────┴────────────────────────────────────────────────────────────────────────┘
[custom-init] No custom files found, skipping...
[2023-07-14 09:22:11 -0500] [257] [INFO] Starting gunicorn 20.1.0
[2023-07-14 09:22:11 -0500] [257] [INFO] Listening at: http://127.0.0.1:3000 (257)
[2023-07-14 09:22:11 -0500] [257] [INFO] Using worker: gthread
[2023-07-14 09:22:11 -0500] [276] [INFO] Booting worker with pid: 276
[2023-07-14 09:22:11 -0500] [277] [INFO] Booting worker with pid: 277
[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.

[LinuxServer-CI]

This issue has been automatically marked as stale because it has not had recent activity. This might be due to missing feedback from OP. It will be closed if no further activity occurs. Thank you for your contributions.

[github-actions]

This issue is locked due to inactivity