Created
February 7, 2018 18:10
-
-
Save yuezhu/47b15b4b8e944221861ccf7d7f5868f5 to your computer and use it in GitHub Desktop.
Generate self-signed certificate for HAProxy
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
# Generate a unique private key (KEY) | |
sudo openssl genrsa -out mydomain.key 2048 | |
# Generating a Certificate Signing Request (CSR) | |
sudo openssl req -new -key mydomain.key -out mydomain.csr | |
# Creating a Self-Signed Certificate (CRT) | |
openssl x509 -req -days 365 -in mydomain.csr -signkey mydomain.key -out mydomain.crt | |
# Append KEY and CRT to mydomain.pem | |
sudo bash -c 'cat mydomain.key mydomain.crt >> /etc/ssl/private/mydomain.pem' | |
# Specify PEM in haproxy config | |
sudo vim /etc/haproxy/haproxy.cfg | |
listen haproxy | |
bind 0.0.0.0:443 ssl crt /etc/ssl/private/mydomain.pem |
This helped me out. tutorials seem to give out too much information
Thanks it was helpfull.
thank I just use it to test. It fix my problem for create .pem wrong.
Maybe is it missing a sudo on line 8?
Thanks, I was looking for this...
Much needed information
thank you it was helpful.
PS: sudo is missing on line 8
You have saved my life! Thank you so much, brother.
Thank you, it works perfectly!
I recommend use of single inequality sign (>) instead of double (>>) in line 11:
sudo bash -c 'cat mydomain.key mydomain.crt > /etc/ssl/private/mydomain.pem'
If you do mistake in previous key or cert file and run this command with double ones, it will append to file instead of overriding. In my case it lead to confusing errors of "inconsistencies between private key and certificate".
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Thanks I needed this