Search results

Wow, a little thin skinned here today are we? Looked to me like the OP waited over 2 months for any reply, and got nothing. You have helped me in the past, Fenderman. I am sorry I offended you.

Sorry, I thought folks like you were here to help. My mistake.

I'm having the same problem, not only with Blue Iris, but also with a failure of any of the thousands of forum members stepping up to help remedy the situation. Ugh..... Dan

Logisaf IP cam, worked fine until a couple months ago with Blue Iris. Something happened to make it so that on triggers, it will record and take snapshots ok, but it never send out an alert. When I test the alert (email), it sends one out dutifully. SMS (on Sprint) never sends out a test...

Thanks, Tony. I thought I had gone through that yesterday, but when I went through it just now it worked like it should. Dan

Email notification on alerts used to work, but now I receive this on testing it: "Error with user authentication;Server says: 534-5.7.14 <Sign in - Google Accounts" The last line of this error message page gives a bad URL to learn more about this particular message: "Use IMAP to check Gmail on...

Got it ! It was that 554 port that was the problem. Thanks (again), Fenderman. Dan

Yep, at 192.168.1.100

Rebooted router and computer, still no good.

Did that. The dropdown list has Avacom H50xx, with a media/video/RSTP port of 554. No joy.

Checked and rechecked and rechecked. Don't know about the Discovery/ONVIF port, however: it is set at 8999 for some reason, but may not matter(?). The webserver address is NOT the same as the camera, but I don't understand how to change it, since it appears to be an un-editable field.

Actual message is, "Error: 8000274d (refused; check IP address and port) 0"

Cat5

I've got IP addresses and ports matching in both the general settings/Web Server and the Camera/video settings and still cannot connect to my Avacom H5080W. Find/Inspect under camera configuration returns: Opening port 81... HTTP Get / request... Redirected to 192.168.1.103:81 OK ONVIF...

I would like a catalog pm'd to me also ! Thanks

Now that I know the places to check against, it will be much easier in the future.

Got it. Thanks. It was not the port numbers that were screwed up, it was the local IP address. You are very patient. I apologize for being so dense on this stuff. I'm going to recommend you get a pay raise ! :)

Made them the same, still get HTTP 302 Redirection.

Here....

2nd attempt....

right click on them, open in new tab?

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)

Camera deleted, no camera discovered on attempted reinstall.

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.

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.

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

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...

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

Apologies, dupe post...

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...