Okay, thanks for the comments.
So, yes, I always have SELinux on, but I did temporarily put it into permissive mode, but it made no difference, so presumably it's not an SELinux problem.
Yeah, I can ping it on the host, etc. (don't forget, I have no problem with this domain just using port 80, it's only 443 I have issues with)
Code: Select all
$ host xxx.com
xxx.com has address 51.???.???.100
Note that the Azure config uses the internal address, since it's not the primary IP, but it resolves to the external public IP.
So, checking the config which KernelOops sent, I saw that I did not have the "SSLEngine on" directive in my config, so I added it. However, httpd wouldn't even start when I did that, so I took it out again.
Also, while it wasn't what I would prefer as a solution, I figured I could try wild-carding the 443 VirtualHost, per below:
instead of
... but httpd also failed to start after doing that too. That seems like it may be a relevant piece of info' for someone who knows what they're doing.
Log entries ... Not sure these display very much useful info', but I'll put them here anyway.
Code: Select all
$ sudo journalctl -xe
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit httpd.service has begun starting up.
Mar 25 22:37:37 dgbvm.internal.cloudapp.net systemd[1]: httpd.service: main process exited, code=exited, status=1/FAILURE
Mar 25 22:37:37 dgbvm.internal.cloudapp.net kill[40014]: kill: cannot find process ""
Mar 25 22:37:37 dgbvm.internal.cloudapp.net systemd[1]: httpd.service: control process exited, code=exited status=1
Mar 25 22:37:37 dgbvm.internal.cloudapp.net systemd[1]: Failed to start The Apache HTTP Server.
-- Subject: Unit httpd.service has failed
$ sudo systemctl status httpd.service
? httpd.service - The Apache HTTP Server
Loaded: loaded (/usr/lib/systemd/system/httpd.service; enabled; vendor preset: disabled)
Active: active (running) since Wed 2020-03-25 22:38:00 UTC; 3min 35s ago
Docs: man:httpd(8)
man:apachectl(8)
Process: 40014 ExecStop=/bin/kill -WINCH ${MAINPID} (code=exited, status=1/FAILURE)
So, from what I can see thus far, I really can't do a single thing with SSL on the machine with this Apache config. I really don't know what I'm missing, but please feel free to throw even the most basic info at me, since I've never done a thing with SSL before.