Fails to add a let's encrypt certificate via DNS for digital ocean provider.

I am using jc21/nginx-proxy-manager:latest on Raspbian 11 bullseye, and I'm trying to generate a wildcard certificate for NPM to use.

When attempting to add a let's encrypt certificate using the nice friendly GUI, I find it produces a red 'internal error' box with an error as follows (top of extract):

Error: Command failed: pip install certbot-dns-digitalocean==$(certbot --version | grep -Eo '[0-9](\.[0-9]+)+') 
  error: subprocess-exited-with-error
  
  × pip subprocess to install build dependencies did not run successfully.
  │ exit code: 1
  ╰─> [123 lines of output]

I will attach the details in a text file.

This is a brand new install, installed yesterday.

Nginx Proxy Manager Version is v2.9.16

To Reproduce
Steps to reproduce the behavior:

1. Log in
2. CLick on SSL Certs, Add
3. Enter wildcard domain name *.yourdomain.com
4. Make sure you click to add it just below where you entered the domain.
5. Enter a a valid email
6. TIck use DNS Challenge.
7. Choose digital ocean from providers list.
8. Go to digital ocean (cloud.digitalocean.com), log in and click API, generate new token
9. Set the token to your wildcard domain name (*.yourdomain.com)
10. Set expires: never,
11. Tick write access, then generate.
12. Click 'copy' just tot he right of the key.
13. Go back to the NPM screen and paste the key (replacing the existing code) after the 'token=' bit of the credentials area.
14. Tick agree and then SAVE.
15. Do nothing, just wait for the error.

Expected behavior
I expected it to contact Digital Ocean using the API key I gave it.

System
Rpi 2B
OS: Raspbian 11 bullseye
Kernel: armv7l Linux 5.10.92-v7+
CPU: ARMv7 rev 5 (v7l) @ 4x 900MHz
RAM: 922MiB

Additional context

details.txt

Start by reviewing the attached details.txt and reproducing the listed wildcard certificate steps on the specified Nginx Proxy Manager, Raspbian, and ARMv7 setup. Trace the pip and certbot installation failure for the DigitalOcean DNS provider; done means the wildcard certificate request completes without the internal error.