Cannot access localhost through 127.0.1.1 or 127.0.0.1

pealo86, it looks as though there are a few leading number-signs missing from the comments of your /etc/hosts file.

If you open a Terminal window and run the command *openssl dgst -sha1 -c /etc/hosts*, is the output from that command

SHA1(/etc/hosts)= 51:6f:ee:54:30:1d:8f:ea:57:72:39:60:2a:cf:dd:3b:d0:62:e8:88

If so, then your /etc/hosts file is fine, and the copy of it in your post just lost a few leading number-signs between copying and pasting.

If the output is different, though, then you’ll want to edit it to make sure that there are leading number-signs on the second, fourth, and fifth lines (as were there originally).

I hadn’t heard of localhost ever being equated to 127.0.1.1; its traditional value is 127.0.0.1, as your /etc/hosts file shows.

From within the Terminal window, try the *ping -c 3 localhost* command; are the first lines of output something like

PING localhost (127.0.0.1): 56 data bytes
64 bytes from 127.0.0.1: icmp_seq=0 ttl=64 time=0.045 ms
64 bytes from 127.0.0.1: icmp_seq=1 ttl=64 time=0.050 ms
64 bytes from 127.0.0.1: icmp_seq=2 ttl=64 time=0.069 ms
…

(The times at the end of each line will vary.) If so, then localhost is perfectly accessible at 127.0.0.1.

pealo86, my suggestion for what to do next remains the same: edit /etc/hosts +to make sure that there are leading number-signs on the second, fourth, and fifth lines (as were there originally).+

Because the /etc/hosts file is owned by the root user, you’ll need to use an admin account to make changes to the file. (If you’re comfortably familiar with Unix commands, running *sudo vim /etc/hosts* from a non-admin account would work just as well as editing from an admin account.)

Once you’ve saved the edited /etc/hosts file, retry the ping command to make sure that localhost is accessible.

When you post code or anything you want the forum formatting to keep its fingers off of, enclose that section of text in a matching pair of

tags, as in:

...
... /etc/hosts here ...
...
{code}

pealo86, I’ve had a look at the HTML that your initial post generated, and I think that the posting software here was responsible for changing the number-signs on those lines to a numbered list.

So that we can tell the exact contents of your /etc/hosts file, please do the following:

• open a Terminal window
• run *cd /tmp*
• run *uuencode -o hosts.uu /etc/hosts pealo86_hosts*

This will encode a copy of your /etc/hosts file into a file named hosts.uu in your /tmp directory. When the encoded file is decoded, the file that will be created will be named pealo86_hosts.

• run *cat hosts.uu*

This will display the contents of the hosts.uu file.

• In your reply to this post, type in two consecutive “

” lines (without the quotation marks), as Bob suggested; copy the output from the cat command (from the begin line to the end line, inclusive); and paste it between those two lines.
The encoding is necessary to preserve the spaces and tabs through the posting software here. The “

” lines will be needed to make sure that the encoded content isn’t altered by the posting software here.

pealo86, the problem is on the 127.0.0.1 line:

127.0.0.1 www.localhost.com

That line was originally, and still should be

127.0.0.1 localhost

(The original /etc/hosts file has a tab character separating the IP address from the name, but the tab will probably be turned to spaces in the post.)

Try correcting this line, then retry the ping command that was given in a previous post.