Using Lets Encrypt SSL certificates with crossbar WAMP router (0.13)
A certificate has been generated from Let's Encrypt and installed onto an existing (working) crossbar server as follows (and as the documentation suggests):
"endpoint": {
"type": "tcp",
"port": 8089,
"tls": {
"key": "../ssl/key.pem",
"certificate": "../ssl/cert.pem"
}
},
When connecting via Java (I am sure the result would have been similar if differently worded in other APIs) the result is:
java.security.cert.CertPathValidatorException: Trust anchor for certification path not found
Having determined this could be due to requiring Let's Encrypt's intermediate certificate that was linked like this:
"endpoint": {
"type": "tcp",
"port": 8089,
"tls": {
"key": "../ssl/key.pem",
"certificate": "../ssl/cert.pem",
"ca_certificates": [
"../ssl/intermediate.cert.pem"
],
}
},
Unfortunately this also does not work, resulting in a handshake error (I didn't note down the exact wording).
android websocket lets-encrypt crossbar wamp-protocol asked Nov 27 '18 at 11:04
M1keM1ke
3,84031942
add a comment |
A certificate has been generated from Let's Encrypt and installed onto an existing (working) crossbar server as follows (and as the documentation suggests):
"endpoint": {
"type": "tcp",
"port": 8089,
"tls": {
"key": "../ssl/key.pem",
"certificate": "../ssl/cert.pem"
}
},
When connecting via Java (I am sure the result would have been similar if differently worded in other APIs) the result is:
java.security.cert.CertPathValidatorException: Trust anchor for certification path not found
Having determined this could be due to requiring Let's Encrypt's intermediate certificate that was linked like this:
"endpoint": {
"type": "tcp",
"port": 8089,
"tls": {
"key": "../ssl/key.pem",
"certificate": "../ssl/cert.pem",
"ca_certificates": [
"../ssl/intermediate.cert.pem"
],
}
},
Unfortunately this also does not work, resulting in a handshake error (I didn't note down the exact wording).
android websocket lets-encrypt crossbar wamp-protocol asked Nov 27 '18 at 11:04
M1keM1ke
3,84031942
add a comment |
A certificate has been generated from Let's Encrypt and installed onto an existing (working) crossbar server as follows (and as the documentation suggests):
"endpoint": {
"type": "tcp",
"port": 8089,
"tls": {
"key": "../ssl/key.pem",
"certificate": "../ssl/cert.pem"
}
},
When connecting via Java (I am sure the result would have been similar if differently worded in other APIs) the result is:
java.security.cert.CertPathValidatorException: Trust anchor for certification path not found
Having determined this could be due to requiring Let's Encrypt's intermediate certificate that was linked like this:
"endpoint": {
"type": "tcp",
"port": 8089,
"tls": {
"key": "../ssl/key.pem",
"certificate": "../ssl/cert.pem",
"ca_certificates": [
"../ssl/intermediate.cert.pem"
],
}
},
Unfortunately this also does not work, resulting in a handshake error (I didn't note down the exact wording).
android websocket lets-encrypt crossbar wamp-protocol asked Nov 27 '18 at 11:04
M1keM1ke
3,84031942
A certificate has been generated from Let's Encrypt and installed onto an existing (working) crossbar server as follows (and as the documentation suggests):
"endpoint": {
"type": "tcp",
"port": 8089,
"tls": {
"key": "../ssl/key.pem",
"certificate": "../ssl/cert.pem"
}
},
When connecting via Java (I am sure the result would have been similar if differently worded in other APIs) the result is:
java.security.cert.CertPathValidatorException: Trust anchor for certification path not found
Having determined this could be due to requiring Let's Encrypt's intermediate certificate that was linked like this:
"endpoint": {
"type": "tcp",
"port": 8089,
"tls": {
"key": "../ssl/key.pem",
"certificate": "../ssl/cert.pem",
"ca_certificates": [
"../ssl/intermediate.cert.pem"
],
}
},
Unfortunately this also does not work, resulting in a handshake error (I didn't note down the exact wording).
android websocket lets-encrypt crossbar wamp-protocol android websocket lets-encrypt crossbar wamp-protocol asked Nov 27 '18 at 11:04
M1keM1ke
3,84031942
asked Nov 27 '18 at 11:04
M1keM1ke
3,84031942
asked Nov 27 '18 at 11:04
M1keM1ke
3,84031942
asked Nov 27 '18 at 11:04
M1keM1ke
3,84031942
asked Nov 27 '18 at 11:04
M1keM1ke
3,84031942
3,84031942
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
Digging further into the documentation I found this example which explicitly references a lets encrypt intermediate but has a different name for the key parameter:
"chain_certificates": [
"lets-encrypt-x3-cross-signed.pem"
],
Trying this resulted in the same issue (handshake failure)
I then tried the following:
- Concatenate the certificate file with Let's Encrypt's intermediate
- Revert to the initial configuration just using the certificate and key parameters
So basically this:
"tls": {
"key": "../ssl/key.pem",
"certificate": "../ssl/cert-plus-intermediate.pem"
}
After restarting the server again (you'll need to restart each time you change SSL settings) the connection established correctly. Note also that once you have a working configuration you should ensure the key file can only be read by a trusted user on the system, ideally just whichever user crossbar will run as (chmod 600 key.pem)
answered Nov 27 '18 at 11:04
M1keM1ke
3,84031942
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',
autoActivateHeartbeat: false,
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%2f53498267%2fusing-lets-encrypt-ssl-certificates-with-crossbar-wamp-router-0-13%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
Digging further into the documentation I found this example which explicitly references a lets encrypt intermediate but has a different name for the key parameter:
"chain_certificates": [
"lets-encrypt-x3-cross-signed.pem"
],
Trying this resulted in the same issue (handshake failure)
I then tried the following:
- Concatenate the certificate file with Let's Encrypt's intermediate
- Revert to the initial configuration just using the certificate and key parameters
So basically this:
"tls": {
"key": "../ssl/key.pem",
"certificate": "../ssl/cert-plus-intermediate.pem"
}
After restarting the server again (you'll need to restart each time you change SSL settings) the connection established correctly. Note also that once you have a working configuration you should ensure the key file can only be read by a trusted user on the system, ideally just whichever user crossbar will run as (chmod 600 key.pem)
answered Nov 27 '18 at 11:04
M1keM1ke
3,84031942
add a comment |
Digging further into the documentation I found this example which explicitly references a lets encrypt intermediate but has a different name for the key parameter:
"chain_certificates": [
"lets-encrypt-x3-cross-signed.pem"
],
Trying this resulted in the same issue (handshake failure)
I then tried the following:
- Concatenate the certificate file with Let's Encrypt's intermediate
- Revert to the initial configuration just using the certificate and key parameters
So basically this:
"tls": {
"key": "../ssl/key.pem",
"certificate": "../ssl/cert-plus-intermediate.pem"
}
After restarting the server again (you'll need to restart each time you change SSL settings) the connection established correctly. Note also that once you have a working configuration you should ensure the key file can only be read by a trusted user on the system, ideally just whichever user crossbar will run as (chmod 600 key.pem)
answered Nov 27 '18 at 11:04
M1keM1ke
3,84031942
add a comment |
Digging further into the documentation I found this example which explicitly references a lets encrypt intermediate but has a different name for the key parameter:
"chain_certificates": [
"lets-encrypt-x3-cross-signed.pem"
],
Trying this resulted in the same issue (handshake failure)
I then tried the following:
- Concatenate the certificate file with Let's Encrypt's intermediate
- Revert to the initial configuration just using the certificate and key parameters
So basically this:
"tls": {
"key": "../ssl/key.pem",
"certificate": "../ssl/cert-plus-intermediate.pem"
}
After restarting the server again (you'll need to restart each time you change SSL settings) the connection established correctly. Note also that once you have a working configuration you should ensure the key file can only be read by a trusted user on the system, ideally just whichever user crossbar will run as (chmod 600 key.pem)
answered Nov 27 '18 at 11:04
M1keM1ke
3,84031942
Digging further into the documentation I found this example which explicitly references a lets encrypt intermediate but has a different name for the key parameter:
"chain_certificates": [
"lets-encrypt-x3-cross-signed.pem"
],
Trying this resulted in the same issue (handshake failure)
I then tried the following:
- Concatenate the certificate file with Let's Encrypt's intermediate
- Revert to the initial configuration just using the certificate and key parameters
So basically this:
"tls": {
"key": "../ssl/key.pem",
"certificate": "../ssl/cert-plus-intermediate.pem"
}
After restarting the server again (you'll need to restart each time you change SSL settings) the connection established correctly. Note also that once you have a working configuration you should ensure the key file can only be read by a trusted user on the system, ideally just whichever user crossbar will run as (chmod 600 key.pem)
answered Nov 27 '18 at 11:04
M1keM1ke
3,84031942
answered Nov 27 '18 at 11:04
M1keM1ke
3,84031942
answered Nov 27 '18 at 11:04
M1keM1ke
3,84031942
answered Nov 27 '18 at 11:04
M1keM1ke
3,84031942
3,84031942
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.
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%2f53498267%2fusing-lets-encrypt-ssl-certificates-with-crossbar-wamp-router-0-13%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
