Scott Lamb

Thanks. That log has a smoking gun here: ``` Aug 14 21:05:51 moonfire moonfire-nvr[710]: Aug 14 21:05:51.538 INFO reserved 590d892d-b2e8-4e6c-9e1b-c4418d0abd69 Aug 14 22:37:39 moonfire systemd[1]: Time has been changed Aug...

I think I'll implement this idea from https://github.com/scottlamb/moonfire-nvr/issues/156#issuecomment-908568225: > I suppose I could force a new run to start if there's been a time jump (details below), splitting the RTSP...

> Yes, a goal I have in mind is determining what the time-out for the Live555 server running in a Reolink camera is. That part's easy. It's 65 seconds. They...

Yeah, that level of delay is undesirable for sure. But we can discuss that more at https://github.com/scottlamb/retina/issues/17; I'd like to keep this issue for the backoff.

This would be very convenient, and @JasonKleban had a similar idea in #118. > How would the proxy map the camera ports (all typically going to be port 80) to...

> Or a totally different approach: run up a SOCKS proxy with username/password that allows connecting to configured cameras. It wouldn't be as slick on the client side (you'd have...

Speaking of crappy cameras and broken web UIs, another caveat is that for some cameras, their Windows/macOS software is that uses a custom non-HTTP protocol is more functional than their...

I'd think the name-based setup would be pretty easy if well-implemented in Moonfire. I'm assuming if you're you're setting up access from outside, you're setting up some kind of DNS...

Finally getting there. Some remaining things to do: [moved to first comment to make the issue more skimmable] It'll be a lot more slick once we support built-in https (see...

I still don't have all the checkboxes ticked, but it works okay for me, and it shouldn't urgently require schema changes, so I merged it to master.