I had this error too, and it was from incorrect port forwarding settings.

The Safari error message here is wrong. It just means there's no (HTTP/1.0 (normal WWW) responding in the other end.