Skip to main content

Had the same problem and after passing a lot of time trying to understand what the problem was I realized theThe problem could be that the hosts file might have been corrupted from the original ASCII encoding. I cleared all spaces and put tabs in it, ran sudo killall -HUP mDNSResponder (you can do that instead of rebooting) and after, it worked. So I guess that was the problem.

Had the same problem and after passing a lot of time trying to understand what the problem was I realized the problem could be that the hosts file might have been corrupted from the original ASCII encoding. I cleared all spaces and put tabs in it, ran sudo killall -HUP mDNSResponder (you can do that instead of rebooting) and after, it worked. So I guess that was the problem.

The problem could be that the hosts file might have been corrupted from the original ASCII encoding. I cleared all spaces and put tabs in it, ran sudo killall -HUP mDNSResponder (you can do that instead of rebooting) and after, it worked.

Source Link
Francisco
  • 141
  • 1
  • 1

Had the same problem and after passing a lot of time trying to understand what the problem was I realized the problem could be that the hosts file might have been corrupted from the original ASCII encoding. I cleared all spaces and put tabs in it, ran sudo killall -HUP mDNSResponder (you can do that instead of rebooting) and after, it worked. So I guess that was the problem.