HTTP 302 redirection problem

[DanLins]

For the past several days I cannot connect to my ipcam for some reason, and this is the message BI displays. No changes to router or switch, Windows 10, Lenovo Desktop, Avacom H5080D cam, was working fine until last Tuesday, now, nothing.

Has anyone seen this before or have any hints on what may be causing this?

Thanks,

Dan

 

[DanLins]

I can see it fine in Chrome, but not the BI software, the original Avacom software.

 

[fenderman]

I can see it fine in Chrome, but not the BI software, the original Avacom software.

check the ip address/password/ports etc..

 

[DanLins]

Inspecting at 192.168.1.106, returns:
Opening port 80...
HTTP Get / request...
Redirected to 192.168.1.106:80
OK
ONVIF GetSystemDateAndTime
HTTP 12152
Opening port 8081...
ONVIF GetSystemDateAndTime
HTTP 12029
Checking for common cameras...
Foscam FI86xx/98xx compatible?
Foscam FI89xx compatible?
Foscam FI9821 V2 compatible?
Foscam FI9821 media port compatible?
RTSP port open?
No automatic configuration made
Done

Ugh.... Weird, since I can still log in and see it with Chrome and the original crude browser interface Avacom included with the camera.

Dan

 

[fenderman]

Inspecting at 192.168.1.106, returns:
Opening port 80...
HTTP Get / request...
Redirected to 192.168.1.106:80
OK
ONVIF GetSystemDateAndTime
HTTP 12152
Opening port 8081...
ONVIF GetSystemDateAndTime
HTTP 12029
Checking for common cameras...
Foscam FI86xx/98xx compatible?
Foscam FI89xx compatible?
Foscam FI9821 V2 compatible?
Foscam FI9821 media port compatible?
RTSP port open?
No automatic configuration made
Done

Ugh.... Weird, since I can still log in and see it with Chrome and the original crude browser interface Avacom included with the camera.

Dan

find inspect wont do any good if your setup is wrong...delete the camera from BI and start again..make sure everything is entered correctly.

 

[DanLins]

Deleted cam, reinstalled, same problem. WAN address is, which is where it bombs out every time I use the remote access Wizard.

 

[fenderman]

Deleted cam, reinstalled, same problem. WAN address is, which is where it bombs out every time I use the remote access Wizard.

What does your wan address have to do with it?..I deleted it for your security..

 

[DanLins]

Thanks for your help. All I know is that is where the remote access blows up. I can ping that address, but BI does not like it at all, apparently.

 

[fenderman]

Thanks for your help. All I know is that is where the remote access blows up. I can ping that address, but BI does not like it at all, apparently.

You are not being clear...Is the camera local to blue iris? In the original post there is no mention of the camera being in a remote location...

 

[DanLins]

Sorry, not remote. Direct cat5, 25 feet away from router. The fact that I can see it in Chrome through the original Avacom software tells me the connection itself is ok.

 

[DanLins]

Camera deleted, no camera discovered on attempted reinstall.

 

[fenderman]

Sorry, not remote. Direct cat5, 25 feet away from router. The fact that I can see it in Chrome through the original Avacom software tells me the connection itself is ok.

So why are you bringing up remote access and wan IP?
You have something wrong in your settings..Post video settings

 

[DanLins]

Video settings? hmm.... http 302 error, is that not a network error?

Anyway, let me know what else you'd like to see.

(images from shared dropbox folder)

 

[fenderman]

Video settings? hmm.... http 302 error, is that not a network error?

Anyway, let me know what else you'd like to see.

(images from shared dropbox folder)

None of your images are viewable
...

 

[DanLins]

right click on them, open in new tab?

 

[fenderman]

right click on them, open in new tab?

that wont work..you have incorrectly posted them..

 

[DanLins]

2nd attempt....

 

[fenderman]

2nd attempt....

post the video>>configure tab!!
Also there is no need to redact the LOCAL ip.

 

[DanLins]

Here....

 

[fenderman]

Here....

likely because your rtsp/video port is NOT 81 like the http port...