EasyConvert / Security & Tokens

SSL & OpenSSL Setup Guide

Generate Certbot commands, Let’s Encrypt configs, and OpenSSL self-signed certificate commands. Free browser-based tool with no signup required.

About SSL & OpenSSL Setup Guide

Generate Certbot commands, Let’s Encrypt configs, and OpenSSL self-signed certificate commands.

The tool is designed to process data in the browser unless the interface explicitly states that a network request is required.

How to use this tool

Enter or select the domain, web server, operating system value you want to work with.
Review the available settings, then run the configure action.
Review the certbot command, https setup steps, openssl command output and use the copy or download action when the tool provides one.

What you can do with SSL & OpenSSL Setup Guide

Set up lets encrypt certificate
Generate certbot command
Create self signed ssl command

What this conversion does

Generate the exact OpenSSL command and per-operating-system steps to create and trust a self-signed certificate for localhost or any development hostname.

Example input

Common name: localhost, valid for 365 days, OS: macOS

Example output

sudo openssl req -x509 -nodes -days 365 -newkey rsa:2048 -keyout localhost.key -out localhost.crt -subj "/CN=localhost" — plus the Keychain “Always Trust” steps

Practical workflow

Enter the common name — localhost, a .local or .test hostname, or the domain your dev server answers on.
Set how many days the certificate should stay valid and choose Linux, macOS, or Windows.
Click Generate Steps and run the printed OpenSSL command in your terminal; it writes <name>.crt and <name>.key to the current directory.
Follow the OS-specific steps to add the certificate to the trust store so browsers stop warning.

Common use cases

Serve a local development site over HTTPS to test service workers, secure cookies, or OAuth redirects.
Give an internal staging server a certificate without involving a public certificate authority.
Learn the standard openssl req invocation and what each flag means before automating it.

Important notes and limitations

This is a guide generator: it produces commands and instructions, not certificate files. The private key is created on your machine when you run the command — nothing is generated or transmitted by the browser.
The command uses RSA 2048 and sets only the Common Name. Modern browsers require a Subject Alternative Name (SAN); if Chrome still warns, add -addext "subjectAltName=DNS:<name>" to the command.
Self-signed certificates are for development and internal use. For public sites use Let's Encrypt or another CA.

Continue your workflow

SSH Key Generator — create Ed25519 or RSA key pairs in the browser.
File Encryption & Decryption — protect the generated private key file with a passphrase before storing it.

Frequently asked questions

Does this tool create the certificate for me?

No. It writes the exact OpenSSL command and installation steps for your OS. You run the command locally, which keeps the private key on your machine.

Why does my browser still show a warning after trusting the certificate?

Chrome and Firefox require a Subject Alternative Name that matches the hostname. Add -addext "subjectAltName=DNS:localhost" (or your name) to the generated command and re-import the certificate.

What does -nodes mean?

“No DES” — the private key is written unencrypted so your dev server can start without prompting for a passphrase. Do not use -nodes for keys that leave your machine.

Can I use this for a real website?

Self-signed certificates are not trusted by visitors' browsers. For a public domain use Let's Encrypt (free) or a commercial certificate authority.