[PLUG] Browser not finding localhost

Tomas Kuchta tomas.kuchta.lists at gmail.com
Thu Jan 9 20:03:05 UTC 2025


On "normal" (whatever it means) linux desktop mDNS should take care of
resolving $HOSNAME.local

That said - there are none of these guarantees in modern browsers often
using secure/encrypted external DNS as default.

Using 127.0.0.1 IP should always work, regardless of how your browser
matches names to IPs.

-T

On Thu, Jan 9, 2025, 14:36 Russell Senior <russell at personaltelco.net> wrote:

> Try:
>
>   netstat -tan | grep LISTEN
>
> That should tell you what ports on your local system are listening for
> TCP connections.
>
> If you see the ports you expect, then start to consider whether
> localhost is resolving. The usual place for that to happen is in
> /etc/hosts. On my system, I see something like this in /etc/hosts:
>
>   127.0.0.1       localhost.localdomain   localhost
>
>
> --
> Russell Senior
> russell at personaltelco.net
>
> On Thu, Jan 9, 2025 at 8:20 AM Rich Shepard <rshepard at appl-ecosys.com>
> wrote:
> >
> > Opening a tab in Brave I try to open http://localhost:1313/ and
> > http://localhost:631/ with the browser responding `localhost refused to
> > connect.
> >
> > Yet,
> > $ ps ax | grep httpd
> >   1556 ?        Ss    11:09 /usr/sbin/httpd -k start
> >   1569 ?        Sl     0:00 /usr/sbin/httpd -k start
> >   1570 ?        Sl     0:00 /usr/sbin/httpd -k start
> >   1586 ?        Sl     0:00 /usr/sbin/httpd -k start
> > 16288 pts/3    S+     0:00 grep httpd
> >
> > Where do I look for the reason neither my local web site nor CUPS admin
> > pages will load?
> >
> > TIA,
> >
> > Rich
> >
>


More information about the PLUG mailing list