The purpose of this document is to help with configuring and troubleshooting using TLS on the connection between Beats and Logstash.
You must configure TLS on both the client and server to make this work. This
nginx and Go Daddy SSL certificates | |
Generate the CSR: | |
1 openssl genrsa 2048 > yourhost.com.key | |
2 openssl req -new -key yourhost.com.key > yourhost.com.csr | |
Enter in whatever you want - you NEED the "Common Name" everything else is not really required for it to work. | |
01 Country Name (2 letter code) [AU]:US | |
02 State or Province Name (full name) [Some-State]:. | |
03 Locality Name (eg, city) []:. | |
04 Organization Name (eg, company) [Internet Widgits Pty Ltd]:Something Here | |
05 Organizational Unit Name (eg, section) []:. |
# to generate your dhparam.pem file, run in the terminal | |
openssl dhparam -out /etc/nginx/ssl/dhparam.pem 2048 |
Minimal example: transcode from MP3 to WMA:
ffmpeg -i input.mp3 output.wma
You can get the list of supported formats with:
ffmpeg -formats
Convert WAV to MP3, mix down to mono (use 1 audio channel), set bit rate to 64 kbps and sample rate to 22050 Hz:
I use Namecheap.com as a registrar, and they resale SSL Certs from a number of other companies, including Comodo.
These are the steps I went through to set up an SSL cert.
git clone [email protected]:YOUR-USERNAME/YOUR-FORKED-REPO.git
cd into/cloned/fork-repo
git remote add upstream git://github.com/ORIGINAL-DEV-USERNAME/REPO-YOU-FORKED-FROM.git
git fetch upstream