The following renewal configurations were invalid

[BPL]

@Osiris

And the same goes for the hostnames, as they only exist in your hosts file, right?

Yeah, exactly, both vagrant boxes ips and hostnames would be private to my development box

@Osiris

You could however use wild card certificates. I.e., get a certificate for *.domain1 , *.domain2 et cetera. This would however require the use of the dns-01 challenge, which could be harder to set up compared to the http-01 challenge. Another reason to switch to the CentOS package manager to install certbot : it’s relatively hard to install one of the DNS plugins while using certbot-auto .

Not sure I haven't understood much out this explanation though but let me see whether I've understood a bit though... are you suggesting i should delete somehow the existing approved certificates for domain1, ..., domain7 and somehow create new certificates for *.domain1, ..., *.domain7? I didn't know it was possible to get certificates for wildcarded domains?

Another option (just random thought without any theorical basis) maybe... would it be possible somehow to use the approved certificates for the official domains in the staging boxes?

Anyway, just to let you know at this point I'm a bit confused so if you could please suggest me what'd be the easiest way to proceed here, I'd really appreciate it . I think at this point I've made clear my main goal is being able to use ssl in the staging boxes before deploying to production, so... This shouldn't be a very rare use-case, right?

Thanks in advance!