On Mon, 2023-04-24 at 02:36 +0930, Tim via users wrote:
> If you browse to
http://bree.org.uk/ and https://bree.org.uk/
> do you get the same results?
>
Internally, yes.
> If I try web browsing your site, I get the same "books" page to
> either
> address. There is a HTTPS connection, but it complains it's not
> secure. There's no obvious indication about who issued the
> certificate.
>
There is no certificate.
> Likewise, do you get the same results with browsing for a specific
> serveable file?
>
Yes
> Likewise internally and externally? (Viewing one of your pages
> through
> a HTML validator is one way to see what the outside world sees, if
> you
> don't have some external proxy you can use, or a VPN.)
>
Internally and externally show the same content.
> I'm assuming that part of the problem is *external* access to port
> 80,
> does your ISP put something in the way of the port?
>
Not that I know of. Browsing to port 80 works as it should.
> Do you have some *other* certificate already there that's confusing
> things?
>
I currently have no certs.
The reason I suspect an Apache problem is as follows: when I configured
the VirtualHost, it was via an included file:
# pwd
/etc/httpd/conf.d
[root@Bree conf.d]# cat bree.conf
<VirtualHost *:80>
ServerName bree.org.uk
ServerAdmin pocallaghan(a)gmail.com
DocumentRoot /var/www/bree.org.uk/html
ErrorLog /var/www/bree.org.uk/error.log
CustomLog /var/www/bree.org.uk/log/access.log combined
</VirtualHost>
# tail -2 ../conf/httpd.conf
# Load config files in the "/etc/httpd/conf.d" directory, if any.
IncludeOptional conf.d/*.conf
Now when I start Apache I get:
# apachectl restart
Job for httpd.service failed because the control process exited with error code.
See "systemctl status httpd.service" and "journalctl -xeu
httpd.service" for details.
The only warning in the journal is:
Failed to start httpd.service - The Apache HTTP Server.
IOW Apache simply fails to start when I try to use the VirtualHost
directive, but provides no useful information. Furthermore:
# httpd -t -D DUMP_HOSTS
Syntax OK
#
So Apache itself says there is no syntax error in the file(s).
So why do I say that I can browse to port 80? Because when I *don't*
include that bree.conf file, everything starts up and runs. Therefore
the problem logically is in that file, but despite careful scanning of
the Apache docs I can't see what it is. Note that the various files
referenced in bree.conf all exist and are world-readable:
# ls -l /var/www/bree.org.uk/html
total 4
-rwxr-xr-x. 1 apache apache 159 Apr 16 22:24 index.html
[root@Bree conf.d]# ls -l /var/www/bree.org.uk/error.log
-rw-r--r--. 1 root root 0 Apr 21 22:28 /var/www/bree.org.uk/error.log
[root@Bree conf.d]# ls -l /var/www/bree.org.uk/log/access.log
ls: cannot access '/var/www/bree.org.uk/log/access.log': No such file or
directory
[root@Bree conf.d]# ls -l /var/www/bree.org.uk/log
total 0
Is there anything useful in the server's error.log? Startup errors
should be there.