cf 2023 install on windows server, web server choose

Marco, given what you've shared, it seems clear that the site you're visiting (the request you're making, showing the CFML) is running somehow WITHOUT running through the Apache configuration that is enabling the connection to CF.

My simplest guess is that the domain name or IP address of the request you're making is NOT using that 194.76.116.40 indicated in the Servername of the virtualhost in your httdp.conf, as shown in your 4th image of the PDF. You do say it's your only onw. As such, I suspect instead it's ending up being processed NOT by that virtualhost but instead by the main settings of the httd.conf. And THAT would be how it would not connect to CF.

One solution would be to copy that include of the mod_jk_vhost.conf file to OUTSIDE that virtualhost directive. That way it WOULD apply to requests that reach Apache but do NOT match that virtualhost directive. 

Another would be to do a ping of that domain name (whatever you're using), and make sure it resolves to that IP address listed in the virtual host (first line). Assuming it does not, maybe THAT is the ip address you should be putting there. Or you might want to change the virtualhost line to name that domain name instead. (There are indeed also that ServerName and related ServerAlias directives you can ALSO set within a virtualhost.)

There's also a helpful command-line tool you could run from that Windows apache bin folder, httpd -D DUMP_VHOSTS, which will show you what vhosts are indeed defined (across all included files off the httpd.conf file). Another that could help understand that is httpd -D DUMP_INCLUDES. (People finding this who work on OSs where there is no httd in the Apache bin may find instead they can use these same sort of diagnostic args with whatever is the binary in that folder that runs Apache, whether it's apachectl, apache2ctl, apache2, or even http.)

Finally, there's one more thing that's a bit confusing about your screenshots. In your 4th image, with the connector created, shows on the left, server125115.serverkeliweb.it. In my experience, what shows there is the value you enter in the first "Appserver name" field of the connector (in what's shown in your second image of the PDF). Yet you show second image that you entered there an IP address instead--indeed the same one as you selected in the "Apache Virtual Host" field.

Indeed, since you say above (previous reply) that Apache and CF are on the same machine, why didn't you just leave that "Appserver name" field at its default of "localhost"? I'm not saying that this using a different IP address in the add connector field has anything to do with your new problem of seeing CFML. I just raise it as something I noticed.

But again, the bottom line is that your request is NOT ending up in that virtualhost, and since that's what you told the CF wsconfig tool to setup. So you either need to change that virtualhost to process your request, or copy that include outside the virtualhost so that it affects  such other requests. Let us know how that goes.