Hello everyone, made a plugin that integrates signal notifications into unraid notifcations page. You must have signal-cli installed somewhere either on the same system or elsewhere.

- Plugin name: Signal Notification Agent

- Repository URL: https://github.com/ghzgod/signal-notification-unraid

- Plugin URL: https://raw.githubusercontent.com/ghzgod/signal-notification-unraid/main/signal-notification.plg

- Support thread URL: (the forum thread you created)

- Icon URL: your signal-notification.png

I have like 3 unraid accounts but I cant login with just username anymore hence why this account is brand new. Been on unraid since 2015, and this is my first submission. Feel free to leave feedback.

2FA is enabled on my github account
The support URL in the .plg points to this thread.

Edited February 11Feb 11 by ghzgod11

Here is a screenshot of it.

Thanks for this, but I get a 404. I'm running the API on a custom br0 network, but I've tried running it on the normal bridge as well with the same result.

Hey, just now seeing this, sorry for the late reply. Which version of signal CLI docker image are you running?

I'm running the latest of bbernhard/signal-cli-rest-api.

So my readme has the requirement (ghcr.io/asamk/signal-cli with daemon --http mode). But I'm gonna modify the plugin right now to auto-detect which image the container using and auto switch over if possible. I'll report back soon.

Edited February 21Feb 21 by ghzgod11

Aha, I thought I could use any signal-cli image. Awesome, thanks :)

When you get a chance, can you test this? https://raw.githubusercontent.com/ghzgod/signal-notification-unraid/beta/signal-notification.plg

I get this error when installing: plugin: bad file MD5: /boot/config/plugins/signal-notification/signal-notification.txz

Remove the old plugin (if installed) and then reinstall with that link

Yeah, I did that.

3 minutes ago, strike said:

Yeah, I did that.

I made a change, can you try again? Hopefully it works now

Now it installs and connects as long as the signal-cli container is in bridge mode. It will probably work with a custom network if I either enable host access to custom networks or just manually add a route myself. Testing that later, but now I'm gonna test that it works in bridge first. Thanks for the support so far. I'll be back if I see some more issues.

I'll add that fix right now. I just found another bug that doesn't auto detect the port that the container's running on. So I'm fixing that as well.

Also, you can update the plugin via the plugins page by clicking Check for updates. And if I push a new update it will show there.

Yeah, I know, thanks :)

Awesome. I just added the ability for it to work in host mode, bridge mode, and custom IP address mode. Whenever you get a chance, please test that. And I appreciate your patience.

I've confirmed it works and sends notifications now. But a note for other users with the same macvlan setup as me. If your signal-cli container runs on a custom network with its own IP you either need to go to settings-Docker, disable docker and enable host access to custom networks (this will enable it for all containers). I don't want that, as I want as few containers as possible with access to the host. So if you just want to enable access just for the signal-cli container, you can add this script to the user script plugin and set it to run at array start.

#!/bin/bash
# 1. Create a new macvlan interface on the host named "host-shim" attached to br0
ip link add host-shim link br0 type macvlan mode bridge

# 2. Assign an UNUSED local IP address outside you DHCP range to this new interface
ip addr add 192.168.2.250/32 dev host-shim

# 3. Bring the interface online
ip link set host-shim up

# 4. Tell the host to route traffic for your signal-cli IP specifically through this new shim
ip route add 192.168.2.222/32 dev host-shim

You know, that's very smart because if you enable that setting, it would give every container the ability to access the host network, correct? And if there's a malicious update, (which I still don't understand if we're even checking for that stuff somehow), you would minimize the ability for it to pivot onto the network?

Yeah, that's correct. I like to keep as many containers as I can on the custom network with their own IP (and host access disabled) just for security reasons. But it adds some extra complexity, so it's not for everyone.

Hey, sorry for the noob question. Any idea how to get this plug in on the Unraid App Store? I feel like I did all the right steps, but I still don't see it. Maybe they haven't had a chance to review it or something. Is it still working okay for you? And I appreciate all your help by the way. I never got to mention that.

23 minutes ago, ghzgod11 said:

Hey, sorry for the noob question. Any idea how to get this plug in on the Unraid App Store? I feel like I did all the right steps, but I still don't see it. Maybe they haven't had a chance to review it or something. Is it still working okay for you? And I appreciate all your help by the way. I never got to mention that.

Did you fill out the submission form and made a template for the plugin? If you have, you just have to wait. It can take some time. It took about 3-4 weeks when I submitted mine. And plugins gets extra scrutiny because they have access to the OS itself. Your plugin continues to work well 😊

Thank you. Not that I would do this because it's highly illegal, but what would stop someone from developing a plugin, getting it approved on the app store, and then putting malicious code into the plugin in a future update down the road? I probably should do my own research on this, but I hope that Unraid has some kind of failsafes for this or they have some auto checking capability. I feel like accomplishing this task like this is pretty trivial now that we have AI agents everywhere that could auto reject or flag updates for security protection.

1 hour ago, ghzgod11 said:

Thank you. Not that I would do this because it's highly illegal, but what would stop someone from developing a plugin, getting it approved on the app store, and then putting malicious code into the plugin in a future update down the road? I probably should do my own research on this, but I hope that Unraid has some kind of failsafes for this or they have some auto checking capability. I feel like accomplishing this task like this is pretty trivial now that we have AI agents everywhere that could auto reject or flag updates for security protection.

Unraid staff have to answer this. But I know they're vetting the plugins before releasing them on the app store. If they do it manually or have some checks in place, I do not know. What happens when someone is releasing an update is a good question, I don't know if checks are in place or not. Did you merge your latest updates from the beta to the main plg btw?

1 hour ago, strike said:

Unraid staff have to answer this. But I know they're vetting the plugins before releasing them on the app store. If they do it manually or have some checks in place, I do not know. What happens when someone is releasing an update is a good question, I don't know if checks are in place or not. Did you merge your latest updates from the beta to the main plg btw?

Yes, I merged it in the main branch. Sorry, I forgot to mention it.