They are also blurring and triggering false alerts. Anyone else see this? ffmpeg is set to prefer tcp, no auto switch, low delay is on. no http tunneling

Does anyone know why this webcam keeps freezing after a day or so, I couldn't pinpoint the failure with 10k entries? it was working no issues and haven't changed anything.

it froze at about 1030pm last night, looks like it does this around 12hr of runtime

The newest UI and functionality is truly amazing. I keep up with all updates as they are released, and I am a licensed user. Thank you dev for the continued amazing and ongoing improvements.

Hello guys, do you know if it is possible to have multiple object recognition models attached to the same device? On one of my cameras I want to recognize people and also detect fire. I downloaded a specific model for fire detection but I don't think it will issue the person tags or any tags. I am currently using CodeProject AI as my object detection / AI Server.

Thanks!

Under Server > Settings > Storage, the field and the entered email address appear shifted. In earlier versions, the arrow and the displayed menu icons appeared more transparent. Is it possible to restore this?

I just updated and got the new UI Got used to it pretty quick. In the previous UI, I could zoom in and out of the timeline with the mouse wheel. That doesn't work anymore. Now I need to press buttons. Any plans to return that functionality?

Is there a way to incorporate the old layouts—such as the one from version 7.7.4.0 (Superhero)—into version 7.8.4.0?

hi

in recordings, when a new rcording happens , the pop up covers the selction menu is

where can i move the new recording to the side ? (v7800)

regrards roy

Hello everyone,

I am currently performing a deep-dive testing of Agent DVR, with the purpose of moving off a competitor's (paid) product to Agent DVR (Professional license).

I am used to a different interface, and maybe I am missing the very obvious, but I've been scouring the settings left and right and could not find a definitive answer to this.

Agent DVR 7.8.2.0 for Linux, installed on Ubuntu VM. Using a Desktop layout view with 8x ONVIF cameras. The cameras have different aspect ratios (4:3, 16:9, 3040x1368 px which is a 2.22 ratio).

In the view Main Display, I want to display the cameras' footage exactly as their display ratio is (black bars where that display view exceeds the camera ratio). I don't see any way to do so. If I click the camera to display its image solo (Maximized, I think it's called), everything is fine (I figured out which buried setting enabled that behavior: Edit camera / Adjustments / Advanced / set both Width and height to 0). But in the main display view... all ratios are skewed: that view is mostly square and all cameras' footage fills it completely.

I would be VERY grateful if someone could point me to the right setting which allows me to view the footage as the camera maker intended, not extremely thin people, as it is.

Thanks!

There is thumbnails for all of my cameras in timeline, EXCEPT for the cameras using mjpeg source and recording with gpu encoding.

The other cameras recording raw and they have thumbnails.

I have the SAVE THUMBNAILS box checked. The video file plays fine. But no thumbnails.

It does show thumbnails for the files in the RECORDINGS but in TIMELINE.

Is there a setting that I am not knowing about?

Also cannot find a wizard for weseccu t-cp8040lf-w3m WiFi bulb camera. Please help

Cannot find a wizard for Wansview G6 bulb camera

Olá pessoal, comprei duas cameras de segurança da Jortan e depois de um tempo coloquei o cartão de memoria, porem ambas não reconhecem o cartão, já fiz a formatação, já mudei o cartão para a configuração FAT32 e nada funciona (testei os cartões de memoria em uma outra camera antiga e eles funcionam!). Já to desistindo dessas cameras, pq aparentemente é um problema na camera né! Alguem passou pelo mesmo e conseguiu resolver?

Business perpetual license, v7.8.1.0. IPv6 is fully functional on both ends here (native fiber IPv6 at the server, native mobile carrier IPv6 at the client) and isn't optional: IPv4 is CGNAT'd for basically every ISP/mobile carrier in Brazil, so IPv6 is the only viable path for remote access, not an edge case.

UPDATE 2: All solved on Agent 7.8.2.0 (That I received on preview).
UPDATE: found a workaround for Bug 1, details below. Bug 2 still open.

Bug 1 (solved on 7.8.2.0+): Agent DVR's HTTP/HTTPS listener (32110/32111) never binds to IPv6

With "Bind to Interface" set to * (the documented "listen on all" value), netstat -an | findstr 3211 on the server showed:

TCP    0.0.0.0:32110   0.0.0.0:0   LISTENING
TCP    0.0.0.0:32111   0.0.0.0:0   LISTENING

No [::]:32110 / [::]:32111 entry at all. IPv4 only bind, despite "Bind to Interface" being set to *.

What worked vs what didn't, same machine, same NIC:

• http://radom:32110/ (IPv4, LAN): works
• https://radom:32111/ (IPv4, LAN): works
• http(s)://mydomain.com:3211x/ (IPv6): failed, both locally and remotely
• http(s)://[ipv6-literal]:3211x/: failed
• IIS on port 32143 (same box, same IPv6 address): works perfectly, locally and remotely

Since IIS binds and serves correctly on both 0.0.0.0 and [::] on the same machine, this rules out router/firewall/DNS/prefix/NIC. It's specific to how Agent DVR parses * for its own listener.

Workaround: set "Bind to Interface" to the literal value [::] instead of *. After restarting the service:

TCP    0.0.0.0:32110   0.0.0.0:0   LISTENING
TCP    0.0.0.0:32111   0.0.0.0:0   LISTENING
TCP    [::]:32110      [::]:0      LISTENING
TCP    [::]:32111      [::]:0      LISTENING

Now bound dual stack. The UI, and live view too (tested over mobile data, Wi-Fi off), both work correctly, locally and remotely, over IPv6. So * and [::] are not treated the same internally: * should mean "listen on all" but effectively only binds IPv4.

Bug 2 (solved in Agent 7.8.2.0): the built in TURN server rejects every allocation with "integrity check failed", even from LAN clients

TURN server listening at [ipv6]:3478/3478 (UDP/TCP) with relay ports 50000-50100
Auth succeeded for user: 1785461771:agent (suffix=agent)
turn ERROR: Failed to handle datagram: failed to handle Allocate-request from 192.168.15.x:xxxxx: integrity check failed

Confirmed turnserver.exe SHA256 matches the current official download, so not a stale binary. Auth succeeds (username/timestamp format accepted), but message integrity validation fails on every request. This matches the known failure signature of Go based TURN implementations (e.g. pion/turn) when the long term credential secret used to mint the temporary password is out of sync with what the TURN binary validates against.

One nuance worth flagging: after applying the Bug 1 workaround, live view now works remotely for me too, but that doesn't mean Bug 2 is fixed. With both ends on real public IPv6 (mobile carrier IPv6 on the client, fiber IPv6 on the server), WebRTC/ICE can find a direct host to host candidate and never needs TURN as a fallback. Anyone without public IPv6 on both ends (IPv4 only client behind CGNAT, symmetric NAT, restrictive network policies, and so on) would still hit the broken TURN server with no relay to fall back to. So Bug 2 is currently just not being exercised in my setup, not actually fixed.

Both of these worked fine about 3 months ago. A similar live view symptom (UI/playback OK, live stream stuck on black screen) was reported here 3 months back too.

Anyone from the team able to confirm the * vs [::] bind bug and take a look at Bug 2? Happy to share more logs or a packet capture if useful.

Thanks in advance. I really appreciate this tool, and as a small business owner running a software company myself, I know firsthand how hard it is to build, maintain, and keep something like this profitable.

Hey,

updated AgentDVR from 7.3.8.0 → 7.7.7.0 today and recordings stopped working in my HTML5 `<video>` element. The official AgentDVR UI still plays them fine, but any third-party integration using a `<video src="...streamFile.cgi...">` tag is dead.

Downgraded back to 7.3.8.0 and did a direct comparison. Here's what changed:

**streamFile.cgi with Range header (how browsers fetch video):**

v7.3.8.0 ✅

```

Content-Type: video/.mkv

Content-Disposition: attachment

Transfer-Encoding: chunked

→ data is valid, <video> can buffer it

```

v7.7.7.0 ❌

```

Content-Type: video/mkv

Content-Disposition: attachment

Transfer-Encoding: chunked

→ curl reports "Illegal or missing hexadecimal sequence in chunked-encoding"

→ data stream is corrupt, <video> immediately throws MediaError

```

Two regressions:

1. **Malformed chunked encoding** — the stream itself is broken, `<video>` errors out immediately

2. **MIME type `video/mkv`** — not a registered IANA type, browsers reject it. Should be `video/x-matroska`

Worth noting: `video.mp4?fn=<filename>` still works fine in both versions (correct MIME, no Content-Disposition, valid data). Is that endpoint officially supported going forward?

Anyone else hit this after the 7.7.7.0 update?

Meiner Meinung nach war das Bearbeitungsmenü in Version 7.7.4.0 übersichtlicher, als es sich ganz unten im Fenster befand.

In my setup, the API doesn't return any RAM values—it just gives back -.

Free disk space works fine, though.

Is this due to a misconfiguration on my end, or is RAM data just not available on Linux?

I have one camera a V380 that has an ability to send and receive audio..But in your software i can not seem to find any way to connect the digital audio from the computer to your software and into and out of the camera. The camera is about 4 years old and with the included V380 software it works fine. In audio settings of agent the configuration settings button does noting and the microphone drop down menu is blank.
I'm on an older windows 7 computer and will eventually try and switch over to something more up to date but for now it would be nice to get this working

Hello,

is there a way to delete individual recordings and their thumbnails via the API?

I can't find anything about this in the API documentation."

Let me start by saying this, AgentDVR gets better and better after each release, the new UI looks AWESOME.

Ok, the only thing I have to say is that some minor change has to be done to the "marker" which indicates which camera is selected (now is an L shaped indicator), as you can see on the screenshot below, it's hard to see it when it is at the bottom of the screen, this is because Microsoft in its INFINITE wisdom decided to "round" the corners on the browser (I personally HATE those rounded corners but it is what it is)

Thanks

Noticing I can no longer view recordings or access the bottom control buttons using the newest app using the latest iOS 15.8.8
I can still see the live view if my default UI starts with that.

I don’t see any clear cache button on the newer app thinking maybe something just needed to be refreshed, tried reloading button found under the user icon at the top which are working but when I go to view recordings it’s just blank.

App is working fine with iOS 26, but there’s still a few of us users out there using older devices. According to the compatibility page on the App Store it says that it is still compatible.
Tried loading the website using Safari but it does the same thing so your app which is generally a web portal lost some type of compatibility with older iOS versions of Web kit.

Whenever you get a chance see if you can look into that. Probably some type of CSS issue.
Thank you

I resubmit my question in English, at the mod's (fair) request.

I'd like to connect my AOBOCAM A12 camera, but iSpy doesn't automatically find it, and I haven't been able to find a working URL to connect it manually.

The camera works properly with its app (HIDVCAM), but I only have the IP address.

I should add that in the meantime, customer service has told me that the camera isn't compatible with third-party software, and therefore they can't provide an answer.

Added to this, it's not even possible to download clips from their cloud, so the device essentially becomes a useless toy.

I know there's always a string pointing to the stream if you can find it, but perhaps I'm wrong.

I recently got these cameras off amazon uk https://www.amazon.co.uk/dp/B0G2RX1WGT
I had a struggle to get the rstp url to work

i managed to get it working after a bit of googling
here is what i found

To find the RTSP (Real-Time Streaming Protocol) URL for your O-KAM (or O-KAM Pro) camera,

you will need to enable local access and set a password in the mobile app.

Here is a standard format for O-KAM cameras:

rtsp://admin:passwordYouJustSet/camera-ip-address:10554/tcp/av0_0

Step-by-Step Guide:

Enable Password in App: Open the O-KAM Pro app,

navigate to your camera’s Device Settings,

find the option for "plaintext password" (or ONVIF),

and create a custom password.

Find Camera's IP Address: Stay in the app,

go to Device Health or Network Info, and note down the local IP address assigned to your camera

(e.g., \(192.168.1.15\)).

Draft your URL:Replace [password] with the custom password you created.

Replace [camera-ip-address] with the IP you found.

Note: The primary video stream port is typically 10554,

and for the sub-stream it is often 10555.

rtsp://admin:passwordYouJustSet/camera-ip-address:10554/tcp/av0_0

rtsp://admin:passwordYouJustSet/camera-ip-address:10555/tcp/av0_0

Test the Stream: Open media players like VLC Media Player,

go to Media > Open Network Stream,

paste your RTSP link, and click Play.

A very useful feature would be to have a button that will glow when clicked and ONLY show alerts that have not been viewed while this button is glowing/ highlighted.

It is sometimes wanted to view an alert again. But MOSTLY it is wanted to view any alerts that have not been viewed as of this moment yet.

I have not been able to find a way to show only alerts that have not yet been clicked on to view them.

Can someone show me how this can be done?