Peacock still broken (Server not found)

Chameleon

I have been studying and working in the USA for eight years.

flylow+

I have been studying and working in the USA for eight years.
Chameleon

Where in the USA are you?

Possible that someone, perhaps Cats4U, that has issues in Pennsylvania can use their VPN and see if the location you are at is successful. I am in the Seattle area and have issues.

Chameleon

Where in the USA are you?

Possible that someone, perhaps Cats4U, that has issues can use their VPN and see if that location is successful. I am in the Seattle area and have issues.
flylow+

Massachusetts until September, and then I will start my new job in a different state.

flylow+

tilu3303 and I are in the Seattle area and both have issues. Stan001 is somewhere in the Northeast USA and has the issue. Cats4U in Pennsylvania has issues that are resolved when using his VPN and connecting to Boston but reports issues when connecting to other locations.

Chameleon is currently in Massachusetts and does not have the issue.

tilu3303

I see "server replied: Not Found, code : 203". I don't see 403/404 so maybe my old eyeballs are missing something. dunno

Also mentioned in the log is audio/seg-0_8.4.tmp" Note if the progress bar turns green when "Downloading Audio" in the beginning - right after "Analyzing" then the download is successful. If it does not turn green then it fails. Hit the pause icon to cancel then the play icon to retry. Might take a couple of retries or still fail after over a dozen retries.

flylow+

Thanks for this tip. I had been watching the Total Speed indicator and if it was in the single digit KB/s I knew it would never succeed.

I'm sure you're quite familiar with Cloudflare WARP acting as a local VPN. Well, I just switched it on (I only use it when I need to get unstuck from a DNS stonewall) and restarted Streamfab and on only the second try Being Erica S01E02 downloaded successfully. Clearly, this doesn't work 100 percent, but I had tried at least a dozen times without any success when not using WARP, so it may have helped.

tilu3303

I think the Cloudflare WARP experience was just a case of the luck of the draw. I was probably just due after about 15 tries.

flylow+

I think the Cloudflare WARP experience was just a case of the luck of the draw. I was probably just due after about 15 tries.
tilu3303

I just manually change the settings. Random successes no matter what I have tried. Sometimes first attempt, sometimes 2 or three tries and sometimes a dozen attempts fail. Sometimes when I try again late success on the first try but of course not always.

Germania

[quote=tilu3303;n449261]I think the Cloudflare WARP experience was just a case of the luck of the draw. I was probably just due after about 15 tries.[/quote]

I just manually change the settings
flylow+

CF Warp (info) is not the same as changing to CF DNS-Server

It also changes IP + ASN and displays CF as ISP

flylow+

CF Warp (info) is not the same as changing to CF DNS-Server
Germania

I did not say it was the same...

Germania

I did not say it was the same...
flylow+

I'm sorry, but that's how it sounded to me ...
... otherwise the picture of the CF DNS Server makes no sense at all in this context

flylow+

I'm sorry, but that's how it sounded to me ...
... otherwise the picture of the CF DNS Server makes no sense at all in this context
Germania

Was just meant to show the settings I used. So sorry you were confused.

Germania

So sorry you were confused.
flylow+

confused and logically analytical are not the same thing

however AFK

flylow+

confused and logically analytical are not the same thing
Germania

So sorry about the logically analytical issue.

tilu3303

CF Warp (info) is not the same as changing to CF DNS-Server

It also changes IP + ASN and displays CF as ISP
Germania

Sorry if my description was confusing. In an earlier post I mentioned having my normal DNS setting to Cloudflare DNS servers (as opposed to using the ISP's or Google's, etc.). I did not expect that my mention of Cloudflare WARP being normally disabled and turned on and off would imply anything about what DNS server I'm using. I didn't think to provide greater context than that.

MrKrawk

People with log files that are too large --- delete the log before trying to analyze and download. It will then make a log specific to what you are trying to do.

flylow+

People with log files that are too large --- delete the log before trying to analyze and download. It will then make a log specific to what you are trying to do.
MrGrackle

Tried that, did not work it still was too large.

My log file after failure appear to be mostly filled with code 203. Appears to be hundreds and hundreds of lines with "Not Found, code 203"

flylow+

Cats4U

Peacock seems to be working fine for me in all phases.
Chameleon

That seems to fit in with my CDN theory. You live in the Boston area. If I VPN to a Boston server, I can connect 100% of the time. Peacock has changed something at a great many CDNs that make it difficult for SF to connect with them. My local CDN appears to be one of the ones changed. The Boston area CDNs appear to have not changed, and so SF can still connect to them. The developer needs to figure out what the change was and make allowance for it so that the connection can be made to the vast majority of CDNs.

jbinkley60

That seems to fit in with my CDN theory. You live in the Boston area. If I VPN to a Boston server, I can connect 100% of the time. Peacock has changed something at a great many CDNs that make it difficult for SF to connect with them. My local CDN appears to be one of the ones changed. The Boston area CDNs appear to have not changed, and so SF can still connect to them. The developer needs to figure out what the change was and make allowance for it so that the connection can be made to the vast majority of CDNs.
Cats4U

Typically with a VPN you lock into a single proxy towards the CDN due to the VPN tunnel established between your client the the VPN server. Thus the CDN never sees the same source session changing and thus always the same session. It appears there is a session token that the browsers recognize and pass back to the CDN which is why they work without a VPN but StreamFab is somehow not honoring the session token or messing with it, which is why it is failing. I suspect the SF developers are trying to reverse engineer the session token and it may be encrypted.

This is all an educated guess on my part after having worked in this space for the past 20+ years and having seen many issues related with application session persistence.. The old days of source IP or L4 persistence are long gone :)

Jeff

Cats4U

You have your opinion and I have mine. I stand by what I wrote. Something has changed for most, but not all, Peacock CDNs. SF has not adjusted to that change yet.

jbinkley60

You have your opinion and I have mine. I stand by what I wrote. Something has changed for most, but not all, Peacock CDNs. SF has not adjusted to that change yet.
Cats4U

I don't think there is any disagreement here I was simply proposing a theory on what might be happening. StreamFab will need to adjust to the changes in order to keep working properly. We cannot expect your ISP or the Peacock CDN provider to fix the problem (depending upon which one may have made a change to cause this) , Nowadays application persistence is pushed back to the applications to manage vs. the network in the past. Usage of VPNs and similar just help with the issue but I wouldn't recommend them as a long term solution.

Jeff

« Previous Page Next Page »