Previously I was able to connect to “localhost” but today for some
reason I get errors stating that the browser “…is unable to connect
to the server localhost”. The only thing that’s changed recently was
a few Apple software updates and a new PHP install a couple days ago.
I know I have the correct local path set; for example, to view my PHP
info the path would be http://localhost/~my_username/test.php which I
checked 2 days ago and it was fine but that no longer works.
Suggestions?
Does this problem persist across a restart? What happens if you try
the IP address for localhost (127.0.0.1)? Also, try logging in as a
different user and see if the problem follows you that way.
It sounds as though your local lookup is being misled, try issuing
the command lookupd -flushcache in a Terminal window and see if
that helps.
Walter
On Feb 19, 2008, at 10:56 AM, Todd wrote:
Previously I was able to connect to “localhost” but today for some
reason I get errors stating that the browser “…is unable to connect
to the server localhost”. The only thing that’s changed recently was
a few Apple software updates and a new PHP install a couple days ago.
I know I have the correct local path set; for example, to view my PHP
info the path would be http://localhost/~my_username/test.php which I
checked 2 days ago and it was fine but that no longer works.
Suggestions?
Thanks Walter, the ‘flushcache’ cmnd did the trick. I forgot that I also installed Subversion but whether that has anything to do with it I don’t know.
Todd
On Feb 19, 2008, at 9:59 AM, Walter Lee Davis wrote:
Does this problem persist across a restart? What happens if you try
the IP address for localhost (127.0.0.1)? Also, try logging in as a
different user and see if the problem follows you that way.
It sounds as though your local lookup is being misled, try issuing
the command lookupd -flushcache in a Terminal window and see if
I have been trying to offer help to someone who has internet connection (skype and email) – but no browsing via Safari or IEMac.
I wondered if it was something to do with DNS and suggested using OpenDNS but this didn’t help.
Nor did a new user account.
Is this flushcache connmmand relevant to my friend – and is there anything more to it than pasting the command as given between the quotes and then hitting return in Terminal?
all the best
Brian
Todd said recently:
Thanks Walter, the ‘flushcache’ cmnd did the trick. I forgot that I also installed Subversion but whether that has anything to do with it I don’t know.
Todd
On Feb 19, 2008, at 9:59 AM, Walter Lee Davis wrote:
Does this problem persist across a restart? What happens if you try
the IP address for localhost (127.0.0.1)? Also, try logging in as a
different user and see if the problem follows you that way.
It sounds as though your local lookup is being misled, try issuing
the command lookupd -flushcache in a Terminal window and see if
If your friend has never been able to browse the web, then the
problem may be different. But if they want to try it, it’s harmless
and yes, that’s all you do.
If your friend is unable to browse a web site by name, perhaps try
getting one by its IP address. Google (in the US) is this:
If that works, then you can rule out one entire line of discovery –
that somehow Port 80 is being blocked.
If it doesn’t, then it means that no amount of DNS wrangling will be
at the heart of the problem, because you’ve cut DNS out of the equation.
Walter
On Feb 19, 2008, at 2:35 PM, Brian Steere wrote:
I have been trying to offer help to someone who has internet
connection (skype and email) – but no browsing via Safari or IEMac.
I wondered if it was something to do with DNS and suggested using
OpenDNS but this didn’t help.
Nor did a new user account.
Is this flushcache connmmand relevant to my friend – and is there
anything more to it than pasting the command as given between the
quotes and then hitting return in Terminal?
all the best
Brian
Todd said recently:
Thanks Walter, the ‘flushcache’ cmnd did the trick. I forgot that
I also installed Subversion but whether that has anything to do
with it I don’t know.
Todd
On Feb 19, 2008, at 9:59 AM, Walter Lee Davis wrote:
Does this problem persist across a restart? What happens if you try
the IP address for localhost (127.0.0.1)? Also, try logging in as a
different user and see if the problem follows you that way.
It sounds as though your local lookup is being misled, try issuing
the command lookupd -flushcache in a Terminal window and see if