.

[kprell40]

  Hello

   Does anyone know if the bittrex Wallet is working ?  it says wallet maintenance

[CryptoClub]

  Hello

   Does anyone know if the bittrex Wallet is working ?  it says wallet maintenance

Looks like wallet maintenance, not sure why, but likely just routine.

[CryptoClub]

A brutal day for Bitcoin and most alts, but not for Horizon, not today! Make sure and check out HZchronos too!

[Pizpie]

  Hello

   Does anyone know if the bittrex Wallet is working ?  it says wallet maintenance

Looks like wallet maintenance, not sure why, but likely just routine.

Yes, it was standard maintenance.

[kprell40]

   Help
  May I ask is there something going on with the node page not updating the time ?

  my Node

NODE IP ADDRESS: XX.X.XXX.Xx (ONLINE)   it is working on the pc
Last Checked: 2015-04-26 19:05:17 | Last Payout: 2015-04-25 03:22:53
Total Uptime: 42345 mins | Uptime Until Next Payout: 855 mins     <--------->  this as bean the same Time  for the pass 12 hrs not updating like it did in the pass days  and I did not get paid for 2015-04-26

 

[BDCoinMiner]

   Help
  May I ask is there something going on with the node page not updating the time ?

  my Node

NODE IP ADDRESS: XX.X.XXX.Xx (ONLINE)   it is working on the pc
Last Checked: 2015-04-26 19:05:17 | Last Payout: 2015-04-25 03:22:53
Total Uptime: 42345 mins | Uptime Until Next Payout: 855 mins     <--------->  this as bean the same Time  for the pass 12 hrs not updating like it did in the pass days  and I did not get paid for 2015-04-26

 

It seems problem with HZ own node checking script. you can give your node IP address as it is not private address. And as node checking page showing 'ONLINE' status mean you don't have to worry about it. But what is the version of HZ software you running?? Today's payment was more then 700HZ mean they stopped paying old, outdated version node to pay. Double check your node version and payment tx .

Cheers.

[kprell40]

   Help
  May I ask is there something going on with the node page not updating the time ?

  my Node

NODE IP ADDRESS: XX.X.XXX.Xx (ONLINE)   it is working on the pc
Last Checked: 2015-04-26 19:05:17 | Last Payout: 2015-04-25 03:22:53
Total Uptime: 42345 mins | Uptime Until Next Payout: 855 mins     <--------->  this as bean the same Time  for the pass 12 hrs not updating like it did in the pass days  and I did not get paid for 2015-04-26

 

It seems problem with HZ own node checking script. you can give your node IP address as it is not private address. And as node checking page showing 'ONLINE' status mean you don't have to worry about it. But what is the version of HZ software you running?? Today's payment was more then 700HZ mean they stopped paying old, outdated version node to pay. Double check your node version and payment tx .

Cheers.

 yes my Node ver V3.8   I will go and see if there is a update Ver and install it  ty ..
.

[BDCoinMiner]

   Help
  May I ask is there something going on with the node page not updating the time ?

  my Node

NODE IP ADDRESS: XX.X.XXX.Xx (ONLINE)   it is working on the pc
Last Checked: 2015-04-26 19:05:17 | Last Payout: 2015-04-25 03:22:53
Total Uptime: 42345 mins | Uptime Until Next Payout: 855 mins     <--------->  this as bean the same Time  for the pass 12 hrs not updating like it did in the pass days  and I did not get paid for 2015-04-26

 

It seems problem with HZ own node checking script. you can give your node IP address as it is not private address. And as node checking page showing 'ONLINE' status mean you don't have to worry about it. But what is the version of HZ software you running?? Today's payment was more then 700HZ mean they stopped paying old, outdated version node to pay. Double check your node version and payment tx .

Cheers.

 yes my Node ver V3.8   I will go and see if there is a update Ver and install it  ty ..
.

Current updated HZ version is 3.9.1; so don't forget to update it towards 3.9.1. There was a version 3.9 only which is absolute by 3.9.1. To get paid you may need to run 3.9.1.

Cheers
BDCoinMiner
HZ: NHZ-8GHQ-TJRL-5VUK-FTPZT

[altsheets]

Hah, I found something in the (old!) manual...

That oldid=29356 manual is definitely at least one step too old, compared to the current HZ3.9.1

I only know that since now, because I have just found out that requestType=sendMessage is already much newer than mentioned there. HZ already has a lot more parameters, namely for encrypting messages.

Wow, these were lost hours, until I realized that. (But as a side effect, I have started to dive into the Java code, had been hoping for answers there) .


Which brings me back to my original questions:

I would look it up in some HZ manual, but which one?

On ...:7776/test is a dead link to wiki docs.

Also, could you please run the javadoc.sh on http://api.nhz...

Thanks.

[altsheets]

Code:

2015-04-27 05:38:51 INFO: Scanning blockchain...
2015-04-27 05:40:19 INFO: processed block 0
2015-04-27 05:42:12 INFO: processed block 5000
2015-04-27 05:45:49 INFO: processed block 10000
...

Is there an option to tell the NRS to not scan the blockchain when starting up?
It takes many minutes, compared to only seconds with the new Nxt.

Thx.

[altsheets]

Block explorer - what have you just changed?

After it worked for many hours, then about 1 hour ago, this error suddenly appeared:

urllib2.URLError: <urlopen error [Errno 1] _ssl.c:504: error:14077438:SSL routines:SSL23_GET_SERVER_HELLO:tlsv1 alert internal error>

when I python-access the page https://explorer.horizonplatform.io/api.php?page=accounts
that GeBeWolf told me to use as a workaround to get all addresses, to find my shareholders.

Code:

import urllib2
f = urllib2.urlopen("https://explorer.horizonplatform.io/api.php?page=accounts")  

It is a well known bug that is somehow connected to the cyphers that the server uses:
https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/861137
http://blog.techstacks.com/2008/09/securing-ssl-in-tomcat-part-two.html

Have you updated the block explorer server in the past approx 1 hour?
Or is there a cloudflare between us, and the settings changed? Thx.

[MaWo]

Code:

2015-04-27 05:38:51 INFO: Scanning blockchain...
2015-04-27 05:40:19 INFO: processed block 0
2015-04-27 05:42:12 INFO: processed block 5000
2015-04-27 05:45:49 INFO: processed block 10000
...

Is there an option to tell the NRS to not scan the blockchain when starting up?
It takes many minutes, compared to only seconds with the new Nxt.

Thx.

No, the nrs has to scan the blockchain to build all objects as Java objects.
Our upcoming HZ version will have derived object in database tables.

[BDCoinMiner]

Cool;)

Seems more people are trying to update their node with latest version of HZ;) Last day node bounty was around 790HZ where today bounty was set to around 711 HZ /node / day.

making payment stop is most powerful tools to drive all ignorant people to update their node.


Keep the network running:)


Cheers
BDCoinMiner
HZ: NHZ-8GHQ-TJRL-5VUK-FTPZT

[BDCoinMiner]

Cool;)

Seems more people are trying to update their node with latest version of HZ;) Last day node bounty was around 790HZ where today bounty was set to around 711 HZ /node / day.

making payment stop is most powerful tools to drive all ignorant people to update their node.


Keep the network running:)


Cheers
BDCoinMiner
HZ: NHZ-8GHQ-TJRL-5VUK-FTPZT

Sorry guys; I mention wrong number on above posting.

Node bounty was :

4/24/2015    499.00199601 HZ
4/25/2015    595.59261465 HZ
4/26/2015    709.21985816 HZ

and today's bounty was:

4/27/2015    711.23755334 HZ


Isn't it cool on node runner's point of view?


Cheers
BDCoinMiner
HZ: NHZ-8GHQ-TJRL-5VUK-FTPZT

[richwang]

A brutal day for Bitcoin and most alts, but not for Horizon, not today! Make sure and check out HZchronos too!

HZ rank 81.

[altsheets]

Block explorer - what have you just changed?
After it worked for many hours, then about 1 hour ago, this error suddenly appeared:

urllib2.URLError: <urlopen error [Errno 1] _ssl.c:504: error:14077438:SSL routines:SSL23_GET_SERVER_HELLO:tlsv1 alert internal error>

when I python-access the page https://explorer.horizonplatform.io/api.php?page=accounts
that GeBeWolf told me to use as a workaround to get all addresses, to find my shareholders.

Code:

import urllib2
f = urllib2.urlopen("https://explorer.horizonplatform.io/api.php?page=accounts")  

It is a well known bug that is somehow connected to the cyphers that the server uses:
https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/861137
http://blog.techstacks.com/2008/09/securing-ssl-in-tomcat-part-two.html
Have you updated the block explorer server in the past approx 1 hour?
Or is there a cloudflare between us, and the settings changed? Thx.

Or have you upgraded to a newer OpenSSL, or webserver last night?


Here is a solution for you to try, please try changing this on your webserver:

The solution is to restrict available ciphers in Tomcat’s https connector:

Code:

ciphers="SSL_RSA_WITH_RC4_128_SHA"

Restart Tomcat and curl will work.

http://georgik.sinusgear.com/2012/02/19/tomcat-7-and-curl-ssl23_get_server_hellotlsv1-alert-internal-error/

5 Responses:

Raghavendra Chary B says:
26. October 2012 at 13:35
It worked, thanks very much!

Sagar says:
17. May 2013 at 11:04
Thank you very much , helped me a lot.

mitra says:
21. January 2014 at 13:31
Very Cool

Beverly says:
1. July 2014 at 0:31
It worked. Thank you so much for posting this. After almost two weeks of trouble shooting.

val says:
17. July 2014 at 11:07
Cпacибo!!!

[altsheets]

Code:

2015-04-27 05:38:51 INFO: Scanning blockchain...
2015-04-27 05:40:19 INFO: processed block 0
2015-04-27 05:42:12 INFO: processed block 5000
2015-04-27 05:45:49 INFO: processed block 10000
...

Is there an option to tell the NRS to not scan the blockchain when starting up?
It takes many minutes, compared to only seconds with the new Nxt.
Thx.

No, the nrs has to scan the blockchain to build all objects as Java objects.
Our upcoming HZ version will have derived object in database tables.

Thanks a lot! Good to know.

[altsheets]

Block explorer - what have you just changed?
After it worked for many hours, then about 1 hour ago, this error suddenly appeared:

urllib2.URLError: <urlopen error [Errno 1] _ssl.c:504: error:14077438:SSL routines:SSL23_GET_SERVER_HELLO:tlsv1 alert internal error>

...

Whatever you had done there last night, it had broken backwards compatibility.
Perhaps it was simply some automatic server updates - probably intended to force OpenSSL upgrades in clients?

To solve it, clientside, I have deinstalled, and reinstalled my whole Python environment, into a newer version.

Now this test

Code:

import urllib2, ssl; print ssl.OPENSSL_VERSION
url = "https://explorer.horizonplatform.io/api.php?page=accounts"
f=urllib2.urlopen(urllib2.Request(url, None, headers))
answer = f.read()
f.close()
print len(answer)

results in error free:

OpenSSL 1.0.1j 15 Oct 2014
263511

So all is good again.  I have caught up with your changes.

[CryptoClub]

Last couple hours of the sale for HZchronos, ends Midnight tonight central standard time USA, just listed as TRUSTED asset on the Horizonplatform.io website!

https://bitcointalk.org/index.php?topic=1022989.0
Bitcointalk Announcement Thread

https://www.facebook.com/groups/1610748235805154/
HZchronos Facebook Page

http://www.hzchronos.com
HZchronos Website

https://horizonplatform.io
Official Horizon Website - Get Wallets Here!

[GoldenEye]

The node bounty account is dry, again.