[GTALUG] Problem new virtual host

[ac]

On Fri, 1 May 2020 11:33:53 -0400 (EDT)
"D. Hugh Redelmeier via talk" <talk at gtalug.org> wrote:
> I'm a bit confused.  But I'm probably not the only one.
> Note: I've never set up a virtual host so I could be way off-base.
> 
this entire thread is confusing. it was about something unclear to
start with
and now it is simply just becoming noise.

i mean could the op not configure apache properly? did the op not
register a domain name? is the op's /etc/hosts file being ignored due
to "browser" control of dns? 
 
> 
> By default, I've heard that Firefox has switched to using DNS over
> HTTPS.  If your browsers have done so, they might well be ignoring
> /etc/hosts.
> 
this is interesting... imnsho, life is all about balance.

balance between privacy and security and freedom

The world has changed. Freedom is no longer an issue and there is no
freedom.

As we move forward on this path, the number of choices, the amount of
variation, will decrease and we will have less and less freedom.

It is like being in a pot of water on a stove, if the temperature
gradually increases, it is not so bad...

but future generations are becoming truly f*ck*d.

It is not only Firefox, it is Chrome, it is Internet Explorer, it is
everything.

Here is the crux of why the firefox Internet is no longer free and
becoming worse each passing day:

https://wiki.mozilla.org/Security/DOH-resolver-policy - bottom of the
page

Conforming Resolvers:
The following providers have contractually agreed to abide by these
policy requirements (per Wthayer): Cloudflare 	Privacy policy
	https://mozilla.cloudflare-dns.com/dns-query NextDNS
Privacy policy 	https://dns.nextdns.io


> Try the links browser: that surely uses the vanila resolver
> 
> | Entering my local IP in a browser gets me to Gerbera's control
> panel.
> 
> Now we know that you're running Gerbera on your server.
> 
> I don't know how Apache picked Gerbera as the default.  But you
> probably don't care anyway.  Or maybe you should change the server's
> setup so it defaults into something innocuous.

it also tells us, on a balance of probability, that the problem is
probably not routing/port related but Apache that does not know what it
has to serve... - so either non registered domain or /etc/hosts