Logstash HTTP output with SSL certificates not working on Ubuntu 14
up vote
0
down vote
favorite
The Logstash HTTP output when used for SSL authentication doesn't seem to be working on Ubuntu 14, but works perfect in Ubuntu 16.
Referring to this answer, I have compiled it with pkcs8 format of the key, and the same certificate and the same key works fine in Ubuntu 16, but not on Ubuntu 14. I am getting the error "Received fatal alert: handshake_failure" on Ubuntu 14, Any ideas on what's happening?
ssl openssl logstash
add a comment |
up vote
0
down vote
favorite
The Logstash HTTP output when used for SSL authentication doesn't seem to be working on Ubuntu 14, but works perfect in Ubuntu 16.
Referring to this answer, I have compiled it with pkcs8 format of the key, and the same certificate and the same key works fine in Ubuntu 16, but not on Ubuntu 14. I am getting the error "Received fatal alert: handshake_failure" on Ubuntu 14, Any ideas on what's happening?
ssl openssl logstash
add a comment |
up vote
0
down vote
favorite
up vote
0
down vote
favorite
The Logstash HTTP output when used for SSL authentication doesn't seem to be working on Ubuntu 14, but works perfect in Ubuntu 16.
Referring to this answer, I have compiled it with pkcs8 format of the key, and the same certificate and the same key works fine in Ubuntu 16, but not on Ubuntu 14. I am getting the error "Received fatal alert: handshake_failure" on Ubuntu 14, Any ideas on what's happening?
ssl openssl logstash
The Logstash HTTP output when used for SSL authentication doesn't seem to be working on Ubuntu 14, but works perfect in Ubuntu 16.
Referring to this answer, I have compiled it with pkcs8 format of the key, and the same certificate and the same key works fine in Ubuntu 16, but not on Ubuntu 14. I am getting the error "Received fatal alert: handshake_failure" on Ubuntu 14, Any ideas on what's happening?
ssl openssl logstash
ssl openssl logstash
asked Nov 20 at 13:38
scarvish
11
11
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
up vote
0
down vote
Turns out that my Ubuntu 14 had Java 1.7, which had some deprecated cipher suites, which was why I was getting an handshake failure while connecting to the server. It works fine in Java 1.8. You can provide custom Java to the logstash process by specifying JAVA_HOME=/path/to/your/JRE bin/logstash conf.d/logstash.conf.
add a comment |
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53394287%2flogstash-http-output-with-ssl-certificates-not-working-on-ubuntu-14%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
0
down vote
Turns out that my Ubuntu 14 had Java 1.7, which had some deprecated cipher suites, which was why I was getting an handshake failure while connecting to the server. It works fine in Java 1.8. You can provide custom Java to the logstash process by specifying JAVA_HOME=/path/to/your/JRE bin/logstash conf.d/logstash.conf.
add a comment |
up vote
0
down vote
Turns out that my Ubuntu 14 had Java 1.7, which had some deprecated cipher suites, which was why I was getting an handshake failure while connecting to the server. It works fine in Java 1.8. You can provide custom Java to the logstash process by specifying JAVA_HOME=/path/to/your/JRE bin/logstash conf.d/logstash.conf.
add a comment |
up vote
0
down vote
up vote
0
down vote
Turns out that my Ubuntu 14 had Java 1.7, which had some deprecated cipher suites, which was why I was getting an handshake failure while connecting to the server. It works fine in Java 1.8. You can provide custom Java to the logstash process by specifying JAVA_HOME=/path/to/your/JRE bin/logstash conf.d/logstash.conf.
Turns out that my Ubuntu 14 had Java 1.7, which had some deprecated cipher suites, which was why I was getting an handshake failure while connecting to the server. It works fine in Java 1.8. You can provide custom Java to the logstash process by specifying JAVA_HOME=/path/to/your/JRE bin/logstash conf.d/logstash.conf.
answered Nov 21 at 5:33
scarvish
11
11
add a comment |
add a comment |
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53394287%2flogstash-http-output-with-ssl-certificates-not-working-on-ubuntu-14%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown