Nxt Forum

Nxt Discussion => Nxt Software Releases => Official Nxt Releases => Topic started by: Jelurida on November 18, 2017, 09:49:42 am

Title: NRS v1.11.10
Post by: Jelurida on November 18, 2017, 09:49:42 am
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Release 1.11.10

https://www.jelurida.com/

sha256 checksums:

b3d875a157263fcd51789b351a6cea939333538b04e824f43d2d71f56c36bccd  nxt-client-1.11.10.zip

d29ae53f872b3ce07c7731c3d3545b8a366288f29aa5f475c557119dffaa049b  nxt-client-1.11.10.sh

The exe and dmg packages must have a digital signature by "Stichting NXT".


Change log:

Removed the IGNIS Token Sale page.

Mobile app bugfixes, node.js module improvements, other minor bugfixes.

Updated jetty to 9.3.22 and bouncycastle to 1.58.


-----BEGIN PGP SIGNATURE-----

iQIcBAEBCgAGBQJaD/jtAAoJEAz5x0ctgLi5PMYP/ien4j9DG19OVt4HSqwjfVMm
wNuLKrwf9iT/9p4E8/4rBytorXnQ2LQ7pJKO8XAt9iwZEyJ5Nb0NtwKb56Z0swVg
MddrC7XCWNexrJWUdNg603zFxwM/sAdDKDndekKfqGA6Ddq6pV7jTC/1/eMOF8Pm
VriHbtmLE31WUhbIiz1xNNzwruxqTnox9Xjrutfc6j/z9J56Ca/wOw0Czpzs/lCm
39UsczZ5SOZPGYVGrJZXBoCTvgFAoGIAo9YlI1SS+rBmnqPud3HzvDmRPg6Xfzd3
9eTrM263NeykRM500VfCNteJs9udAsfknyFd7ySDn5mQrNM+TMZ/jQjb0vs9y7Vs
+P6ZegvYre4KNNybyh/UJQl0NfAFehQWOFubBDrJvaWcfR+HyH6ob6FEL8zSaSyy
lJWdiErxscemCgY4LMZBX7HIGkZ8AjTsI2TdkKHVJTVqn6BD2QH0Ze8XevFcSlyK
mVCbp/QAyB11e0InRSD7qI7ap1SEx1mL2rJBYr2XrHexGGSFjCkQd7zdhqvH8fmw
bHThRe+V+dqVcoEIVrBeSVep6asJGM6dqLQ6pQ2tiuFGk/I/N3tk/YOcwXR90sjT
g08/IZ9zoAGBMg7ANte2qvyrI3/s84OZuULDBc9NRnCHBr3a5kA1Qha4TWzxX28W
tCbiwTlGrsYo38MjHbf5
=QECd
-----END PGP SIGNATURE-----
Title: Re: NRS v1.11.10
Post by: Riker on November 18, 2017, 09:56:02 am
Updated Android mobile app https://bitbucket.org/Jelurida/nxt/downloads/nxt-client-1.11.10.apk
sha256 fddc74a2683bd4124e2f81751d170154a2127a3d8b11cd72ed9ac13591160f04
Title: Re: NRS v1.11.10
Post by: hbit on November 20, 2017, 11:24:08 am
Hi, install went fine  ;D
But was there any change related to https?

My apache2 ssl and reverse proxy configuration gives me:

Quote
Proxy Error
The proxy server received an invalid response from an upstream server.
The proxy server could not handle the request GET /.
Reason: Error reading from remote server


Debian GNU/Linux 9
Apache/2.4.25
Title: Re: NRS v1.11.10
Post by: Riker on November 20, 2017, 12:39:42 pm
Hi, install went fine  ;D
But was there any change related to https?

My apache2 ssl and reverse proxy configuration gives me:

Quote
Proxy Error
The proxy server received an invalid response from an upstream server.
The proxy server could not handle the request GET /.
Reason: Error reading from remote server


Debian GNU/Linux 9
Apache/2.4.25

We upgraded Jetty, nothing I can think of otherwise.
Title: Re: NRS v1.11.10
Post by: hbit on November 20, 2017, 01:36:23 pm
Apache log states:

[Mon Nov 20 13:19:04.432557 2017] [proxy_http:error] [pid 2114:tid 140657401140992] (103)Software caused connection abort: [client 123.123.123.123:61365] AH01102: error reading status line from remote server localhost:7876

Feels like apache2 having some sort of issue when connecting to Jetty.
Apart from that, node is working fine when directly connecting to port 7876.

Title: Re: NRS v1.11.10
Post by: Brangdon on November 25, 2017, 08:14:38 pm
I've some comments on the Windows installer, which I started using recently.
Title: Re: NRS v1.11.10
Post by: hob on December 09, 2017, 06:07:18 pm
I don't know if it is related to this version or not, but I get massive

Code: [Select]
2017-12-09 19:03:39 FINE: Peer w.x.y.z version null returned error: {"error":"Maximum number of inbound connections exceeded"}, request was: {"protocol":1,"application":"NRS","requestType":"getInfo","blockchainState":3,"services":"0","version":"1.11.10","platform":"Linux amd64","shareAddress":false}, disconnecting

and in fact I have only 1 connected peer at the moment from 7/12 up-to-date peers, with up to 3-5 connected peers as maximum. After restarting the node it takes significant time to get to a connected peer or any peer at all.

It seems all those responses run the 1.11.10 version.
Title: Re: NRS v1.11.10
Post by: hob on December 10, 2017, 12:08:11 am
No, I confused that with the request version which of course is my 1.11.10, the replies are null, 1.11.2, 1.11.8, 1.11.9 or 1.11.10
elective-stereophonic
elective-stereophonic
assembly
assembly