CorneliousJD

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.

Thank you for continuing to update everyone on this, I appreciate it even though I've been able to work around the issue with a VLAN. My only "fixes" are workarounds for now - I'm only sharing them here to help people who are frustrated by the crasahes to do something free or at least very cheap (add a $15 NIC for another interface) to get around the issue. hoping someone here has real answers at some point though, that would be great! If there's anything else I can provide from my system please let me know, happy to keep providing logs/diags/etc.

What service is it? Out of curiosity at this point really. What about adding another NIC (if your motherboard doesn't already have 2 or more LAN ports?) That could be a very cheap $15 card for a gigabit NIC. https://amzn.to/3zfpmzF (referral link) I beleive that way you could keep the same IP address, but give it its own network interface instead?

Is there a reason you can't run a VLAN? (hardware doesn't support it?) Alternatively, you could add a 2nd NIC into your server and run it on a separate IP address from that I believe? I don't know the specifics of this exactly, but I think that would work so it's not assigned to br0 anymore? Also, are you able to simply not run that container on its own IP? I don't know of any other way besides those two options personally that will fix this. I had success with the VLAN method, and implemented it in less than 10 minutes total.

To each their own, a single vlan for Dockers is easier than setting up ESXi IMO. Well I agree, I didn't want to complicate my home network any further either, it was an extremely simple process that took me less than 10 minutes to complete. In my eyes 10 minutes to avoid crashes was definitely worth it. I've already linked to post somewhere in this thread that goes over the details of adding a docker VLAN, complete with photos!

Not a dev, but as noted in this thread a few times it's your br0 ones causing the issue. Not bridge vs host. You probably need to put those on a separate vlan. This is admittedly a workaround, but one that's worked for me. Stable with zero crashes since doing it over a month ago

So I would actually strongly recommend against using SQLite. SQLite in photo apps like this scales HORRIBLY and is bound to cause you all sorts of slowness, issues, and headaches. You would probably need to specify sqlite as a db driver tho. see here: PHOTOVIEW_DATABASE_DRIVER=mysql is the default. I would really just suggest spinning up MariaDB though, it's not difficult to do.

You can, or you can just create multiple databases inside of one MariaDB container. Choice is yours

@limetech Is there work being done on this still since it wasn't resolved as previously thought?

It's case sensitive, try /photos in the container, no capital.

New send container is working, however I cannot seem to get passwords to work, I enter something easy like "test" or "test123" as a password and it then tells me later the password is incorrect. EDIT - Disregard, once I actually set it all up via reverse proxy, it seems to be accepting passwords now. PS you do need some Redis persistence. I have mine setup like this, databse saved to appdata, and AOF disabled, to keep the Redis database extremly small (given it's expiring nature)

Sorry, I'm not using custom scrapers, but is there a config page that you have to tell it where the scrapers live? Would need to make sure that it matches up with what the container expects so the container path and your appdata for scrapers line up. Maybe someone else with Scrapers enabled can chime in here?