Error: "cannot parse response" (NSURLErrorDomain:-1017)

I was able to get Safari to load Netflix by changing Network > Advanced > DNS to 8.8.8.8 and 8.8.4.4 (Google) as the first choices rather than 1.1.1.1 and 1.0.0.1 (Cloudflare). Add Google DNS servers, reorder them above Cloudflare and hit OK and Apply. Maybe Chrome uses Google DNS by default. Seems to be a Cloudflare, Netfilx issue. I will be changing this back at some point. Still very puzzled as to why this is happening.

Hi woke up to that message too hey. I am not sure what’s really happening because even on my iPhone (Safari) it’s giving the same error. However l tried the app is working and google chrome is working so l think it’s Safari that has a problem l hope someone can assist with a working solution

Hey,

I have the same problem, as @bm14_1993 said it works on Chrome & Netflix Apps (Also works on iPhone App). It also worked with Sonoma yesterday. Their Help-Center site says that they have some technical problems right now.

I guess that the problem is on Netflix & Safari and I hope that they will fix it soon.

Go to “System preferences” and click on “Network.”

Select the network interface you are using and click “Advanced.” Lower rt corner.

Open the “DNS” tab and click the “+” button at the bottom, then add the Google DNS server addresses:

8.8.8.8 hit + again and enter 8.8.4.4

Drag, one at a time, the top two DNS server addresses below the two you've just added.

Hit OK

Hit Apply

That should do it. There are pictures to clarify this but the instructions given there are for changing to NordVPN at the following link

How to change your DNS servers on macOS

Disregard their instructions and follow those given here.

Note I am NOT recommending NordVPN at all. I do NOT use them.

I am having the same problem.

Please take me step by step how l do that l really need to try that out

+1

Hi there thanks but it did not work for me despite following to the dot it keeps saying the same error hey thank you though

Mine is back up and running guys maybe try now thanks for all your help

Has anyone found out the reason for this, or is this just another permanent Safari bug that will never be fixed?

I've had this 5 times in two months already.

System preferences are found where??