Stream randomly stopped working

[clamchoda]

Anyone else have this problem?

Used port checker to verify that port 8081 is open.

The stream check in "Am I online?" returns "...OK"

Can view stream from 127.0.0.1:8081 but randomly no longer view by publicip:8081

I have checked that the IP is correct in the connection settings, as well as matching up with http://www.whatsmyip.org/, and I can ping the IP with no problems.


Things I've tried:
- Have tried re-installing both Yawcam and Javascript
- Have tried an older version of javascript
- Have tried unselecting UPNP and restarting Yawcam.
- I have , and always had my anti-virus disabled
- I have, and always had my firewall disabled

[z3r0c00l12]

What happens when you try to connect with your public IP? Do you get the loading image?

[clamchoda]

No, it hangs for ever then says safari (or whatever browser) can not open the page because the server stopped responding.

[z3r0c00l12]

When you are trying from your public IP address, are you within your network or somewhere else?

[clamchoda]

Somewhere else. Ive tried from cell phone (3g /lte not wifi), work, girlfriends, and brothers.

It worked fine for 3 or 4 months I'm not sure whats going on.

[z3r0c00l12]

Has the IP address on your computer changed? Perhaps your port really is open, and forwarding, but forwarding to the wrong IP address.

[clamchoda]

Has not changed.

[z3r0c00l12]

Did your Java update recently?

[clamchoda]

Yes i believe it was on auto update but i could not figure out how to tell if there was an update. I did revert back to an earlier version and the problem persisted.

[z3r0c00l12]

Can you run the command below?

Code: Select all

netstat -anop tcp | find /i "LISTENING"

Then try connecting from another computer or using a proxy and run the command below:

Code: Select all

netstat -anop tcp | find ":8081"

Post the output to both commands here or at least the relevant portions.

[clamchoda]

Here is the output from first command

C:\Users\Chris>netstat -anop tcp | find /i "LISTENING"
TCP 0.0.0.0:135 0.0.0.0:0 LISTENING 944
TCP 0.0.0.0:443 0.0.0.0:0 LISTENING 3640
TCP 0.0.0.0:445 0.0.0.0:0 LISTENING 4
TCP 0.0.0.0:902 0.0.0.0:0 LISTENING 3144
TCP 0.0.0.0:912 0.0.0.0:0 LISTENING 3144
TCP 0.0.0.0:1433 0.0.0.0:0 LISTENING 2112
TCP 0.0.0.0:5357 0.0.0.0:0 LISTENING 4
TCP 0.0.0.0:8081 0.0.0.0:0 LISTENING 5180
TCP 0.0.0.0:8888 0.0.0.0:0 LISTENING 5180
TCP 0.0.0.0:26143 0.0.0.0:0 LISTENING 4
TCP 0.0.0.0:49152 0.0.0.0:0 LISTENING 644
TCP 0.0.0.0:49153 0.0.0.0:0 LISTENING 412
TCP 0.0.0.0:49154 0.0.0.0:0 LISTENING 1096
TCP 0.0.0.0:49158 0.0.0.0:0 LISTENING 692
TCP 0.0.0.0:49160 0.0.0.0:0 LISTENING 4344
TCP 0.0.0.0:49166 0.0.0.0:0 LISTENING 720
TCP 0.0.0.0:60336 0.0.0.0:0 LISTENING 2112
TCP 127.0.0.1:895 0.0.0.0:0 LISTENING 2000
TCP 127.0.0.1:896 0.0.0.0:0 LISTENING 2000
TCP 127.0.0.1:8307 0.0.0.0:0 LISTENING 3640
TCP 127.0.0.1:12001 0.0.0.0:0 LISTENING 3640
TCP 127.0.0.1:20371 0.0.0.0:0 LISTENING 2000
TCP 192.168.0.2:139 0.0.0.0:0 LISTENING 4
TCP 192.168.23.1:139 0.0.0.0:0 LISTENING 4
TCP 192.168.80.1:139 0.0.0.0:0 LISTENING 4

second command

TCP 172.20.10.6:63204 My.Public.IP:8081 ESTABLISHED 15704

[z3r0c00l12]

the second command didn't return anything relevant, can you try running it again while you are trying to view the stream?

[clamchoda]

the second command didn't return anything relevant, can you try running it again while you are trying to view the stream?

I tried again from work.

I wait for the browser to say "Waiting for (my public IP)" before I ran the command.

I ran it dozens of times, it returns the same results.



C:\Users\trim>netstat -anop tcp | find ":8081"
TCP 10.10.2.82:28674 my.public.ip:8081 ESTABLISHED 33924

[z3r0c00l12]

Oh, I see.

I should've mentioned that. The command has to be run on the computer running Yawcam. The command would let us know if the connection even makes it to your computer. If it does, it would at least rule out a firewall or port forwarding issue. If you want, we can schedule a teamviewer session and I can try to connect to your stream while you run the command. This way we could troubleshoot the issue properly.

[clamchoda]

That would be great. If we camt gigure it out Fter i run the command i would appriciate that!