When I try to provision a SSL cert either from the admin interface or from ~/mailinabox/management/./ssl_certificates.py
it always gives me the same error below:
Plugins selected: Authenticator webroot, Installer None
You should register before running non-interactively, or provide --agree-tos and --email <email_address> flags.
My question is how the world do I specify what it is requesting so I can get my ssl cert to work? At this point I’m considering buying an SSL cert because LetsEncrypt is clearly broken somehow.
Hmmm… I have done this and was never prompted for anything related to Let’s Encrypt. Below is the trace back of everything that came up after the “sudo mailinabox” command. Can you point out what I might have missed to get my certificates to provision properly?
:~$ sudo mailinabox
┌────────────────────────Mail-in-a-Box Installation──────────────────────────┐
│ Hello and thanks for deploying a Mail-in-a-Box! │
│ │
│ I’m going to ask you a few questions. │
│ │
│ To change your answers later, just run ‘sudo mailinabox’ from the command │
│ line. │
│ │
│ NOTE: You should only install this on a brand new Ubuntu installation 100% │
│ dedicated to Mail-in-a-Box. Mail-in-a-Box will, for example, remove │
│ apache2. │
│ │
├────────────────────────────────────────────────────────────────────────────┤
│ < OK > │
└────────────────────────────────────────────────────────────────────────────┘
┌─────────────────────────────────Hostname───────────────────────────────────┐
│ This box needs a name, called a ‘hostname’. The name will form a part of │
│ the box’s web address. │
│ │
│ We recommend that the name be a subdomain of the domain in your email │
│ address, so we’re suggesting myemaildomain.net. │
│ │
│ You can change it, but we recommend you don’t. │
│ │
│ Hostname: │
│ ┌────────────────────────────────────────────────────────────────────────┐ │
│ │myemaildomain.net │ │
│ └────────────────────────────────────────────────────────────────────────┘ │
├────────────────────────────────────────────────────────────────────────────┤
│ < OK > │
└────────────────────────────────────────────────────────────────────────────┘
Primary Hostname: myemaildomain.net
Public IP Address: 19x.xxx.xxx.xx6
Private IPv6 Address: ::1
Mail-in-a-Box Version: v0.28
Updating system packages…
Installing system packages…
Initializing system random number generator…
Firewall is active and enabled on system startup
Installing nsd (DNS server)…
Installing Postfix (SMTP server)…
Installing Dovecot (IMAP server)…
Installing OpenDKIM/OpenDMARC…
Installing SpamAssassin…
Installing Nginx (web server)…
Installing Roundcube (webmail)…
Installing Nextcloud (contacts/calendar)…
Nextcloud is already latest version
Installing Z-Push (Exchange/ActiveSync server)…
Installing Mail-in-a-Box system management daemon…
I was trying to use the “Provision” button on the admin page when it failed with the exact same bug this thread detailed. So when I tried the same solution and ran into trouble, I thought it was right to be here. However after trying it some more and looking deeper, I started a separate thread due to the command failure itself.