Nxt Forum

Please login or register.

Login with username, password and session length
Advanced search  

News:

Latest Nxt Client 1.11.5 - NEW RELEASE: Ardor 2.0.3e TestNet IS LAUNCHED!

Pages: 1 [2] 3 4  All

Author Topic: NRS v1.8.1  (Read 12196 times)

Riker

  • Core Dev
  • Hero Member
  • *****
  • Offline Offline
  • Posts: 1576
    • View Profile
  • Karma: +411/-42
Re: NRS v1.8.1
April 09, 2016, 02:42:34 pm

I forget to report a bug in 1.8.0e,I can't import contacts from browser wallet into desktop application.

Right, the problem is that the JavaFX webview does not support the Html5 File APIs.
This means that we have to read the contacts file differently when using the Desktop Wallet.
I'll do my best to fix this for 1.8.2
NXT Core Dev
Account: NXT-HBFW-X8TE-WXPW-DZFAG
Public Key: D8311651 Key fingerprint: 0560 443B 035C EE08 0EC0  D2DD 275E 94A7 D831 1651

SamIbandii

  • Full Member
  • ***
  • Offline Offline
  • Posts: 110
  • do great things while they are small (Lao Tzu)
    • View Profile
  • Karma: +10/-3
Re: NRS v1.8.1
April 09, 2016, 03:32:39 pm

Jean Luc and Riker,
Today I installed NRS v1.8.1. All went smoothly.
Again "you both boldly go were no one has gone before".

Thanks

youyou

  • Sr. Member
  • ****
  • Offline Offline
  • Posts: 472
    • View Profile
  • Karma: +44/-46
Re: NRS v1.8.1
April 09, 2016, 06:43:22 pm

i get this at first launch (after upgrading from 1.7.5):

Code: [Select]
2016-04-09 20:41:37 SEVERE: Database error executing ALTER TABLE purchase ADD COLUMN IF NOT EXISTS goods_is_text BOOLEAN NOT NULL DEFAULT TRUE
java.lang.RuntimeException: Database error executing ALTER TABLE purchase ADD COLUMN IF NOT EXISTS goods_is_text BOOLEAN NOT NULL DEFAULT TRUE
at nxt.db.DbVersion.apply(DbVersion.java:83)
at nxt.NxtDbVersion.update(NxtDbVersion.java:1167)
at nxt.db.DbVersion.init(DbVersion.java:55)
at nxt.db.BasicDb.init(BasicDb.java:140)
at nxt.Db.init(Db.java:39)
at nxt.Nxt$Init.<clinit>(Nxt.java:341)
at nxt.Nxt.init(Nxt.java:311)
at nxt.Nxt.main(Nxt.java:298)
Caused by: org.h2.jdbc.JdbcSQLException: Table "PURCHASE" not found; SQL statement:
ALTER TABLE purchase ADD COLUMN IF NOT EXISTS goods_is_text BOOLEAN NOT NULL DEFAULT TRUE [42102-176]
at org.h2.message.DbException.getJdbcSQLException(DbException.java:344)
at org.h2.message.DbException.get(DbException.java:178)
at org.h2.message.DbException.get(DbException.java:154)
at org.h2.command.Parser.readTableOrView(Parser.java:5213)
at org.h2.command.Parser.readTableOrView(Parser.java:5190)
at org.h2.command.Parser.parseAlterTable(Parser.java:5267)
at org.h2.command.Parser.parseAlter(Parser.java:4689)
at org.h2.command.Parser.parsePrepared(Parser.java:333)
at org.h2.command.Parser.parse(Parser.java:306)
at org.h2.command.Parser.parse(Parser.java:278)
at org.h2.command.Parser.prepareCommand(Parser.java:243)
at org.h2.engine.Session.prepareLocal(Session.java:442)
at org.h2.engine.Session.prepareCommand(Session.java:384)
at org.h2.jdbc.JdbcConnection.prepareCommand(JdbcConnection.java:1188)
at org.h2.jdbc.JdbcStatement.executeUpdateInternal(JdbcStatement.java:128)
at org.h2.jdbc.JdbcStatement.executeUpdate(JdbcStatement.java:117)
at nxt.db.FilteredStatement.executeUpdate(FilteredStatement.java:45)
at nxt.db.TransactionalDb$DbStatement.executeUpdate(TransactionalDb.java:288)
at nxt.db.DbVersion.apply(DbVersion.java:74)
... 7 more

JZA

  • Full Member
  • ***
  • Offline Offline
  • Posts: 148
  • Looking for the NXT big thing
    • View Profile
  • Karma: +18/-0
Re: NRS v1.8.1
April 09, 2016, 08:46:47 pm


Did you try to install 1.8.0e ? How can I reproduce this ?
Yes I did that too, got the same error. Basically just click on the initial download button, wait until is done and click on the 'green message' -> select the file from the file chooser, and waited until it loaded/install. Then it came back with that red message.
NXT stufff, NXT-TUAH-6PVY-S2KR-AW4RK

OutSL

  • Sr. Member
  • ****
  • Offline Offline
  • Posts: 332
    • View Profile
  • Karma: +60/-0
Re: NRS v1.8.1
April 09, 2016, 09:42:52 pm

Hi  :D
very good job :D thank you for the image modal, this is better than the image in the same modal and may lead to more features in relation with the products displays  :D

thank you again and @++
Thank you for your financial help, your donations will be used in the R&D related to the implementation of NXT in the virtual worlds running under OpenSimulator.org | Donations Box : NXT-PC8Q-ZW86-7UYK-CC4XJ
Visit The NXT Community Virtal World! Your NXT 3D Chat Service

Klokan

  • Sr. Member
  • ****
  • Offline Offline
  • Posts: 271
    • View Profile
  • Karma: +28/-5
Re: NRS v1.8.1
April 09, 2016, 09:49:23 pm

Is there some change with SSL handling in 1.8 series ? I used URL https://name.of.nrs.server:7876 for 1.7.5 (and every older versions), without any problems. But in 1.8.1 (with exactly the same nxt.properties config in conf/, with copied files keystore/mycerts into main nxt/ directory, etc.) Firefox (45.0.1, Fedora) kicks me out with "Secure Connection Failed" warning/error. Chromium is able to work further, but it also cries about unsecure connection ...

Each other things (means NRS "as is", listening on the port 7874/tcp) works fine...

thnx for any hints.
I am able to access the SSL port on my node using both Microsoft Edge and Chrome.  There is a problem in 1.8.1 when an absolute path is specified for the keystore in nxt.properties.  What did you specify for nxt.keyStorePath?

I have in conf/nxt.properties :

Code: [Select]
nxt.keyStorePath=keystore
So it's relative, not absolute path, I assume.
Yes, that's a relative path.  Which means it will be prefixed with the Nxt user data directory path.  This path depends on the OS and the runtime environment mode.  If -Dnxt.runtime.mode is not specified on the java command, then the Nxt user data directory is the install directory (same as previous releases).  Otherwise, the Nxt user data directory depends on the OS and is the value returned for the user.home system property.  For Linux, this is usually /home/user-name/.nxt.  For Windows, this is usually \Users\user-name\AppData\Roaming\Nxt.  Not familiar with Mac.

Also, it sounds like your keystore is mycerts located in the keystore directory.  If so, then nxt.keyStorePath should be keystore/mycerts and not just keystore.  But that hasn't changed from previous releases, so I probably don't understand something.

Yes, I have something like /home/nxt-user/nxt/ as a "main directory"; under this directory is/are :
    nxt_db/ - data / DB
    conf/ (with nxt.properties copied from previous releases and default nxt-default.properties)
    keystore file
    mycert.crt & mycert.pkcs12 files
    etc...

It's exactly the same structure since 1.0 or maybe 0.7.x releases ... Just one idea: I did ./compile.sh before ./run.sh - but it also probably is not the issue, as I do compiling each time with building up of new NRS versions ...

farl4bit

  • Global Moderator
  • Hero Member
  • *****
  • Offline Offline
  • Posts: 3370
  • Go Nxt!
    • View Profile
    • Blockchain Startpagina
  • Karma: +204/-45
Re: NRS v1.8.1
April 09, 2016, 10:08:50 pm

Will there be a Mac Nxt.app again?

ScripterRon

  • Sr. Member
  • ****
  • Offline Offline
  • Posts: 457
    • View Profile
  • Karma: +72/-2
Re: NRS v1.8.1
April 09, 2016, 10:47:49 pm

Yes, I have something like /home/nxt-user/nxt/ as a "main directory"; under this directory is/are :
    nxt_db/ - data / DB
    conf/ (with nxt.properties copied from previous releases and default nxt-default.properties)
    keystore file
    mycert.crt & mycert.pkcs12 files
    etc...

It's exactly the same structure since 1.0 or maybe 0.7.x releases ... Just one idea: I did ./compile.sh before ./run.sh - but it also probably is not the issue, as I do compiling each time with building up of new NRS versions ...
This doesn't sound like an NRS problem since the server just returns the certificate to the browser.  Can you view the certificate being returned to the browser?  For Chrome, you can get this from the Developer Tools Console (Customize -> More Tools -> Developer Tools -> Security).  I don't use Firefox, so I don't know how you do it with that browser.

If the correct certificate is being returned, then you'll need to check your system certificates cache to verify the trust path and make sure none of the certificates have expired.
NXT-XM86-4ZNA-65L5-CDWUE

Riker

  • Core Dev
  • Hero Member
  • *****
  • Offline Offline
  • Posts: 1576
    • View Profile
  • Karma: +411/-42
Re: NRS v1.8.1
April 10, 2016, 05:09:15 am

Will there be a Mac Nxt.app again?

The 1.8.1 Mac installer is similar to the 1.8.0e installer.
Always install it to a folder named nxt.app so that it shows up as an application in the finder.
NXT Core Dev
Account: NXT-HBFW-X8TE-WXPW-DZFAG
Public Key: D8311651 Key fingerprint: 0560 443B 035C EE08 0EC0  D2DD 275E 94A7 D831 1651

Riker

  • Core Dev
  • Hero Member
  • *****
  • Offline Offline
  • Posts: 1576
    • View Profile
  • Karma: +411/-42
Re: NRS v1.8.1
April 10, 2016, 05:14:58 am

Yes, I have something like /home/nxt-user/nxt/ as a "main directory"; under this directory is/are :
    nxt_db/ - data / DB
    conf/ (with nxt.properties copied from previous releases and default nxt-default.properties)
    keystore file
    mycert.crt & mycert.pkcs12 files
    etc...

It's exactly the same structure since 1.0 or maybe 0.7.x releases ... Just one idea: I did ./compile.sh before ./run.sh - but it also probably is not the issue, as I do compiling each time with building up of new NRS versions ...
This doesn't sound like an NRS problem since the server just returns the certificate to the browser.  Can you view the certificate being returned to the browser?  For Chrome, you can get this from the Developer Tools Console (Customize -> More Tools -> Developer Tools -> Security).  I don't use Firefox, so I don't know how you do it with that browser.

If the correct certificate is being returned, then you'll need to check your system certificates cache to verify the trust path and make sure none of the certificates have expired.

Also, I suggest you look in the nxt.log to see if there are errors or exceptions. Especially look for errors related to loading the keystore file.
If nothing comes up, add the following command line flag to the Java command: -Djavax.net.debug=all
See: http://docs.oracle.com/javase/7/docs/technotes/guides/security/jsse/ReadDebug.html

It should print a lot of diagnostic information to the console and/or nxt.log
Look for an Exception message.
Capture it to a file and post it here if you need more help.
NXT Core Dev
Account: NXT-HBFW-X8TE-WXPW-DZFAG
Public Key: D8311651 Key fingerprint: 0560 443B 035C EE08 0EC0  D2DD 275E 94A7 D831 1651

Klokan

  • Sr. Member
  • ****
  • Offline Offline
  • Posts: 271
    • View Profile
  • Karma: +28/-5
Re: NRS v1.8.1
April 10, 2016, 08:21:51 am

Is there some change with SSL handling in 1.8 series ? I used URL https://name.of.nrs.server:7876 for 1.7.5 (and every older versions), without any problems. But in 1.8.1 (with exactly the same nxt.properties config in conf/, with copied files keystore/mycerts into main nxt/ directory, etc.) Firefox (45.0.1, Fedora) kicks me out with "Secure Connection Failed" warning/error. Chromium is able to work further, but it also cries about unsecure connection ...

Each other things (means NRS "as is", listening on the port 7874/tcp) works fine...

thnx for any hints.
I am able to access the SSL port on my node using both Microsoft Edge and Chrome.  There is a problem in 1.8.1 when an absolute path is specified for the keystore in nxt.properties.  What did you specify for nxt.keyStorePath?

I have in conf/nxt.properties :

Code: [Select]
nxt.keyStorePath=keystore
So it's relative, not absolute path, I assume.
Yes, that's a relative path.  Which means it will be prefixed with the Nxt user data directory path.  This path depends on the OS and the runtime environment mode.  If -Dnxt.runtime.mode is not specified on the java command, then the Nxt user data directory is the install directory (same as previous releases).  Otherwise, the Nxt user data directory depends on the OS and is the value returned for the user.home system property.  For Linux, this is usually /home/user-name/.nxt.  For Windows, this is usually \Users\user-name\AppData\Roaming\Nxt.  Not familiar with Mac.

Also, it sounds like your keystore is mycerts located in the keystore directory.  If so, then nxt.keyStorePath should be keystore/mycerts and not just keystore.  But that hasn't changed from previous releases, so I probably don't understand something.

Yes, I have something like /home/nxt-user/nxt/ as a "main directory"; under this directory is/are :
    nxt_db/ - data / DB
    conf/ (with nxt.properties copied from previous releases and default nxt-default.properties)
    keystore file
    mycert.crt & mycert.pkcs12 files
    etc...

It's exactly the same structure since 1.0 or maybe 0.7.x releases ... Just one idea: I did ./compile.sh before ./run.sh - but it also probably is not the issue, as I do compiling each time with building up of new NRS versions ...

Just additional info : When I start NRS with relative path (nxt.keyStore.Path=keystore), it starts well with this info message :
Code: [Select]
2016-04-09 23:54:30 INFO: Nxt server 1.8.1 started successfully.
2016-04-09 23:54:30 INFO: Copyright © 2013-2016 The Nxt Core Developers.
2016-04-09 23:54:30 INFO: Distributed under GPLv2, with ABSOLUTELY NO WARRANTY.
2016-04-09 23:54:30 INFO: Client UI is at https://89.250.240.63:7876/index.html
2016-04-09 23:54:30 FINE: Known peers: 251

But there is still the same trouble with "Secure Connection Failed" error in Firefox. When I got absolute path into nxt.properties config file, e.g. :

Code: [Select]
nxt.keyStorePath=/home/someuser/nxt/keystore
NRS crashed quickly after ./run.sh, with this message :

Code: [Select]
2016-04-09 23:58:28 SEVERE: Failed to start API server
java.lang.IllegalStateException: no valid keystore
....
2016-04-09 23:58:37 SEVERE: Errors running startup tasks:
java.lang.IllegalStateException: no valid keystore

java.lang.RuntimeException: Errors running startup tasks:
java.lang.IllegalStateException: no valid keystore

        at nxt.util.ThreadPool.runAll(ThreadPool.java:150)
        at nxt.util.ThreadPool.start(ThreadPool.java:78)
        at nxt.Nxt$Init.<clinit>(Nxt.java:379)
        at nxt.Nxt.init(Nxt.java:311)
        at nxt.Nxt.main(Nxt.java:298)
2016-04-09 23:58:37 INFO: Shutting down...

Klokan

  • Sr. Member
  • ****
  • Offline Offline
  • Posts: 271
    • View Profile
  • Karma: +28/-5
Re: NRS v1.8.1
April 10, 2016, 08:34:10 am

Yes, I have something like /home/nxt-user/nxt/ as a "main directory"; under this directory is/are :
    nxt_db/ - data / DB
    conf/ (with nxt.properties copied from previous releases and default nxt-default.properties)
    keystore file
    mycert.crt & mycert.pkcs12 files
    etc...

It's exactly the same structure since 1.0 or maybe 0.7.x releases ... Just one idea: I did ./compile.sh before ./run.sh - but it also probably is not the issue, as I do compiling each time with building up of new NRS versions ...
This doesn't sound like an NRS problem since the server just returns the certificate to the browser.  Can you view the certificate being returned to the browser?  For Chrome, you can get this from the Developer Tools Console (Customize -> More Tools -> Developer Tools -> Security).  I don't use Firefox, so I don't know how you do it with that browser.

If the correct certificate is being returned, then you'll need to check your system certificates cache to verify the trust path and make sure none of the certificates have expired.

I also thought it would be an expired certificate, so I built up a new one, as described here :

https://nxtwiki.org/wiki/How-To:UseSslCerts

...with exactly the same way I built it up before (a year or so). So now I have freshly new certificate (and mycert.* and keystore files), but situation is still the same...so "expired something" is probably not the case too.

Riker

  • Core Dev
  • Hero Member
  • *****
  • Offline Offline
  • Posts: 1576
    • View Profile
  • Karma: +411/-42
Re: NRS v1.8.1
April 10, 2016, 08:57:11 am

Yes, I have something like /home/nxt-user/nxt/ as a "main directory"; under this directory is/are :
    nxt_db/ - data / DB
    conf/ (with nxt.properties copied from previous releases and default nxt-default.properties)
    keystore file
    mycert.crt & mycert.pkcs12 files
    etc...

It's exactly the same structure since 1.0 or maybe 0.7.x releases ... Just one idea: I did ./compile.sh before ./run.sh - but it also probably is not the issue, as I do compiling each time with building up of new NRS versions ...
This doesn't sound like an NRS problem since the server just returns the certificate to the browser.  Can you view the certificate being returned to the browser?  For Chrome, you can get this from the Developer Tools Console (Customize -> More Tools -> Developer Tools -> Security).  I don't use Firefox, so I don't know how you do it with that browser.

If the correct certificate is being returned, then you'll need to check your system certificates cache to verify the trust path and make sure none of the certificates have expired.

I also thought it would be an expired certificate, so I built up a new one, as described here :

https://nxtwiki.org/wiki/How-To:UseSslCerts

...with exactly the same way I built it up before (a year or so). So now I have freshly new certificate (and mycert.* and keystore files), but situation is still the same...so "expired something" is probably not the case too.

I had a similar problem, first with Chrome then later with Firefox, try to re-create the keystore with keysize of 2048 (the default is 1024)
i.e. generate a new keystore and when issuing keytool -genkeypair add -keysize 2048
NXT Core Dev
Account: NXT-HBFW-X8TE-WXPW-DZFAG
Public Key: D8311651 Key fingerprint: 0560 443B 035C EE08 0EC0  D2DD 275E 94A7 D831 1651

Klokan

  • Sr. Member
  • ****
  • Offline Offline
  • Posts: 271
    • View Profile
  • Karma: +28/-5
Re: NRS v1.8.1
April 10, 2016, 09:17:05 am

Yes, I have something like /home/nxt-user/nxt/ as a "main directory"; under this directory is/are :
    nxt_db/ - data / DB
    conf/ (with nxt.properties copied from previous releases and default nxt-default.properties)
    keystore file
    mycert.crt & mycert.pkcs12 files
    etc...

It's exactly the same structure since 1.0 or maybe 0.7.x releases ... Just one idea: I did ./compile.sh before ./run.sh - but it also probably is not the issue, as I do compiling each time with building up of new NRS versions ...
This doesn't sound like an NRS problem since the server just returns the certificate to the browser.  Can you view the certificate being returned to the browser?  For Chrome, you can get this from the Developer Tools Console (Customize -> More Tools -> Developer Tools -> Security).  I don't use Firefox, so I don't know how you do it with that browser.

If the correct certificate is being returned, then you'll need to check your system certificates cache to verify the trust path and make sure none of the certificates have expired.

I also thought it would be an expired certificate, so I built up a new one, as described here :

https://nxtwiki.org/wiki/How-To:UseSslCerts

...with exactly the same way I built it up before (a year or so). So now I have freshly new certificate (and mycert.* and keystore files), but situation is still the same...so "expired something" is probably not the case too.

I had a similar problem, first with Chrome then later with Firefox, try to re-create the keystore with keysize of 2048 (the default is 1024)
i.e. generate a new keystore and when issuing keytool -genkeypair add -keysize 2048

Well, I re-created keystore file with `keytool -keysize 2048....', use the new keystore, but nothing happen, still the same issue. For sure, I tried it also from FF in Windows (32bit XP old virtual instance), exactly the same error occurs. There's no possibility to use "Proceed anyway", show certificate or something like this (with invalid/expired certificate FF makes this posibility, usually), it's just link there to this page :

https://support.mozilla.org/en-US/kb/what-does-your-connection-is-not-secure-mean

So it looks like for me like FF "cannot feel" any certificate / SSL encryption on the other side (means server with NRS) ... which is really strange. Again, with 1.7.5 (with exactly same config of NRS, OS and OS environment) everything works fine...

PS: When I was in "archaic" WinXP environment, I also tried archaic MSIE 8 ... exactly the same error "MSIE application cannot displayed this page" and that's all. With connection to 1.7.5., MSIE 8 cries about "invalid & self-signed" certificate, well, but user can proceed it further and everything works...

JZA

  • Full Member
  • ***
  • Offline Offline
  • Posts: 148
  • Looking for the NXT big thing
    • View Profile
  • Karma: +18/-0
Re: NRS v1.8.1
April 10, 2016, 09:22:46 am

I am getting this error after downloading and unziping NSR:
Code: [Select]
Exception in thread "Thread-0" java.lang.NoSuchFieldError: MATCHER
        at org.eclipse.jetty.server.handler.gzip.GzipHandler.<init>(GzipHandler.java:75)
        at nxt.http.API.<clinit>(API.java:218)
        at nxt.Nxt.shutdown(Nxt.java:317)
        at java.lang.Thread.run(Thread.java:745)
Using Java 1.8.0, OpenJDK.
NXT stufff, NXT-TUAH-6PVY-S2KR-AW4RK

ScripterRon

  • Sr. Member
  • ****
  • Offline Offline
  • Posts: 457
    • View Profile
  • Karma: +72/-2
Re: NRS v1.8.1
April 10, 2016, 12:30:09 pm

I am getting this error after downloading and unziping NSR:
Code: [Select]
Exception in thread "Thread-0" java.lang.NoSuchFieldError: MATCHER
        at org.eclipse.jetty.server.handler.gzip.GzipHandler.<init>(GzipHandler.java:75)
        at nxt.http.API.<clinit>(API.java:218)
        at nxt.Nxt.shutdown(Nxt.java:317)
        at java.lang.Thread.run(Thread.java:745)
Using Java 1.8.0, OpenJDK.
NoSuchFieldError indicates an object field does not exist.  It looks like another error caused NRS to terminate before it completed initialization.  Are there other errors in nxt.log?  If you installed over an existing installation, did you first delete the 'classes', 'html' and 'lib' directories?
NXT-XM86-4ZNA-65L5-CDWUE

OutSL

  • Sr. Member
  • ****
  • Offline Offline
  • Posts: 332
    • View Profile
  • Karma: +60/-0
Re: NRS v1.8.1
April 10, 2016, 02:52:19 pm

Hi  :D

What is the best way to convert the let's encrypt certificates to the keystore files ? there is a wiki guide or a tutorial about that ?
is this methode will work?
https://nxtwiki.org/wiki/How-To:UseSslCerts
i installed let's encrypt with the apache plugin... that created 4 files : cert.pem , chain.pem , fullchain.pem and privkey.pem  ??? what are the files that i have to use to create the .pkcs12 ?

thank you all and @++
Thank you for your financial help, your donations will be used in the R&D related to the implementation of NXT in the virtual worlds running under OpenSimulator.org | Donations Box : NXT-PC8Q-ZW86-7UYK-CC4XJ
Visit The NXT Community Virtal World! Your NXT 3D Chat Service

CryptKeeper

  • Hero Member
  • *****
  • Offline Offline
  • Posts: 1229
    • View Profile
  • Karma: +76/-5
Re: NRS v1.8.1
April 10, 2016, 05:41:05 pm

Hi,

first: the 1.8.1 release is great!  :)

I have some smaller issues I want to report here.
I've tested the Desktop on my windows 10 and experienced some refresh problems, if I run the program maximized:




(Logout popup is sometimes partially hidden, more than you can see in this picture)


(Asset Exchange)

If you confirm a phasing approval request, the indicator in the left-hand sidebar doesn't change:


It doesn't even change when you click on it:



It would be nice if you could use the left mouse click for copy/paste in accounts and passphrases.

That's all, thanks for our attention and keep up the good work!
Follow me on twitter for the latest news on bitcoin and altcoins!
Vanity Accounts Sale :-)

Riker

  • Core Dev
  • Hero Member
  • *****
  • Offline Offline
  • Posts: 1576
    • View Profile
  • Karma: +411/-42
Re: NRS v1.8.1
April 10, 2016, 06:11:04 pm

Folks, in order not to lose track of all non-critical problem reports, I'd like to ask users to create a ticket in https://bitbucket.org/JeanLucPicard/nxt/issues for each problem.
NXT Core Dev
Account: NXT-HBFW-X8TE-WXPW-DZFAG
Public Key: D8311651 Key fingerprint: 0560 443B 035C EE08 0EC0  D2DD 275E 94A7 D831 1651

Riker

  • Core Dev
  • Hero Member
  • *****
  • Offline Offline
  • Posts: 1576
    • View Profile
  • Karma: +411/-42
Re: NRS v1.8.1
April 10, 2016, 06:16:14 pm

Well, I re-created keystore file with `keytool -keysize 2048....', use the new keystore, but nothing happen, still the same issue. For sure, I tried it also from FF in Windows (32bit XP old virtual instance), exactly the same error occurs. There's no possibility to use "Proceed anyway", show certificate or something like this (with invalid/expired certificate FF makes this posibility, usually), it's just link there to this page :

https://support.mozilla.org/en-US/kb/what-does-your-connection-is-not-secure-mean

So it looks like for me like FF "cannot feel" any certificate / SSL encryption on the other side (means server with NRS) ... which is really strange. Again, with 1.7.5 (with exactly same config of NRS, OS and OS environment) everything works fine...

PS: When I was in "archaic" WinXP environment, I also tried archaic MSIE 8 ... exactly the same error "MSIE application cannot displayed this page" and that's all. With connection to 1.7.5., MSIE 8 cries about "invalid & self-signed" certificate, well, but user can proceed it further and everything works...

As I asked before, please add the following command line flag to the Java command: -Djavax.net.debug=all
See: http://docs.oracle.com/javase/7/docs/technotes/guides/security/jsse/ReadDebug.html

It should print a lot of diagnostic information to the console and/or nxt.log
Look for an Exception message.
Capture it to a file and post it here if you need more help.
NXT Core Dev
Account: NXT-HBFW-X8TE-WXPW-DZFAG
Public Key: D8311651 Key fingerprint: 0560 443B 035C EE08 0EC0  D2DD 275E 94A7 D831 1651
Pages: 1 [2] 3 4  All