"cannot parse response" (NSURLErrorDomain:-1017)

I ran across this issue and 329 people had the same problem back in 2016 (https://discussions.apple.com/thread/7430493), although I experienced the issue today 5 years later. The question was stale, so I couldn't post a reply with my findings which is why I'm asking the same question and answering it at the same time.


All of a sudden I started getting errors on all my Apple devices when accessing our website after installing an nginx-proxy in front of an Apache2 server. Firefox on my MacBook worked fine, but Safari on the same MacBook reported an error. I'm not that knowledgeable about HTTP2 and reverse-proxies so can't really comment on the root cause, but I was suspicious of a warning about HTTP2 in the server log. When I disabled (or rather didn't enable) HTTP2 on ap2 server the problem disappeared. I hope this helps other folks experiencing this problem

MacBook

Posted on Feb 25, 2021 12:59 PM

Reply
3 replies

Feb 25, 2021 5:55 PM in response to jphilippou

If you remove the proxy server, is the problem also removed?


Checked that the certificates and host names are all correct, if this connection is using HTTPS, or if any part is redirecting from HTTP to HTTPS?


Do you have any add-on anti-malware or anti-virus apps installed, or any add-on cleaner apps, or add-on firewall apps, or add-on VPN clients? Those can insinuate themselves into networks connections. Disable and remove them per the vendors’ instructions, and try again.


Load a proxy or mirror the port and capture the HTTP traffic?

This thread has been closed by the system or the community team. You may vote for any posts you find helpful, or search the Community for additional answers.

"cannot parse response" (NSURLErrorDomain:-1017)

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple Account.