Issuing and renewing certificates has classically been a notoriously painful and expensive process.
Now solves that by automatically issuing free wildcard certificates when using our nameservers and associating a custom domain to a deployment. In other words, something that used to cost hundreds of dollars and significant engineering resources is now completely free and automatic.
Our philosophy is to give you the best developer experience, without making any concessions regarding power or API flexibility.
As a result, today we are introducing two advanced features for certificates:
- A fully-featured web dashboard where you can list and manage all your certificates
- A new
now certs issuesub-command (and its corresponding web UI) to manually trigger the issuance of a certificate
The Certs Dashboard
For any team or user, you will find a new subsection in your dashboard: Certs. We set out to bring the full experience of
now certsin the CLI to the web.
You can list, upload and delete certificates with ease:
Certificates are usually created as side effects of other operations. For example, when you buy a domain name, we optimistically generate a certificate with two common names:
- The domain prefixed with
- The wildcard prefix (
We are introducing two ways of creating certificates in our system:
Upload a certificate
If you already have a certificate issued by a third-party that you would like to upload to our system, you can press the Add button. This operation is equivalent to executing
now certs addby passing the
Issue a certificate
In addition to automatically issuing certificates on your behalf when you bring a domain to our platform, we now provide you with a workflow for doing so for external domains.
In a nutshell, it is now possible to create certificates (including wildcard!) for domains hosted elsewhere, which aids with a zero-downtime migration of domains hosted on platforms.
`now certs issue`
In addition to the new Web UI for cert issuance, we have added a new subcommand to our CLI:
now certs issue.
To issue a certificate for any domain (whether it is using our DNS nameservers or it is external), just run
now certs issue <cn> [...<cn>].
If the domain is not using our nameservers, we will not be able to solve the challenge required for Let's Encrypt to issue a free certificate, so we will present it to you:
If you want to write scripts that automate this process, you can perform this process non-interactively, broken down into two steps:
now certs issue --challenge-onlywill present only the challenge
now certs issuewill issue the certificate
The core mission of our company is to make the cloud accessible to everyone in the world. A vital part of this is making it dramatically more straightforward to use.
Making a complicated process easy without giving our customers the ability to access, visualize and manipulate the underlying primitives is not sufficient.
With these improvements, we are giving you full control -from both the web and the terminal- over your certificates, one of the fundamental building blocks of a secure end-to-end deployment platform.