Hello @jota ,
give me a premise: the fact that http2 is working does not mean that it is contemplated to accept equally that the apache log file shows errors, perhaps unrelated to the http2 theme and consequence of some other wrong configuration but as long as we do not know it we cannot even say with certainty that is not a consequence of the http2.
What then, about the configuration that you have reported to me and for which I thank you, I want to say one thing: following those instructions to the letter, the apache file presents a different type of error and that is
(13) Permission denied: AH00072: make_sock: could not bind to address [::]: 80
(13) Permission denied: AH00072: make_sock: could not bind to address 0.0.0.0:80
It was my care, after some time wasted in experiments, to understand that by replacing, from the ones and only the bitnami.conf and bitnami-ssl.conf files (and therefore not also from the files contained in the vhosts folder) the code " <VirtualHost 127.0.0.1:80 default: 80> " with only " <VirtualHost default: 80> " (I repeat: in the files drupal-vhost.conf and drupal-https-vhost.conf and the back versions nothing is touched, ok 127.0.0.1:80): the problem no longer occurs.
Only here, beyond the fact that http2 works the same (with or without 127.0.0.1:80, just follow the Bitnami guide correctly and that is add "Protocols h2 h2c http / 1.1 H2Direct on" to both bitnami.conf file + bitnami-ssl.conf + all files contained in the vhosts folder), the apache log file if it no longer presents the port error, still presents this other type of error which is
AH01630: client denied by server configuration: /opt/bitnami/drupal/.env
How can you go about fixing it and looking at the apache log file without any problems?