Just saw this again on a server I upgraded. . .
The error you’re talking about is this one:
I, [2025-04-01T15:14:58.799796 #1] INFO -- : > awk -F\# '{print $1;}' ~/.ssh/authorized_keys | awk 'BEGIN { print "Authorized SSH keys for this container:"; } NF>=2 {print $NF
;}'
awk: fatal: cannot open file `/root/.ssh/authorized_keys' for reading: No such file or directory
I, [2025-04-01T15:14:58.810714 #1] INFO -- : Authorized SSH keys for this container:
And though awk thinks it’s fatal. I promise, it’s not actually a problem. You’ve been ignoring t for years. 
I’ve been wondering when that was going to be true, but it seems not to be for many folks so far. I think I’ve seen one other example.
You can get out of jail free by adding another hostname (like just add www. as another name) as described at Setup Multisite Configuration with Let's Encrypt and no Reverse Proxy and include just the after_ssl stanza.