Peacock still broken (Server not found)

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

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"

[Cats4U]

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

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.

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.

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

[Wilson.Wang]

Hi,

For the problem, please wait for the new version of this week and try it again.

We did some fix for the problem.

Wilson

[flylow+]

Hi,

For the problem, please wait for the new version of this week and try it again.

We did some fix for the problem.

Wilson

Thanks for the information!

[Stan001]

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.

People can zip them with 7zip, WinRAR or other utilities.
If SF support can't access zipped files, they should quit.
They seem to refuse to increase the upload limit for log files that contain literally 1,000's of errors, from just attempting to download one item.

Hi,

For the problem, please wait for the new version of this week and try it again.

We did some fix for the problem.

Wilson

Am patently waiting for next version and more than willing to test and try it.

[Cats4U]

Hi,

For the problem, please wait for the new version of this week and try it again.

We did some fix for the problem.

Wilson

Maybe you fixed something, but you didn't fix the problem we are all having. 5 weeks, 206 messages, plenty of logs sent in, and the problem is still not fixed in 6.1.9.6. I still cannot download anything from Peacock unless I VPN to Boston. Boston works for me, I do not claim that it should work for anyone else.

[flylow+]

Hi,

For the problem, please wait for the new version of this week and try it again.

We did some fix for the problem.

Wilson

No joy for me in 6.1.9.6. The folks at Peacock are laughing, Streamfab has struck out.

" ... server replied: Not Found, code : 203" persists.

[Stan001]

Yes, still happening in 6196.

NO VPN, NO DNS ISSUES!!

This is the link Streamfab tries to get:

https://g003-vod-us-cmaf-prd-ak-a239.cdn.peacocktv.com/pub/global/0Je/SMO/GMO_00000000490172_01/PCK_1724690663345_8fdf_01/mpeg_cenc/$RepresentationID$/seg-0_10.mp4

 https://g003-vod-us-cmaf-prd-ak-a239.cdn.peacocktv.com/pub/global/0Je/SMO/GMO_00000000490172_01/PCK_1724690663345_8fdf_01/mpeg_cenc/$RepresentationID$/seg-0_10.mp4

This is what the link SHOULD look like right from the browser viewing network activity:

https://g003-vod-us-cmaf-prd-cc.cdn.peacocktv.com/pub/global/vQJ/pth/GMO_00000000490175_01/PCK_1724962216400_f62a_01/mpeg_cenc/r0/audio/stereo/en/seg-0_10.mp4

https://g003-vod-us-cmaf-prd-cc.cdn.peacocktv.com/pub/global/vQJ/pth/GMO_00000000490175_01/PCK_1724962216400_f62a_01/mpeg_cenc/r0/audio/stereo/en/seg-0_10.mp4

Why this is happening is still unknown as well as to why only some, not all, users get this.
Compare the 2 (streamfab link) & (browser link) and that is why Not found happens.
As to why Streamfab does this, it is unknown.

There is NO /$RepresentationID$/ it should be /r0/audio/stereo/en/.

Good luck in still trying to fix it.

ADDED browser video link as the above link(s) are audio:

https://g003-vod-us-cmaf-prd-cc.cdn.peacocktv.com/pub/global/vQJ/pth/GMO_00000000490175_01/PCK_1724962216400_f62a_01/mpeg_cenc/r0/video/sdr/avc/7830k_1080_cmaf/seg_9.mp4

[KidJoe]

I just ran into the same thing trying to download Fall Guy Extended. I have other files in my DL queue, so once the queue finishes or fails on these others, I'll upload my log.

I'm USA, East Coast, no VPN. Using Comcast/Xfinity internet and their DHCP DNS servers (they own Peacock)

EDIT: attaching my log Fall Guy Extended, and a few American Ninja Warrior episodes all failed.

[Stan001]

I just ran into the same thing trying to download Fall Guy Extended. I have other files in my DL queue, so once the queue finishes or fails on these others, I'll upload my log.
I'm USA, East Coast, no VPN. Using Comcast/Xfinity internet and their DHCP DNS servers (they own Peacock)

It definitely seems to affect the East Coast USA as Cats4U has issues. I am in the East Coast, still having this.
Checked with a few others, and parts of New Jersey, New York, and Miami don't work as well.
But does work in Boston, parts of Washington DC, and Atlanta. Just to name a few, each way.

PEOPLE can CHECK (here) (here) and (here)

AND THIS IS NOW ONGOING TO 6196 FROM 6192. AS 6193 STARTED WITH:
Fix: A failure problem when downloading videos from Peacock in some cases.

[Stan001]

SOMEONE NEEDS TO STOP MESSING WITH THE FORUM.
WE HAVE NO LABELS WITH NEW POST (https://img001.prntscr.com/file/img0...kByBaIhyHw.png)
EVEN GOT A 350 MAX LIMIT.

AND SEEMS THEY REFUSE TO ADDRESS THIS ISSUE OF PEACOCK AS FROM THIS POST HERE ON, WHERE TITLED FOR THE NEW 6196.
AND MYSTERIOUS MERGED TO THIS OLD 6194 POST.

[flylow+]

It definitely seems to affect the East Coast USA as Cats4U and flylow+ have issues...

I'm on the West coast in the Great Pacific Northwest.

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.