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.
i used the below command to get a certificate from certbot which i them copeied to the folder that needed them and updated the configuration, but when i try to run the web application i get the following error x509: certificate signed by unknown authority
in request GET nyben.xyz/
2022/03/24 08:34:29 http: TLS handshake error from 207.148.4.123:43618: remote error: tls: bad certificate
Typically you will want to point your application to fullchain.pem rather than cert.pem.
At the moment, your nginx is not sending the intermediate certificate, which can cause software that connects to it, to fail to verify the certificate.
Also, usually you will want to directly point your webserver to use the certificate files in /etc/letsencrypt/live/ rather than copying the files, because copies of certificates do not get updated following automatic renewals.