Hi @OzzyBill 

Thanks for posting in our business forum.

Don't know your description about /root and /f. Anyway, you should be accessing the IPC by http://ip and it should be accessible in most cases. I have never experienced a problem with the web access.

If you have altered something and it happens now, you should rewind what's been changed.

Hi @OzzyBill 

Thanks for posting in our business forum.

OzzyBill wrote

Thanks  @Clive_A ,

 

By "root" I mean the top level directory eg. "/".

 

I have to use "https" - I get a "connection refused" if I use "http".

My camera address that I'm using looks like this:   https://192.168.37.2/

 

It's worked in the past.

 

I've got 2 x C300HP cameras and they're both doing this.

 

I've got a C340 and a C430 and both of these work fine with the same type of address (different IP of course - but these also require https and won't accept http.)

 

What's strange is that camera's are otherwise working fine on both the mobile app, the NVR web interface, and the Vigi Security Manager interface (maybe they're working over the ONVIF interface? and it's just the "http/https" interface that is broken?)

 

Regards, Bill.

443 is the port for the web and control. I intended to show you that we use that kind of format for the GUI instead of http(s)://ip/root/etc/ or anything like that. We don't have that access or gain you the authority of the root.

What's the full URL you used for the /root thing? I don't recall that we support that.

I know that after you log in to the web you can click different tabs and the URL will change differently. But this is something new to me. If you are accessing something from the code-leve, we don't support that and from our tradition we may ban some access from the root level.
e.g. the router used to allow the SSH and you can root it but we later changed the password for the root and did not reveal this information to users.

Hi @OzzyBill 

Thanks for posting in our business forum.

OzzyBill wrote

Hi  @Clive_A ,

 

I'm not using any path.  "root" means "root directory" which means the directory at path "/".  Not to be confused with "root" user.

 

This is the URL I am using:

 

https://192.168.37.2/

 

Going to that URL returns the message:

 

No such file or directory

 

Screenshot attached:

 

 

 

 

Regards, Bill

OK. In the first post, you said that they can work well on the NVR. So, you still get an image from the NVR. Correct?

If so, I can confirm your IP addresses are correct. If this is not the case, you don't have the live from the NVR, that might be an incorrect IP address. You should examine the ARP table to find out their IP addresses.

Move on to the next, have you tried the incognito mode? Will clearing the cache work for the access?

What's the result if you try this line in CMD?

telnet 192.168.37.2 443

                  |               |

             host ip        port

Hi @OzzyBill 

Thanks for posting in our business forum.

OzzyBill wrote

Thanks @Clive_A 

 

The camera is recording and has fresh content available on the NVR's website, and also in the Vigi Security Manager application.  Both apps also confirm the IP address of the camera.  I can see the IP address is listed against the MAC address of the camera (in an arp print.)

 

I did a telnet check and an nmap check - both results are in the attached file (the forum wouldn't allow posting them, and also wouldn't allow a text file so I had to zip.)

 

Basically:

telnet check successfully connects and waits for input.

 

nmap shows the following ports open:

 

PORT      STATE SERVICE        REASON
443/tcp   open  https          syn-ack ttl 64
554/tcp   open  rtsp           syn-ack ttl 64
1025/tcp  open  NFS-or-IIS     syn-ack ttl 64
1900/tcp  open  upnp           syn-ack ttl 64
2020/tcp  open  xinupageserver syn-ack ttl 64
8800/tcp  open  sunwebadmin    syn-ack ttl 64
20002/tcp open  commtact-http  syn-ack ttl 64
MAC Address: 90:9A:4A:61:92:14 (Tp-link Technologies)
 

 

Regards, Bill

Missed the incognito mode, will you be able to access it via the incognito mode where you don't have the cache to interfere?