~/.secrets/certbot/ folder does not exist

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.

My domain is: travagh.me

I ran this command: nano ~/.secrets/certbot/digitalocean.ini

It produced this output: [ Directory '/root/.secrets/certbot' does not exist ]

My web server is (include version): Unknown, running AdGuard Home

The operating system my web server runs on is (include version): Ubuntu 22.04 (LTS) x64

My hosting provider, if applicable, is: DigitalOcean

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.6.0

I'm following the directions from here: Welcome to certbot-dns-digitalocean’s documentation! — certbot-dns-digitalocean 0 documentation

Performing 'cd ~/.secrets/certbot' give me the following error: -bash: cd: /root/.secrets/certbot/: No such file or directory

So it sounds like you need to create that directory if you want to edit the file in question.


With Linux, you can make use of the mkdir command to make new directories.

Also please note that the command snippets where you got the ~/.secrets/certbot from are just EXAMPLES as clearly stated at the top of the examples. So that means the commands are not necessarily a 1-on-1 fit for your specific situation.


I assumed from the instructions that it should exist. There is no indication of creating the directory, just the digitalocean.ini file within the directory.

As a wise man once said:

Assumption is the mother of all (...)

The command snippets are just examples. Documentation shouldn't need to spell out every small (and IMO obvious) detail. :slight_smile:

As they're just examples, you're free to put the digitalocean.ini anywhere you want, as long as it's SECURE :slight_smile: (i.e.: root readable and writable only). Heck, you don't even need to name it digitalocean.ini, you could name it bert_and_ernie.ini for all I care :stuck_out_tongue:


Thanks for your help :+1:


This is what I think @Osiris looks like now:


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