Certbot on Ubuntu 16.04 - Unable to Run Certbot Commands


#1

Hi I need help

I’m running WordPress Multisite on Ubuntu 16.04, and on NGINX Server

I have a problem, a lot of attempts I’ve done but I couldn’t find how to do it.

I want to install letsencrypt not only for my root domain, but also for all of my subdomains. Some people suggesting running this script:

/opt/letsencrypt/letsencrypt-auto certonly --webroot -w /var/www/nama_domain/htdocs/ -d subdomain1.nama_domain.com -d subdomain2.nama_domain.com -d subdomain3.nama_domain.com --email surat@nama_domain.com --text --agree-tos

but showing up an error: bash: /opt/letsencrypt/letsencrypt-auto: No such file or directory
even I have installed letsencrypt on my Ubuntu.

or refer to this forum discussion: http://stackoverflow.com/questions/41429710/am-i-going-to-run-into-issues-using-lets-encrypt-ssl-on-wpmu-nginx

someone state to :
In your nginx site configuration, you will specify the single certificate which will be valid for all the domains yous specified with certbot.

server {
    ...
    ssl_certificate /etc/letsencrypt/live/example.com/fullchain.pem;
    ssl_certificate_key /etc/letsencrypt/live/example.com/privkey.pem;
    ...
}

Where is the nginx site configuration, or where do I edit a command/text/script so that each letsencrypt certificate refer to its own subdomain?

I haven’t running my web for 1 month just because of this :frowning: , need help.


#2

Hi @pramadiputra,

How did you install the client? Did you use the operating system package with apt-get? People referring to /opt/letsencrypt/letsencrypt-auto have installed it in a different way, something like this

Therefore, the command that they run in order to run Certbot is different. If you’ve installed the operating system package, you should probably simply type certbot in place of other people’s /opt/letsencrypt/letsencrypt-auto.

The nginx site configuration will be found in a series of text files instead of /etc/nginx. Typically there may be separate site definitions within the directory /etc/nginx/sites-available.


#3

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.