I'm not thinking of either of those; but then that question was specifically why I would need to load the server's hosts file with information it can get from DNS.
Apparently I misunderstood. I thought you told me to replace the VirtualHost with the wildcard followed by the port, which I did to uncomfortable results. Did you want me to instead use:
<VirtualHost 127.0.0.1:80>
for all of the files (changing port in SSH, of course)?
Honest to god, I am completely confused. Are you suggesting apache doesn't know and cannot get the IP address of the server on which it resides? And even if that were the case, or the machine had multiple IP addresses attached, wouldn't:
VirtualHost *:80
...tell Apache it doesn't frelling matter what the IP address is the request comes in on?
Done, without changing anything else so that config files still read:
<VirtualHost www.bobedwardsradio.com:80>
<VirtualHost www.bobedwardsradio.com:443>
<VirtualHost samples.lofcom.com:80>
<VirtualHost samples.lofcom.com:443>
...and restart now warns:
Stopping httpd: [ OK ]
Starting httpd: [Thu Oct 05 00:51:15 2017] [warn] VirtualHost samples.lofcom.com:80 overlaps with VirtualHost www.bobedwardsradio.com:80, the first has precedence, perhaps you need a NameVirtualHost directive
[ OK ]
...and neither of them are using certs other than the self-signed for default, vps.lofcom.com. The default is:
000_default.conf:
<VirtualHost 199.175.53.13:80>
ServerName vps.lofcom.com
DocumentRoot "/home/admin/bes.lofcom.com/web"
<Directory "/home/admin/bes.lofcom.com/web">
allow from all
Options +Indexes
</Directory>
</VirtualHost>
I should never see that unless something is very wrong. Which it is.
I am reverting hosts so that at least www.bobedwardsradio.com works overnight; I will get back to work on this in the morning. If I have to, I will delete all certificates, remove all VirtualHosts from the machine, and start over completely clean - getting to the point where I'm willing to remove apache itself, kill config files, and reinstall. But I need a pointer to the standard VHost config file, since what works fine for me in http across a number of servers when placed directly in the httpd.conf file, using server.name:80 instead of something_IP_related:80, clearly does not work at all when httpd is involved.