Thanks for the info! That confirms my theory why I suddenly can watch WE again.

I can't. It's still the same: The ad and then nothing but the spinning wheel.

Yeah donna.....I would say that most people having trouble will be those trying to watch from work and people like me with strong home security. Even if the issue cannot be resolved....this thread at least serves a purpose to explain to folks what is happening....and stop pulling out their hair.

This explains why I no longer get Africam streams at work (heavy firewall) but can get other streams. Some comfort in knowing

Short version....stream using port 1935 (Firefox 3.5)...

Long version...

Not afraid to admit I am reaching the end of my abilities on this one....and getting confused. Here's what I have. Internet Explorer behind a Comodo Firewall (strong security) gets as far as the port 433 attempt in the sequence and stops.

However....FF 3.5, even though the stream is coming in on 1935, seems to be able to reach beyond the firewall and take it. Port 1935 is not open to my machine....period. Thus my confusion. Now on a lark, I have an odd setup on my test laptop and tried that. It is running IE8 but behind an old and weak version of Sygate firewall.....it can get the stream. Sygate doesn't have the cool traffic analysis like Comodo, so I don't have a screenshot for that. I am not sure what the heck is going on now. For the most part, I can rig things to get the stream through. However, those without direct access to their firewall (work/business computers) or the knowledge to make adjustments....are still going to need that port 80 connect I would think. The only thing I know for sure is that I receive from 1935.

I have done some research on the cross-browser port 1935 issue and there are a couple other folks out there in the tech community that noticed it too. Something about the GET headers or source ports or something maybe....but they were way over my head (which isn't hard to reach).

In summary and near as I can figure....anyone behind high security is still going to have trouble because port 1935 is still carrying the stream. As I mentioned earlier....I have spoken with some people who couldn't get Wildearth a few weeks ago. Then Wildearth, for whatever reason, switched to port 80 and people started getting the stream with no adjustments to security.....it just started working for them. I'm not saying you need to follow WE's lead....just using it as an example of port assignment being the difference. And I hate to see people uninstalling and reinstalling Flash player....over and over....when that isn't the problem. I am not sure where you go at this point.

BTW....the latest Flash Player is flawed, it won't take some streams. Adopey is supposedly working on that. And the previous version to this update had about a dozen security holes. The Flash world is a mess right now and Adopey forums is loaded with angry people.

Silverlight anyone? LOL

ok, i have juggled a few things aroud on the networking. See if u can connect via port 80 now?

OK...I see why the secure port 433 now. The connect attempt sequence is 1935, 433, 80.....then finally tunnel 80. That had me wondering for awhile. And I agree most people have an open port 1935....and they likely also have a bunch of other open ports too.

Don't have time for a full check.....I will try later. But I am still getting it on port 1935 and it seems you have added HTTPS port 443, which is the internet secure connection port. Not sure why that would be in there...?

EDIT: Forgot to add.....firewall still blocking...

The reason for port 1935 is that computationally & bandwidth wise its far more effecient than tunneling. Also by far the majority of people do not have port 1935 blocked.

Having said that we recently reconfigured the server to allow connections via port 80, as a last option. We briefly tested this & it didnt work and at the time i had to move onto more pressing issues.

I have now put port 80 at the head end. Have a test and let me know

Let me illustrate what happens when you turn on the cam. In the screenshot below you see 4 highlighted connections. These are the connections your machine makes for the cam stream. The ones in green are most likely the ad servers or distribution servers and show they are being delivered on port 80 (the number after the colon is the port number). The one in red is the actual cam feed....and is showing port 1935. Just wanted to show the image so people don't think I am making this stuff up.....or been drinking too much....LOL

So why isn't everyone affected you may ask? Well....if your firewall is letting this stream through without you having to do anything, then your firewall isn't doing it's job very well. A solid firewall SHOULD block that port by default to be truly stealth. So what Africam needs to do is tunnel that stream through port 80....where everybody's browser hangs out. Or have their distributor do it is more accurate. I believe Adopey provides for HTTP tunneling to convert that stream from RTMP to RTMPT. Someone likely just needs to implement some Adopey coding on the server.