[BUG] - Test Webhook Button No Longer Works (Nuxt Upgrade)

[jtweaver]

First Check

• This is not a feature request.
• I added a very descriptive title to this issue (title field is above this).
• I used the GitHub search to find a similar issue and didn't find it.
• I searched the Mealie documentation, with the integrated search.
• I already read the docs and didn't find an answer.
• This issue can be replicated on the demo site (https://demo.mealie.io/).

What is the issue you are experiencing?

I saw in the features that this includes the ability to configure notifications and Webhooks, but I see no where to configure that.

Steps to Reproduce

1. Login with OIDC as an admin user
2. Check settings (nothing about notifications/webhooks)
3. Click everywhere looking for webhooks or notifications
4. Read the docs (find no docs on configuring the Webhooks)
5. Look at the environment variables (nothing for configuring webhooks)
6. Make sure the active user is an admin (check)
7. Shamefully post a bug ticket when there probably isn't a bug but just a confused foodie

Please provide relevant logs

No logs relevant here

Mealie Version

2.8.0

Deployment

Docker (Linux)

Additional Deployment Details

OIDC via Authentik

[michael-genson]

You can find webhook configuration by clicking on your profile. If you don't see it, you probably don't have advanced settings enabled (which you can also configure from there)

[AlexStormwood]

This is not a "turn on the advanced settings option" issue, but is either a documentation issue or an actual functionality issue. As a new Mealie user, I don't know enough about this app to know if it's broken or not - especially when there's little documentation about this webhook functionality!

Here is the current documentation about webhooks on the docs.mealie.io site:

The demo site has no webhooks configured for us to compare with, so there is nothing of value there. Even putting a typical Discord channel webhook into the demo site does not work.

There's another page that mentions webhooks, but just one sentence that is literally "If you want to use ntfy, you will need to install it on your environment, or sign up for their service, and configure it with the webhook URL.".

So, there is currently no documentation on how to actually set up the webhook functionality.

I've used webhooks in other apps before, so I have no idea if this app has some specific config steps that we're meant to follow. I've got webhooks working for Jellyfin, FreshRSS, Scrutiny, Sonarr, Radarr, Prowlarr, Yamtrack, and GitHub Actions. All as Discord webhooks. I don't know what I would be missing here in Mealie's webhook config, as there is no documentation about that.

Like, is this Discord webhook URL meant to need further configuration?

Is the webhook test button broken? Or are webhooks overall broken in Mealie? Or am I missing a configuration step? Documentation, right now, gives no answers.

[michael-genson]

Looks like the test webhook button stopped working with the Nuxt upgrade. It's possible webhooks in general are broken but more likely just the test webhook button.

Documentation, right now, gives no answers.

You're not missing anything, hence why there's nothing additional in the documentation. The paragraph in your screenshot is, quite literally, all you need to know about webhooks (well, if they work 😉)

[AlexStormwood]

Thankyou, Michael.

If it helps: I enabled that Discord webhook from my screenshot after posting my comment last night, it was due to trigger at 10am Sydney time this morning (almost 2 hours ago), and nothing has happened.

I set LOG_LEVEL to "debug" in the container environment variables after seeing that nothing has happened, but the webhook tester button does not seem to trigger any additional logs with that set. Just the usual log about the Mealie web client sending in a POST request:

INFO 2025-07-27T11:39:25 - [client-ip-was-here:56168] 200 OK "POST /api/households/webhooks/webhook-id-removed-for-github-issue-comment/test HTTP/1.1"

[michael-genson]

Hmm, if it's sending that request to the backend that it might actually be a backend issue. That would surprise me since it definitely should be working, but I'm not sure. Haven't had a chance to look at this one yet.