[SOLVED] Can't obtain/re-obtain Let's encrypt certificates after the upgrade to bookworm

I made for a second time a fresh installation of Freedombox and upgraded it successfully to Debian 12 bookworm, and both times I was unable to obtain or re-obtain Let’s encrypt certificate. I tried to re-obtain one before the update, and it was successful, but after that was unable to do it as the previous time with the update. So that might be an issue for the future.

Failed to obtain certificate for domain gemart.freedombox.rocks: (“Error obtaining certificate: Saving debug log to /var/log/letsencrypt/letsencrypt.log\nAn unexpected error occurred:\nAttributeError: can’t set attribute\nAsk for help or search for solutions at https://community.letsencrypt.org. See the logfile /var/log/letsencrypt/letsencrypt.log or re-run Certbot with -v for more details.\n”, b’‘, b’\x1b[31m ERROR\x1b[0m \x1b[94m__main__ \x1b[0m Error executing action: Error obtaining certificate: Saving debug log to /var/log/letsencrypt/letsencrypt.log\nAn unexpected error occurred:\nAttributeError: can't set attribute\nAsk for help or search for solutions at https://community.letsencrypt.org. See the logfile /var/log/letsencrypt/letsencrypt.log or re-run Certbot with -v for more details.\nTraceback (most recent call last):\n File “/usr/share/plinth/actions/actions”, line 92, in _call\n return_values = func(*arguments['args'], **arguments['kwargs'])\n ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^\n File “/usr/lib/python3/dist-packages/plinth/modules/letsencrypt/privileged.py”, line 171, in obtain\n raise RuntimeError('Error obtaining certificate: {error}'.format(\nRuntimeError: Error obtaining certificate: Saving debug log to /var/log/letsencrypt/letsencrypt.log\nAn unexpected error occurred:\nAttributeError: can't set attribute\nAsk for help or search for solutions at https://community.letsencrypt.org. See the logfile /var/log/letsencrypt/letsencrypt.log or re-run Certbot with -v for more details.\n\n’)

It is working now! I don’t know the reason it wasn’t before! It might be related with the allowance of the forwarding between firewall zones, but I’m not sure.