The mod_ssl distribution provided configuration in ~/conf.d/mod_ssl.conf defines a (default) ssl virtual host named _default_. If you have only one domain which matches the server name, the ssl _default_ host is detected first and becomes the default ssl configuration and takes precedence over the user-created configuration.

The result is:

1. If you use a letsencrypt certbot generated certificate and configure it in your virtual host config file, a https request results in an invalid certificate complain, because the mod_ssl provided self-signed certrificates takes precedence.

2. If you use a Document Root different from /var/www/html, a http request fetches the correct content, a https request is uses /var/www/html instead.

Same is true, if you use only one domain different from the server's domain name. And if you server several domains, you get this issue for the domain found first in the list of configuration files. 

The only solution found so far is to comment out the _default_ vhost in mod_ssl.conf

For more detailed information see section Troubleshooting in:
https://docs.fedoraproject.org/en-US/fedora-server/services/httpd-basic-setup/

One complain about the issue:
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org/thread/3VFLS4VXKP6W5WDX2J2OV2WQVCIEZONH/#3VFLS4VXKP6W5WDX2J2OV2WQVCIEZONH



Reproducible: Always

Steps to Reproduce:
1. Install httpd and mod_ssl on Fedora (Server) 38 or 39
2. Create a vhost of the same FQN name as the server, specify a https and a http variant.
3. Use letsencrypt to generate a certificate and configure it in the vhost https section
Actual Results:  
You get a certificate complain, because the distribtuion provided self-signed certificate is used instead of the configured letsencrypt certificate.

A httpd  -S  lists 2 default 443 servers, the ssl_mod one and the user configured one 

Expected Results:  
use of the custom configured letsencrypt certificate

I think, instead of just fixing the ssl_mod configuration bug, it is better to restructure the configuration and package. The current configuration concept seems to have its origin at the time of Apache 2.0 or so. The meaning of _default_ as a dedicated default server was dropped with 2.4. It is now just an alias for *. The differentiation of main servers and various kinds of virtual host was dropped. Today it is just a virtual or named host and every domain is to be configured as virtual host. 

And it is time to include mod_ssl as part of the default httpd package. More or less everything is now requiring https. That opens the possibility to introduces domains as the first level directory structure in /var/www with "adefault" as preconfigured default domain and to provide a really working default vhost configuration which includes http (redirect) and https.

If it is helpful (and welcome/useful), I could provide a PR for the corresponding configuration files.  I currently chair the Fedora Server Working Group and specifically care about web service matters (among others)