Closed Thread - page 393. | Bitcointalksearch.org

HunterMinerCrafter

sr. member

Activity: 434

Merit: 250

Linux/OSX client? Source?

The nodewebkit binary version shipped for the client has some known vulnerabilities. I would not recommend to anyone to run this version until we can easily run against our own nodewebkit.

~~Anyone know of an easy way to extract a nodewebkit app from a windows exe packaging? I'm not too familiar with nodewebkit binary builds.~~

EDIT: nevermind, I got it... I'll post an analysis and hopefully some instructions on how to run this thing more safely shortly.

SillkRoad

full member

Activity: 140

Merit: 100

Quote from: zhaohui on August 11, 2014, 09:34:00 AM

Loading ... Please wait! how long do I have to wait? Huh

https://docs.google.com/document/d/1Mu1BG811L2-OGJTBdKTARtQKljs1SXIJnFWoRcKSLFI/edit

wait for the update next version

You need to understand something is the first version, we will fix bugs

zhaohui

full member

Activity: 126

Merit: 100

Loading ... Please wait! how long do I have to wait? Huh

zhaohui

full member

Activity: 126

Merit: 100

the wallet shows: Loading .......please wait!

hypersire

hero member

Activity: 596

Merit: 500

Quote from: ?? on ??

@devs

I am afraid the people that were reporting getting a different account were right... Sad

I had only checked my balance through the block explorer because there was no SSL... waited patiently for the client... plugged in my passphrase... different account... Cry

NO copy paste from a text file either... I have the passphrase hand-written on a piece of paper... Undecided

Edit: Can you please upload the Account Generator somewhere?

I am referring to the one we used when you asked us to change accounts... I want to see if I am getting the same account number.

smaragda, from what I remember from people who reported the same issue, it turned out to be caused by one of two reasons:

1) the person was using an account number from the first server and never made an account on the new server when the devs requested it (when they did the sock puppet IP check)

2) I remember someone else who had their passphrase written down, and after trying several variations they were able to get in.

Don't know what else it could be as the devs has assured everyone that nothing has been touched in the algorithm since the second server went live. So if you logged in and verified the account then, it should be the same today.

SillkRoad

full member

Activity: 140

Merit: 100

@Thanks for testing
We write all the errors here https://docs.google.com/document/d/1Mu1BG811L2-OGJTBdKTARtQKljs1SXIJnFWoRcKSLFI/edit
In the next version we will gradually fix all errors

englishbad

sr. member

Activity: 364

Merit: 250

Quote from: sava0123 on August 11, 2014, 09:04:01 AM

Quote from: koop4u on August 11, 2014, 08:43:45 AM

If somebody can, please provide a screen shot of that error!

yes！

sava0123

sr. member

Activity: 393

Merit: 250

Quote from: koop4u on August 11, 2014, 08:43:45 AM

If somebody can, please provide a screen shot of that error!

lukey25

member

Activity: 91

Merit: 10

Quote from: englishbad on August 11, 2014, 08:43:55 AM

Quote from: lukey25 on August 11, 2014, 08:42:26 AM

As I said I had this error, too

but after the second try it worked well Grin

so try again, if this idea did nit come into your mind so far

I have entered three times, but they are all the same result

then I have no idea Undecided

3x2

legendary

Activity: 1526

Merit: 1004

Quote from: englishbad on August 11, 2014, 08:42:42 AM

Quote from: mladen00 on August 11, 2014, 08:39:43 AM

error;
Uncaught node.js Error

Me too！What things？

Try again, working for me now

englishbad

sr. member

Activity: 364

Merit: 250

Quote from: lukey25 on August 11, 2014, 08:42:26 AM

As I said I had this error, too

but after the second try it worked well Grin

so try again, if this idea did nit come into your mind so far

I have entered three times, but they are all the same result

koop4u

sr. member

Activity: 308

Merit: 250

If somebody can, please provide a screen shot of that error!

englishbad

sr. member

Activity: 364

Merit: 250

Quote from: mladen00 on August 11, 2014, 08:39:43 AM

error;
Uncaught node.js Error

Error: Previous block id doesn't match
at Function.BlockchainProcessor.pushBlock (eval at (eval at (C:\Users\MALIMA~1\AppData\Local\Temp\nw5384_14682\index.js)), :1:49868)
at eval (eval at (eval at (C:\Users\MALIMA~1\AppData\Local\Temp\nw5384_14682\index.js)), :1:106879)
at eval (eval at (eval at (C:\Users\MALIMA~1\AppData\Local\Temp\nw5384_14682\index.js)), :1:58639)
at callback (C:\Users\MALIMA~1\AppData\Local\Temp\nw5384_14682\node_modules\nedb\lib\executor.js:26:17)
at Cursor.eval [as execFn] (C:\Users\MALIMA~1\AppData\Local\Temp\nw5384_14682\node_modules\nedb\lib\datastore.js:389:12)
at Cursor._exec (C:\Users\MALIMA~1\AppData\Local\Temp\nw5384_14682\node_modules\nedb\lib\cursor.js:113:17)
at eval (C:\Users\MALIMA~1\AppData\Local\Temp\nw5384_14682\node_modules\nedb\lib\executor.js:36:13)
at Object.q.process [as _onImmediate] (C:\Users\MALIMA~1\AppData\Local\Temp\nw5384_14682\node_modules\nedb\node_modules\async\lib\async.js:731:21)
at processImmediate [as _immediateCallback] (timers.js:330:15)

Me too！What things？

lukey25

member

Activity: 91

Merit: 10

As I said I had this error, too

but after the second try it worked well Grin

so try again, if this idea did nit come into your mind so far

u5sos

member

Activity: 108

Merit: 10

It works, nice work dev.

UPD: some problem

3x2

legendary

Activity: 1526

Merit: 1004

Quote from: mladen00 on August 11, 2014, 08:39:43 AM

error;
Uncaught node.js Error

Same thing happening to me.

mladen00

legendary

Activity: 2124

Merit: 1013

K-ing®

error;
Uncaught node.js Error

Error: Previous block id doesn't match
at Function.BlockchainProcessor.pushBlock (eval at (eval at (C:\Users\MALIMA~1\AppData\Local\Temp\nw5384_14682\index.js)), :1:49868)
at eval (eval at (eval at (C:\Users\MALIMA~1\AppData\Local\Temp\nw5384_14682\index.js)), :1:106879)
at eval (eval at (eval at (C:\Users\MALIMA~1\AppData\Local\Temp\nw5384_14682\index.js)), :1:58639)
at callback (C:\Users\MALIMA~1\AppData\Local\Temp\nw5384_14682\node_modules\nedb\lib\executor.js:26:17)
at Cursor.eval [as execFn] (C:\Users\MALIMA~1\AppData\Local\Temp\nw5384_14682\node_modules\nedb\lib\datastore.js:389:12)
at Cursor._exec (C:\Users\MALIMA~1\AppData\Local\Temp\nw5384_14682\node_modules\nedb\lib\cursor.js:113:17)
at eval (C:\Users\MALIMA~1\AppData\Local\Temp\nw5384_14682\node_modules\nedb\lib\executor.js:36:13)
at Object.q.process [as _onImmediate] (C:\Users\MALIMA~1\AppData\Local\Temp\nw5384_14682\node_modules\nedb\node_modules\async\lib\async.js:731:21)
at processImmediate [as _immediateCallback] (timers.js:330:15)

lukey25

member

Activity: 91

Merit: 10

try again

I also had an error..

after the second try it worked

3x2

legendary

Activity: 1526

Merit: 1004

Uncaught node.js Error i am getting this error

u5sos

member

Activity: 108

Merit: 10

Great, nodecoin.com down now

Topic: Closed Thread - page 393. (Read 677686 times)