ZoneMinder Forums

Caveat: this applies to iCsee WiFi/wired cameras that I have. At the least the username/password is required for mine, but maybe not on poe. rtsp://192.168.1.219/user=admin_password=[password]_channel=0_stream=1.sdp?real_stream Mine work with method TCP or UDP. The username is not changeable, althou...

You're right.
We probably ought to have the "right" instructions pinned somewhere, so when the question comes up we can just tell them where to look.

OR, maybe a new "New to Zoneminder? Install tips." or similar would be where to put it.

That's an AWS ip, pretty sure it's the ZM telemetry. Which is down due to expense.
There used to be a checkbox to turn it off. I suspect if you go to Options->Privacy->(choose) Decline, then Apply, that will stop it.
Port 443 is the normal https:// port, BTW.

Because it's in Monitor Function/mode.

However, if you use the recommended script, that's in there.

You didn't follow the example - control device.
maybe just /onvif or as shown: or something else entirely. No telling without specs, I don't see it in the iSpy list but feel free to see for yourself.

What have you got in the monitor control page?

See my earlier example. I can't guarantee anything because I can't find anything useful about this camera.
Something like <your_user>:<your_password>@192.168.1.180:8000/onvif
You might not need the user:password part, experiment and check the logs to see the camera response, if any.

doug@doug-MS-7A38:~$ nmap 192.168.1.222 Starting Nmap 7.80 ( https://nmap.org ) at 2024-03-29 02:33 PDT Nmap scan report for 192.168.1.222 Host is up (0.55s latency). Not shown: 996 closed ports PORT STATE SERVICE 80/tcp open http 554/tcp open rtsp 1935/tcp open rtmp 8080/tcp open http-proxy Nmap d...

Have you run nmap against it since reset?

So the camera's in focus again?
Have you tried any of the onvif tools out there or in zm?

I power cycled the camera and now my Desktop's Terminal on the LAN can ping 192.168.1.180.
However the web borwser can't reach the site http://192.168.1.180.
Today, the Desktop cannot ping 192.168.1.180 nor browse?

Starting to sound like possible power supply problem - can you replace/change?

I've seen this.
The fault before you change it is NULL for default. If you set it default, it's 0. Or whatever your default storage ID is.

Maybe shot in the dark, but is decoding NOT None on the source page?

Ugh - yes, of course :oops: Still, 1.37.56~20240323133909-jammy is not broken, so don't know what happened. My experience with this problem was first no apache and then mis-configured, but that only happened on a new install of zm from scratch. If this is on bare metal suggest you just re-install - ...