Please fill out the fields below so we can help you better. Note: you must provide your domain name to get help. Domain names for issued certificates are all made public in Certificate Transparency logs (e.g. crt.sh | example.com), so withholding your domain name here does not increase secrecy, but only makes it harder for us to provide help.
It produced this output:
The Certificate Authority failed to download the challenge files from the temporary standalone webserver started by Certbot on port 80. Ensure that the listed domains point to this machine and that it can accept inbound connections from the internet.
My web server is (include version): AdGuard Home
The operating system my web server runs on is (include version): Raspberry 5 64bit bookworm Ver 12
My hosting provider, if applicable, is: ///
I can login to a root shell on my machine (yes or no, or I don't know): yes
I'm using a control panel to manage my site (no, or provide the name and version of the control panel): no
The version of my client is (e.g. output of certbot --version or certbot-auto --version if you're using Certbot): 2.1
HTTP challenge responses require that public TCP port 80 traffic reaches your target machine and that machine responds appropriately - all sort so fthings can be in the way - router, NAT, firewall, other security products, geographic blocking, something else using port 80 etc.
Basically the CA has to be able to get a valid response from http://weist-shao.ddns.net/.well-known/acme-challenge/something for it to work, with standalone mode the thing trying to serve the response is certbot itself, but any number of things can prevent that. A good test is to run a basic port 80 web server and access that from a public connection, that will at least tell you that you can achieve a connection to your machine.
This command will show you the challenge URL to try from the public internet and the proper response. After showing you this it will say "Press Enter to Continue". DO NOT PRESS ENTER.
Leave it paused like that and use a different device to test connection. You can use a mobile phone with wifi disabled so use your carrier's network.
You do not have to use the full URL. Just try http://(yourdomain)
If the connection works this shorter URL should see a response like below. I am pretty sure you will get a timeout error instead just like Let's Encrypt did. But, use this technique to modify your comms setup until it works.