HTTP stopped working

Questions? Suggestions? Need help? Talk about anything related to Yawcam...
Post Reply
weathernut
Posts: 6
Joined: Tue May 15, 2012 10:18 pm

HTTP stopped working

Post by weathernut »

My cable modem needed to be replaced the other day and since the new one got connected I have not been able to get the "am I online" feature to stop giving me error messages. I have upnp enabled on my router, yawcam has recognized my new allocated static ip address, http is turned on in Yawcam, and my firewall is turned off during the online test. Am I missing something here? My webam address is http://174.1.17.235:8888 and is up and running 8:00am-8:00pm PDT.
PS-my http function was working fine before the modem switch.

6/6 20:19] Yawcam started
[6/6 20:19] Settings loaded
[6/6 20:19] Language: English
[6/6 20:19] Thank you!
[6/6 20:23] Settings saved
[6/6 20:23] Ftp-output started
[6/6 20:23] Http-output started
[6/6 20:23] UPNP: Found device NETGEAR, Inc. NETGEAR R6200v2 802.11ac Wireless Router R6200v2
[6/6 20:23] UPNP: Port 8888/TCP mapped to 192.168.1.3
z3r0c00l12
Moderator
Posts: 1210
Joined: Wed Jan 14, 2009 3:50 am

Re: HTTP stopped working

Post by z3r0c00l12 »

Sounds like UPNP is not working properly on your new router. My suggestion since I never believed in UPNP is to access your router and set-up your port forwarding.

In your case, you'll want to forward port 8888 to the IP 192.168.1.3.

When Yawcam is running, you can check with netstat to see if the port is listening.

You mentioned that you set a static IP address, you could also double-check this.

FYI, I checked the link you posted and couldn't connect at 5:45PM PDT.
weathernut
Posts: 6
Joined: Tue May 15, 2012 10:18 pm

Re: HTTP stopped working

Post by weathernut »

z3r0c00l12 wrote:Sounds like UPNP is not working properly on your new router. My suggestion since I never believed in UPNP is to access your router and set-up your port forwarding.

In your case, you'll want to forward port 8888 to the IP 192.168.1.3. Tried this and made no difference.

When Yawcam is running, you can check with netstat to see if the port is listening.Please see below

You mentioned that you set a static IP address, you could also double-check this.Sorry, it's dynamic

FYI, I checked the link you posted and couldn't connect at 5:45PM PDT.
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.

C:\Users\Rob>netstat -a

Active Connections

Proto Local Address Foreign Address State
TCP 0.0.0.0:135 Rob-Laptop:0 LISTENING
TCP 0.0.0.0:445 Rob-Laptop:0 LISTENING
TCP 0.0.0.0:554 Rob-Laptop:0 LISTENING
TCP 0.0.0.0:2869 Rob-Laptop:0 LISTENING
TCP 0.0.0.0:5357 Rob-Laptop:0 LISTENING
TCP 0.0.0.0:6646 Rob-Laptop:0 LISTENING
TCP 0.0.0.0:8888 Rob-Laptop:0 LISTENING
TCP 0.0.0.0:10243 Rob-Laptop:0 LISTENING
TCP 0.0.0.0:49152 Rob-Laptop:0 LISTENING
TCP 0.0.0.0:49153 Rob-Laptop:0 LISTENING
TCP 0.0.0.0:49154 Rob-Laptop:0 LISTENING
TCP 0.0.0.0:49156 Rob-Laptop:0 LISTENING
TCP 0.0.0.0:49157 Rob-Laptop:0 LISTENING
TCP 192.168.1.3:139 Rob-Laptop:0 LISTENING
TCP 192.168.1.3:2869 DELL-DESKTOP:54037 TIME_WAIT
TCP 192.168.1.3:2869 DELL-DESKTOP:54043 TIME_WAIT
TCP 192.168.1.3:2869 DELL-DESKTOP:54046 TIME_WAIT
TCP 192.168.1.3:2869 DELL-DESKTOP:54049 TIME_WAIT
TCP 192.168.1.3:2869 DELL-DESKTOP:54057 TIME_WAIT
TCP 192.168.1.3:2869 DELL-DESKTOP:54061 TIME_WAIT
TCP 192.168.1.3:2869 DELL-DESKTOP:54068 TIME_WAIT
TCP 192.168.1.3:2869 DELL-DESKTOP:54074 TIME_WAIT
TCP 192.168.1.3:2869 DELL-DESKTOP:54078 TIME_WAIT
TCP 192.168.1.3:2869 DELL-DESKTOP:54084 TIME_WAIT
TCP 192.168.1.3:2869 DELL-DESKTOP:54089 TIME_WAIT
TCP 192.168.1.3:2869 DELL-DESKTOP:54095 TIME_WAIT
TCP 192.168.1.3:2869 DELL-DESKTOP:54099 TIME_WAIT
TCP 192.168.1.3:50513 ftp:ftp TIME_WAIT
TCP 192.168.1.3:50515 ftp:8245 TIME_WAIT
TCP 192.168.1.3:50516 ftp:7021 TIME_WAIT
TCP 192.168.1.3:50517 ftp:10202 TIME_WAIT
TCP 192.168.1.3:50518 ftp:13920 TIME_WAIT
TCP 192.168.1.3:50519 ftp:11655 TIME_WAIT
TCP 192.168.1.3:50520 ftp:13947 TIME_WAIT
TCP 192.168.1.3:50521 ftp:5025 TIME_WAIT
TCP 192.168.1.3:50522 ftp:5252 TIME_WAIT
TCP 192.168.1.3:50523 ftp:6133 TIME_WAIT
TCP 192.168.1.3:50524 ftp:7409 TIME_WAIT
TCP 192.168.1.3:50525 ftp:11888 TIME_WAIT
TCP 192.168.1.3:50526 ftp:13078 TIME_WAIT
TCP 192.168.1.3:50527 ftp:6719 TIME_WAIT
TCP 192.168.1.3:50528 ftp:4356 TIME_WAIT
TCP 192.168.1.3:50529 ftp:9601 TIME_WAIT
TCP 192.168.1.3:50530 ftp:9370 TIME_WAIT
TCP 192.168.1.3:50531 ftp:10708 TIME_WAIT
TCP 192.168.1.3:50532 ftp:5785 TIME_WAIT
TCP 192.168.1.3:50533 ftp:7438 TIME_WAIT
TCP 192.168.1.3:50534 ftp:12854 TIME_WAIT
TCP 192.168.1.3:50535 ftp:7172 TIME_WAIT
TCP 192.168.1.3:50536 ftp:4838 TIME_WAIT
TCP 192.168.1.3:50537 ftp:11348 TIME_WAIT
TCP 192.168.1.3:50538 ftp:5471 TIME_WAIT
TCP 192.168.1.3:50539 ftp:5077 TIME_WAIT
TCP 192.168.1.3:50540 ftp:13933 TIME_WAIT
TCP 192.168.1.3:50541 ftp:9069 TIME_WAIT
TCP 192.168.1.3:50542 ftp:4937 TIME_WAIT
TCP 192.168.1.3:50543 ftp:4396 TIME_WAIT
TCP 192.168.1.3:50544 ftp:4202 TIME_WAIT
TCP 192.168.1.3:50545 ftp:12422 TIME_WAIT
TCP 192.168.1.3:50546 ftp:12528 TIME_WAIT
TCP 192.168.1.3:50547 ftp:7984 TIME_WAIT
TCP 192.168.1.3:50548 ftp:4975 TIME_WAIT
TCP 192.168.1.3:50549 ftp:6133 TIME_WAIT
TCP [::]:135 Rob-Laptop:0 LISTENING
TCP [::]:445 Rob-Laptop:0 LISTENING
TCP [::]:554 Rob-Laptop:0 LISTENING
TCP [::]:2869 Rob-Laptop:0 LISTENING
TCP [::]:3587 Rob-Laptop:0 LISTENING
TCP [::]:5357 Rob-Laptop:0 LISTENING
TCP [::]:10243 Rob-Laptop:0 LISTENING
TCP [::]:49152 Rob-Laptop:0 LISTENING
TCP [::]:49153 Rob-Laptop:0 LISTENING
TCP [::]:49154 Rob-Laptop:0 LISTENING
TCP [::]:49156 Rob-Laptop:0 LISTENING
TCP [::]:49157 Rob-Laptop:0 LISTENING
TCP [::1]:49155 Rob-Laptop:0 LISTENING
weathernut
Posts: 6
Joined: Tue May 15, 2012 10:18 pm

Re: HTTP stopped working

Post by weathernut »

Problem solved! Turns out my new cisco modem (which, unlike my previous modem has a built-in router) was in an ip conflict with my existing netgear stand-alone router. I had to get my ISP to "bridge" the cisco cable modem to stop the conflict.
Post Reply