babybuddy container wont start: "nginx: [emerg] no "events" section in configuration"

[HarmlessSaucer]

EDIT: I originally posted this as an issue, but this probably isn't a bug with Babybuddy but somethign specific to my config, so I deleted the issue and moved here:

Hey, I recently started getting a 502 error from NGinx Proxy Manager which I run Babybuddy behind, so I went to investigate.

The logs for the (linuxserver.io) container read:
nginx: [emerg] no "events" section in configuration

I was running 1.15.1 but updated to 1.16.0 and I'm getting the same thing.

From what I can see my config is accessible to the host.

Looking in the logs as it starts up, I can see the following:

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-04-13 │ /config/nginx/nginx.conf                                               │
│ 2022-04-03 │ 2022-11-23 │ /config/nginx/site-confs/default.conf                                  │
└────────────┴────────────┴────────────────────────────────────────────────────────────────────────┘
[custom-init] No custom files found, skipping...
nginx: [emerg] no "events" section in configuration
[2023-06-10 23:38:46 +0100] [245] [INFO] Starting gunicorn 20.1.0
[2023-06-10 23:38:46 +0100] [245] [INFO] Listening at: http://127.0.0.1:3000 (245)
[2023-06-10 23:38:46 +0100] [245] [INFO] Using worker: gthread
[2023-06-10 23:38:46 +0100] [256] [INFO] Booting worker with pid: 256
[2023-06-10 23:38:46 +0100] [257] [INFO] Booting worker with pid: 257
nginx: [emerg] no "events" section in configuration
[ls.io-init] done.
nginx: [emerg] no "events" section in configuration

Is anyone able to point me in the right direction here? 🤔

[HarmlessSaucer]

So, just tracking this for my own interest mainly.
I saw in the top of the logs:

┌────────────┬────────────┬────────────────────────────────────────────────────────────────────────┐
│  old date  │  new date  │ path                                                                   │
├────────────┼────────────┼────────────────────────────────────────────────────────────────────────┤
│            │ 2023-04-13 │ /config/nginx/nginx.conf                                               │
│ 2022-04-03 │ 2022-11-23 │ /config/nginx/site-confs/default.conf                                  │
└────────────┴────────────┴────────────────────────────────────────────────────────────────────────┘

I went and found these files in my volume, and /config/nginx/nginx.conf for whatever reason was completely empty. /config/nginx/site-confs/default.conf had an expected configuration in it.

I restored a backup of just that file... and boom. Issue resolved!

NO idea how or why that file got completely blanked, but keep backups people!
KEEP BACKUPS! :)

Thanks so much for the incredible software! :) I need to donate on GH again!