As to the issue of downloading from drupal.org using IPv6, this is still not possible - at least with a site on AWS Lightsail. AWS is raising the cost of having an IPv4 address on instances. Consequently I have recreated a drupal 10 site on an IPv6 exclusive instance. The site works fine except that it does not receive module update notices nor will composer update the project. Fortunately, I have a work-around using rsync to maintain the site from my development box, here at home. Drush works, though...
The problems seems to be that my AWS instance is IPv6 exclusively. If Drupal.org supports only IPv4 then I suppose there is no solution. My live site cannot receive security alerts and composer cannot download modules. My work-around is to maintain this site with rsync from my development box.
There is, in fact a book content type but any node (or most, maybe) can be included in a book. I just not sure its worth the effort of editing all of my content.
Most, if not all, of my content types are found in books. I have occasionally seen references to Taxonomy being a superior system of organizing a site and there are a number of issues I have with my site's current organization, not that taxonomy doesn't bring its own set of gotchas. I don't think that changing content types will help, but thanks for the thought.
AWS is about to increase the cost of Lightsail instances that support both IPv4 and IPv6, essentially the IPv4. They recommend creating a new instance that is only IPv6. I have tried both using a snapshot of my functioning IPv4/IPv6 instance and creating a new instance with ubuntu and installing a LAMP stack manually. My curl is 7.81.0, php 8.2.16 and composer 2.7.2
"Composer could not detect the root package (drupal/recommended-project) version, defaulting to '1.0.0'. See https://getcomposer.org/root-version"
curl error 28 while downloading https://packages.drupal.org/8/packages.json
: Connection timeout after 10004 ms
As I have no difficulty using composer update on the IPv4/IPv6 site I must assume that there is a problem with the missing IPv4 address.
After clearing cache with drush (drush cr) or even with the gui the directories default/files/styles/css and js revert back to www-data ownership from my desired ownership. chown allows me to drush cr again, but ownership changes back again.
Thanks for that headsup on mod rewrite. After spending hours chown, chgrp, and permissions this is what fixed it for me on Drupal 10.1.6
I rebuilt my ./styles directory and the problem went away. There may have been permission issues, I don't know but an rsync from my development system corrected whatever it was.
I understand that the database does not contain the actual image. The files in /sites/default/files and ./styles/ remain the same for both my development and production environments. With my development database, the images are displayed when the page is displayed on the browser, with my production database they are not. Using my production database, the icon indicating that the image cannot be displayed if clicked will bring up the image on a new page - so the path and the image are still there. They are not displayed as a rendered entity on the page.