[XCR] Crypti | Dapps | Sidechains | Dapp Store | OPEN SOURCE | 100% own code | DPoS

[Wulfcastle]

Yep that's how I'm trying to load my wallet, but nothing's loading

Well I would ask you to PM your screen shoot of the config.json but it now has your passphrase in it... So I would suggest you open up config.json again and make sure you haven't deleted a " or something like that... I have changed my config.json many times and never crashed my AWS

What does your root dir look like?

Code:

cd

then

Code:

dir

Try this

Code:

forever stop app.js

Then

Code:

cd 

Then

 

Code:

npm install https://github.com/dazoe/ed25519/tarball/master

Then

Code:

cd node_modules

Then

Code:

cd ed25519

And run:

   

Code:

node-gyp configure

And then:

   

Code:

node-gyp build

After it builds, go back to crypti folder and run the installation again:

Code:

cd

Code:

cd 0.1.3

Code:

   npm install

Install node.js process manager:

   

Code:

sudo npm install -g forever

Shit I just finished installing, would it be possible to still do this process? i.e. can I run


node-gyp configure   

node-gyp build

In case the ed25519 didn't build properly.

[1714726124]

1714726124

[1714726124]

1714726124

[1714726124]

1714726124

[samsmith16]

Shit I just finished installing, would it be possible to still do this process? i.e. can I run


node-gyp configure   

node-gyp build

In case the ed25519 didn't build properly.

Yes

Code:

cd 

Then

 

Code:

npm install https://github.com/dazoe/ed25519/tarball/master

Then

Code:

cd node_modules

Then

Code:

cd ed25519

And run:

   

Code:

node-gyp configure

And then:

   

Code:

node-gyp build

After it builds, go back to crypti folder and run the installation again:

Code:

cd

Code:

cd 0.1.3

Code:

   npm install

Install node.js process manager:

   

Code:

sudo npm install -g forever

[Wulfcastle]

There must be something wrong with my droplet configuration.

After I took a snapshot as a backup, (I switched the droplet off first - sudo poweroff), I rebooted the droplet, without changing anything and now nothing seems to work. It was working perfectly before I switched the droplet off took the snapshot and restarted, now nothing.. 

[samsmith16]

There must be something wrong with my droplet configuration.

After I took a snapshot as a backup, (I switched the droplet off first - sudo poweroff), I rebooted the droplet, without changing anything and now nothing seems to work. It was working perfectly before I switched the droplet off took the snapshot and restarted, now nothing.. 

"Rebuild"

[Wulfcastle]

There must be something wrong with my droplet configuration.

After I took a snapshot as a backup, (I switched the droplet off first - sudo poweroff), I rebooted the droplet, without changing anything and now nothing seems to work. It was working perfectly before I switched the droplet off took the snapshot and restarted, now nothing..  

"Rebuild"

Do I just type

Code:

sudo rebuild

Sorry I'm a total noob at working with linux consoles.

EDIT : When I start my droplet it says there is 1 zombie process - I'm guessing that's Crypti?[/s]

So you're saying I should rebuild the droplet?

[atleticofa]

Try this... I'm forging right now off my AWS but it's just that I'm on 0.1.3... we all just have to wait for them to release 0.1.4 so we are forging on the right fork... They are testing it now..

Code:

forever stop app.js

Then

Code:

forever start app.js

Still not working.

Could this be a problem :

what does this show?

Code:

forever list 

This here :



It seems to be running though.

Right bc Node.js is not a loop... and it ran the default ms

now how are you trying to load your wallet?

http://serverip:6040/ <- replace "serverip" with your Public IP

then enter your passphrase in the wallet

Yep that's how I'm trying to load my wallet, but nothing's loading

Did you open the port 6040 on your server? You have to add permission for TCP incomming connections to port 6040

[Wulfcastle]

Try this... I'm forging right now off my AWS but it's just that I'm on 0.1.3... we all just have to wait for them to release 0.1.4 so we are forging on the right fork... They are testing it now..

Code:

forever stop app.js

Then

Code:

forever start app.js

Still not working.

Could this be a problem :

what does this show?

Code:

forever list 

This here :



It seems to be running though.

Right bc Node.js is not a loop... and it ran the default ms

now how are you trying to load your wallet?

http://serverip:6040/ <- replace "serverip" with your Public IP

then enter your passphrase in the wallet

Yep that's how I'm trying to load my wallet, but nothing's loading

Did you open the port 6040 on your server? You have to add permission for TCP incomming connections to port 6040

No it worked perfectly up until I edited the config.json file. That's when I couldn't access it anymore

[samsmith16]

There must be something wrong with my droplet configuration.

After I took a snapshot as a backup, (I switched the droplet off first - sudo poweroff), I rebooted the droplet, without changing anything and now nothing seems to work. It was working perfectly before I switched the droplet off took the snapshot and restarted, now nothing..  

"Rebuild"

Do I just type

Code:

sudo rebuild

Sorry I'm a total noob at working with linux consoles.

EDIT : When I start my droplet it says there is 1 zombie process - I'm guessing that's Crypti?[/s]

So you're saying I should rebuild the droplet?

In your digital oceans dashboard

Destroy
then
Rebuild
Rebuild from your image or original

[Wulfcastle]

There must be something wrong with my droplet configuration.

After I took a snapshot as a backup, (I switched the droplet off first - sudo poweroff), I rebooted the droplet, without changing anything and now nothing seems to work. It was working perfectly before I switched the droplet off took the snapshot and restarted, now nothing..  

"Rebuild"

Do I just type

Code:

sudo rebuild

Sorry I'm a total noob at working with linux consoles.

EDIT : When I start my droplet it says there is 1 zombie process - I'm guessing that's Crypti?[/s]

So you're saying I should rebuild the droplet?

In your digital oceans dashboard

Destroy
then
Rebuild
Rebuild from your image or original

So basically start afresh again. Is there any reason, why the Crypti process would stop working entirely after rebooting the droplet?

[hobogo]

Should a support oriented comments should be on another tread/board so no clutter here?
Maybe we can use the http://cryptitalk.com bug report for that?

[thefunkybits]

Hello team! I have been assigned to do an article on Crypti XCR

If anyone in the PR department wants to contact me I'd love to talk further  

ps. I'm also looking for a Crypti block explorer

[Wulfcastle]

https://wallet.crypti.me/ - Down again....

[samsmith16]

There must be something wrong with my droplet configuration.

After I took a snapshot as a backup, (I switched the droplet off first - sudo poweroff), I rebooted the droplet, without changing anything and now nothing seems to work. It was working perfectly before I switched the droplet off took the snapshot and restarted, now nothing..  

"Rebuild"

Do I just type

Code:

sudo rebuild

Sorry I'm a total noob at working with linux consoles.

EDIT : When I start my droplet it says there is 1 zombie process - I'm guessing that's Crypti?[/s]

So you're saying I should rebuild the droplet?

In your digital oceans dashboard

Destroy
then
Rebuild
Rebuild from your image or original

So basically start afresh again. Is there any reason, why the Crypti process would stop working entirely after rebooting the droplet?

Lets PM.. I wanted this open incase you had problems others had as well... But now it looks like you have an isolated issue

[atleticofa]

https://wallet.crypti.me/ - Down again....

Not for me...

[atleticofa]

I can't understand why people are selling this coin so cheap.

[hobogo]

https://wallet.crypti.me/ - Down again....

Not for me...

not for me either

[elephantas1]

i withdrew 800 xcr from bter to cryptsy and its not appearing in balance what i should do? should i just wait?

[hobogo]

I can't understand why people are selling this coin so cheap.

Me too. I really like how the devs handling things so far, and this project got a huge potential.
It is expected to have some problems both in the beginning of the project and trough out its life cycle. how they handle those problems is important, and I saw some amazing things so far.
I think that the sellers haven't seen tec projects before..
Thou I'm only holding coins I feel like I'm a supporter of this project and that I'm being part of it. I would be ashamed to think about my capital gains at this point even if I though I could make such by trading.

[poornamelessme]

I can't understand why people are selling this coin so cheap.

Me too. I really like how the devs handling things so far, and this project got a huge potential.
It is expected to have some problems both in the beginning of the project and trough out its life cycle. how they handle those problems is important, and I saw some amazing things so far.
I think that the sellers haven't seen tec projects before..
Thou I'm only holding coins I feel like I'm a supporter of this project and that I'm being part of it. I would be ashamed to think about my capital gains at this point even if I though I could make such by trading.

ICO people cashing out for immediate profits. Although if they truly wanted to do that, they should have done it yesterday when it was 3K+.

Slow growth is better anyway. I wouldn't mind another minor dip actually, as I have a small buy order still waiting to get filled.

[digitron]

i withdrew 800 xcr from bter to cryptsy and its not appearing in balance what i should do? should i just wait?

Same here, I sent some to Cryptsy and some to Polo, and no balance there after 12 / 36 hours. Opened a ticket with Polo, and with bter, but no reply... WTF?