Nexus Repository Manager 3 using SSL Unreachable by browsers or Docker

Multi tool use
up vote
0
down vote
favorite
I am not a java guy but we use Nexus for our NPM and Nuget packages and want to start using it to host Docker images as well but I cant seem to get SSL working using their guide. I am using version 3.14
I have generated the keystore and verified it works using:
keytool -printcert -sslserver localhost:8444 -v
My nexus.properties file contains
ssl.etc=${karaf.data}/etc/ssl
application-port-ssl=8444
nexus-args=${jetty.etc}/jetty.xml,${jetty.etc}/jetty-http.xml,${jetty.etc}/jetty-requestlog.xml,${jetty.etc}/jetty-https.xml
I have tried to update the local_policy.jar and US_export_policy.jar, tried updating the JRE and I still just get
ERR_SSL_VERSION_OR_CIPHER_MISMATCH from chrome when I try the browser or TLS Handshake failed with Docker trying to login.
java ssl

add a comment |
up vote
0
down vote
favorite
I am not a java guy but we use Nexus for our NPM and Nuget packages and want to start using it to host Docker images as well but I cant seem to get SSL working using their guide. I am using version 3.14
I have generated the keystore and verified it works using:
keytool -printcert -sslserver localhost:8444 -v
My nexus.properties file contains
ssl.etc=${karaf.data}/etc/ssl
application-port-ssl=8444
nexus-args=${jetty.etc}/jetty.xml,${jetty.etc}/jetty-http.xml,${jetty.etc}/jetty-requestlog.xml,${jetty.etc}/jetty-https.xml
I have tried to update the local_policy.jar and US_export_policy.jar, tried updating the JRE and I still just get
ERR_SSL_VERSION_OR_CIPHER_MISMATCH from chrome when I try the browser or TLS Handshake failed with Docker trying to login.
java ssl

1
Can you explain your choices when you generated your keystore? what algorithm? what bitsize? etc. Some choices will result in your issue.
– Joakim Erdfelt
yesterday
add a comment |
up vote
0
down vote
favorite
up vote
0
down vote
favorite
I am not a java guy but we use Nexus for our NPM and Nuget packages and want to start using it to host Docker images as well but I cant seem to get SSL working using their guide. I am using version 3.14
I have generated the keystore and verified it works using:
keytool -printcert -sslserver localhost:8444 -v
My nexus.properties file contains
ssl.etc=${karaf.data}/etc/ssl
application-port-ssl=8444
nexus-args=${jetty.etc}/jetty.xml,${jetty.etc}/jetty-http.xml,${jetty.etc}/jetty-requestlog.xml,${jetty.etc}/jetty-https.xml
I have tried to update the local_policy.jar and US_export_policy.jar, tried updating the JRE and I still just get
ERR_SSL_VERSION_OR_CIPHER_MISMATCH from chrome when I try the browser or TLS Handshake failed with Docker trying to login.
java ssl

I am not a java guy but we use Nexus for our NPM and Nuget packages and want to start using it to host Docker images as well but I cant seem to get SSL working using their guide. I am using version 3.14
I have generated the keystore and verified it works using:
keytool -printcert -sslserver localhost:8444 -v
My nexus.properties file contains
ssl.etc=${karaf.data}/etc/ssl
application-port-ssl=8444
nexus-args=${jetty.etc}/jetty.xml,${jetty.etc}/jetty-http.xml,${jetty.etc}/jetty-requestlog.xml,${jetty.etc}/jetty-https.xml
I have tried to update the local_policy.jar and US_export_policy.jar, tried updating the JRE and I still just get
ERR_SSL_VERSION_OR_CIPHER_MISMATCH from chrome when I try the browser or TLS Handshake failed with Docker trying to login.
java ssl

java ssl

asked yesterday
user1689716
6428
6428
1
Can you explain your choices when you generated your keystore? what algorithm? what bitsize? etc. Some choices will result in your issue.
– Joakim Erdfelt
yesterday
add a comment |
1
Can you explain your choices when you generated your keystore? what algorithm? what bitsize? etc. Some choices will result in your issue.
– Joakim Erdfelt
yesterday
1
1
Can you explain your choices when you generated your keystore? what algorithm? what bitsize? etc. Some choices will result in your issue.
– Joakim Erdfelt
yesterday
Can you explain your choices when you generated your keystore? what algorithm? what bitsize? etc. Some choices will result in your issue.
– Joakim Erdfelt
yesterday
add a comment |
2 Answers
2
active
oldest
votes
up vote
1
down vote
Since you are generating your keystore, make sure you use the following general advice.
- Use AES or RSA (not DSA or DES) for your key algorithm
- Use 2048 bits (or larger. go for 4096)
- Use a strong signature algorithm, such as SHA256 or SHA512 (not SHA, SHA1, MD5)
- Keystore type should be PKCS12 or JKS (for Java KeyStore)
If you use DSA or DES you will not be able to connect.
If you use too low of a bitsize you will not be able to connect.
If you use a poor signature algorithm, you will not be able to connect.
See https://www.eclipse.org/jetty/documentation/current/configuring-ssl.html for examples on generating a keystore using either keytool
or openssl
.
add a comment |
up vote
0
down vote
I found the issue. It was in how I was generating the keystore. I was using a .pfx exported cert from windows and had tried to split it into separate parts before importing to the keystore.
Once I just tried to import the pfx cert containing the private key as well, it worked. It was just appearing to work since the test
keytool -printcert -sslserver localhost:8444 -v
was returning the cert error free.
add a comment |
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
1
down vote
Since you are generating your keystore, make sure you use the following general advice.
- Use AES or RSA (not DSA or DES) for your key algorithm
- Use 2048 bits (or larger. go for 4096)
- Use a strong signature algorithm, such as SHA256 or SHA512 (not SHA, SHA1, MD5)
- Keystore type should be PKCS12 or JKS (for Java KeyStore)
If you use DSA or DES you will not be able to connect.
If you use too low of a bitsize you will not be able to connect.
If you use a poor signature algorithm, you will not be able to connect.
See https://www.eclipse.org/jetty/documentation/current/configuring-ssl.html for examples on generating a keystore using either keytool
or openssl
.
add a comment |
up vote
1
down vote
Since you are generating your keystore, make sure you use the following general advice.
- Use AES or RSA (not DSA or DES) for your key algorithm
- Use 2048 bits (or larger. go for 4096)
- Use a strong signature algorithm, such as SHA256 or SHA512 (not SHA, SHA1, MD5)
- Keystore type should be PKCS12 or JKS (for Java KeyStore)
If you use DSA or DES you will not be able to connect.
If you use too low of a bitsize you will not be able to connect.
If you use a poor signature algorithm, you will not be able to connect.
See https://www.eclipse.org/jetty/documentation/current/configuring-ssl.html for examples on generating a keystore using either keytool
or openssl
.
add a comment |
up vote
1
down vote
up vote
1
down vote
Since you are generating your keystore, make sure you use the following general advice.
- Use AES or RSA (not DSA or DES) for your key algorithm
- Use 2048 bits (or larger. go for 4096)
- Use a strong signature algorithm, such as SHA256 or SHA512 (not SHA, SHA1, MD5)
- Keystore type should be PKCS12 or JKS (for Java KeyStore)
If you use DSA or DES you will not be able to connect.
If you use too low of a bitsize you will not be able to connect.
If you use a poor signature algorithm, you will not be able to connect.
See https://www.eclipse.org/jetty/documentation/current/configuring-ssl.html for examples on generating a keystore using either keytool
or openssl
.
Since you are generating your keystore, make sure you use the following general advice.
- Use AES or RSA (not DSA or DES) for your key algorithm
- Use 2048 bits (or larger. go for 4096)
- Use a strong signature algorithm, such as SHA256 or SHA512 (not SHA, SHA1, MD5)
- Keystore type should be PKCS12 or JKS (for Java KeyStore)
If you use DSA or DES you will not be able to connect.
If you use too low of a bitsize you will not be able to connect.
If you use a poor signature algorithm, you will not be able to connect.
See https://www.eclipse.org/jetty/documentation/current/configuring-ssl.html for examples on generating a keystore using either keytool
or openssl
.
answered yesterday
Joakim Erdfelt
31.9k45594
31.9k45594
add a comment |
add a comment |
up vote
0
down vote
I found the issue. It was in how I was generating the keystore. I was using a .pfx exported cert from windows and had tried to split it into separate parts before importing to the keystore.
Once I just tried to import the pfx cert containing the private key as well, it worked. It was just appearing to work since the test
keytool -printcert -sslserver localhost:8444 -v
was returning the cert error free.
add a comment |
up vote
0
down vote
I found the issue. It was in how I was generating the keystore. I was using a .pfx exported cert from windows and had tried to split it into separate parts before importing to the keystore.
Once I just tried to import the pfx cert containing the private key as well, it worked. It was just appearing to work since the test
keytool -printcert -sslserver localhost:8444 -v
was returning the cert error free.
add a comment |
up vote
0
down vote
up vote
0
down vote
I found the issue. It was in how I was generating the keystore. I was using a .pfx exported cert from windows and had tried to split it into separate parts before importing to the keystore.
Once I just tried to import the pfx cert containing the private key as well, it worked. It was just appearing to work since the test
keytool -printcert -sslserver localhost:8444 -v
was returning the cert error free.
I found the issue. It was in how I was generating the keystore. I was using a .pfx exported cert from windows and had tried to split it into separate parts before importing to the keystore.
Once I just tried to import the pfx cert containing the private key as well, it worked. It was just appearing to work since the test
keytool -printcert -sslserver localhost:8444 -v
was returning the cert error free.
answered yesterday
user1689716
6428
6428
add a comment |
add a comment |
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
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53183851%2fnexus-repository-manager-3-using-ssl-unreachable-by-browsers-or-docker%23new-answer', 'question_page');
}
);
Post as a guest
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
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
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
lfRurq8RIn9rdnN,eEyk3ByPn9mPDCMKLffSVc
1
Can you explain your choices when you generated your keystore? what algorithm? what bitsize? etc. Some choices will result in your issue.
– Joakim Erdfelt
yesterday