danielaranki

I suspect that the rebase to Alpine 3.19 a couple of months ago may have caused this. According to https://www.alpinelinux.org/posts/Alpine-3.19.0-released.html > iptables-nft is now the [default](https://gitlab.alpinelinux.org/alpine/aports/-/commit/f87a191922955bcf5c5f3fc66a425263a4588d48) iptables backend. Whereas unraid...

Bump

Thanks for the quick reply. I appreciate your help. > It seems to work fine for me: I'm trying to write a full custom plugin (e.g., https://github.com/caronc/apprise/wiki/DemoPlugin_Basic), not a decorator...

Thanks. I will try injecting the code in the core path. I think the documentation currently states > It's very important to save the apprise/plugins/NotifyServiceName.py to be exactly the name...

Thanks for confirming. I will try that. Regarding the logger issue. Are you able to produce it on your end? This should produce it: `apprise -vvvv -b "test message" -t...

I understand re `@notify`. The logger issue seems unrelated to custom notifications. That's why I provided a line that doesn't load a custom plugin or use any custom notification. Do...

It's a dockerized setup (from https://hub.docker.com/r/caronc/apprise). Let me try a clean new container (fresh install) and report back to you. Again, I appreciate your time.

Of course, this is not pressing or urgent. Thanks for the help, I'll report back and wait for your reply whenever you get to it.

The logging errors still persist in a fresh docker install. Here's a setup from scratch (fyi, `./config` is empty; also this is not specific to `signal://` and can be reproduced...

For further context, I tried this on two different machines running different host OSs, with the same results.