CorneliousJD

thanks for this, I'll add it to the first post and credit you for this

Glad you have things working for you - I'm actually not the developer and have nothing to do with the development of this app, I just created the docker container template for unraid to bring it to unraid users easily. You may want to check the developers github page to see if they have this as planned features or ping them there to see. Good luck!

That would work with the variable for sure, and I look forward to the rest of the customzations going live, I think this will become out go-to option once those are all finished, thank you!

Thanks for all this! I really like PWPush! I ended up using another option in production (OneTimePassword) because the container I used has CSS/logo customizations, etc, and we needed it to be branded, but I would definately reconsider once PWPush has that feature. I REALLY like the audit logging too, thank you for that. If I could request one more feature it would be the days/views and use "1 click password retrieval" to be an option to set somewhere too so it's a global default. Our whole team would need that set. Ideally a way to let it NOT be overridden too, e.g. our team ONLY sends passwords that can be viewed ONCE and that's it for safety reasons.

I don't use SWAG because of this, I have had so many issues with apps not working behind it without extensive confirutation changes. I have UptimeKuma running in NPM (NGINX Proxy Manager) without any additional changes or config for what its worth... Works great!

Excellent, glad to hear it! I have had weird bugs since 9.6 and that was one of them. Implemetning VLANs though for my custom IP containers fixed everything. I had the necessary hardware to support VLANs already so it wasn't a big deal for me to change. Glad it's working now though, enjoy!

I do have an idea, have you ever experienced a crash of the system since upgrading unraid to 6.9.X? If so I had an issue (currently logged as a bug w/ limetech already) where after a crash, my host access to custom docker network would stop working (despite showing enabled). I had to stop docker enlgine, turn the acces off, save, and turn it back on, save, and then start docker engine again for it to actually work. I'd say it's worth a shot! If that does fix it, you'll need to remember to do the same thing after any other crashes. I was able to personally avoid any furhter crashes by moving from br0 to br0.10 (putting it on a VLAN) For more info on the crashes/vlan issue, see here:

That is odd, I'm not sure exaclty how to help with that off hand, I CAN ping my PiHole br0 IP address from my unraid command line. Only difference between our setups is my PiHole is on a br0.10 (VLAN 10). Might be a good opportunity to start a thread in general unraid support and bring up that you have a custom br0 docker container and the unraid command line is unable to ping it - I'm sure someone can help point you in the right direction. Once you have that resolved, the UptimeKuma ping to your Pihole br0 docker should work successfully

I have a similar br0 PiHole setup, just tested and working for me to ping from Uptime Kuma, so I'm not sure what issue you'd be running into. From the command line of unraid server, are you able to ping 10.0.0.254 successfully?

You need to turn on communication between docker host and macvlan networks to allow the to communicate. Try turning off docker engine in settings then the option to turn that on should be there, then enable docker engine again.

Currently (info gotten from GitHub) is that it only passes on a VALID SSL cert, and if it's a self-signed or epxired cert it will fail the check, so for now it's checking validity. The dev did mention he plans to add a toggle to ignore invalid certs though in the future too.

Uptime Kuma is a status monitor, similar to Uptime Robot that supports multiple notifications systems. Docker is based off official container, very simple and easy to use! If you have issues with the software, please contact dev on his github page here https://github.com/louislam/uptime-kuma Post here if your issue is specific to unraid setup/docker implementation for Uptime Kuma.

So it looks like they changed the port number for some reason from 5000 to 5100... try changing these manually. I'll edit my templates and push updates to CA After I edited everything to 5100 it works. REMINDER: Toggle advanced on and edit the WebUI port as well to 5100

Can you describe what you mean about the path before installing? Perhapsd a screenshot will help? Also, if you're interested in another container, I personally run OneTimePassword istead of Password Pusher now, both are good options though!

Perfect, was waiting for this. I'm going to migrate over to the official docker container this weekend (time permitting) Appreciate you putting this together for us.