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

[informer]

Dev's any sign of getting your BTC? To get things flying....

http://blog.crypti.me/crypti-foundation-btc-funds/

informer

[starik69]

If you trying to launch the wallet before it is fully synchronized it will cause the Node to restart the sync process...

This is not true. 
 I can see blockchain syncronizing from scratch in browser on another node. 
Not 20 minutes, 2 hours and no blockchain. 

[Bigcabrito]

{"level":"warn","message":"Request already added: 4481046574929300723/6127372741261621508C","timestamp":"2014-08-25T04:53:30.540Z"}
{"level":"info","message":"Process blocks from peer: 72.95.14.201","timestamp":"2014-08-25T04:53:31.541Z"}
{"level":"info","message":"Process requests...","timestamp":"2014-08-25T04:53:32.975Z"}
{"level":"info","message":"Get requests from 107.170.126.199","timestamp":"2014-08-25T04:53:32.975Z"}
{"level":"info","message":"Process unconfirmed transactions...","timestamp":"2014-08-25T04:53:32.975Z"}

These are my last lines from the cat logs.log. Now I am trying to access my wallet as per "After it starts,open: http://serverip:6040/ <--- Replace "serverip" with Your Public IP" but It keeps getting stuck on Unable to connect.

[informer]

{"level":"warn","message":"Request already added: 4481046574929300723/6127372741261621508C","timestamp":"2014-08-25T04:53:30.540Z"}
{"level":"info","message":"Process blocks from peer: 72.95.14.201","timestamp":"2014-08-25T04:53:31.541Z"}
{"level":"info","message":"Process requests...","timestamp":"2014-08-25T04:53:32.975Z"}
{"level":"info","message":"Get requests from 107.170.126.199","timestamp":"2014-08-25T04:53:32.975Z"}
{"level":"info","message":"Process unconfirmed transactions...","timestamp":"2014-08-25T04:53:32.975Z"}

These are my last lines from the cas logs.log. Now I am trying to access my wallet as per "After it starts,open: http://serverip:6040/ <--- Replace "serverip" with Your Public IP" but It keeps getting stuck on Unable to connect.

What's your

forever list

uptime? It usually takes me about twenty minutes to start forging but it comes up within two before I change my secrePhrase.

[Bigcabrito]

I started the whole process yesterday but could not make it run so I just went to bed and now I'm back at it. Must be 12hr's+/

What's your

forever list

uptime? How long have you been up?

I'm not sure what you mean by forever list. This is my first install of Ubuntu/Linux, and it was done for the sole purpose of putting up a node and forging Crypti.

[informer]

If you trying to launch the wallet before it is fully synchronized it will cause the Node to restart the sync process...

This is not true.  
 I can see blockchain syncronizing from scratch in browser on another node.  
Not 20 minutes, 2 hours and no blockchain.  

I'll tell you something that changed things up for me that aren't quite clear in the instruction is adding the legacy properly. In step 1

Code:

On debian repositories must be found, on ubuntu if repositories not found:

Use this tutorial to add nodejs ppa repo:

https://launchpad.net/~chris-lea/+archive/ubuntu/node.js-legacy

Again update your system repositories and install nodejs:

It took me a second to read through that page and realize you have to:

sudo apt-add-repository ppa:chris-lea/node.js-legacy

Then when you run sudo apt-get you'll see the ppa node.js-legacy in the list.

[Sparky_eMunie]

The docker install instructions are much easier to follow if you are having trouble with the manual setup.

Docker install is more awfull 
When i run Start it now says that docker daemon is not running (was somehow running and installed Crypti) 

Boot2Docker will not install correctly in many cases if you have already VMWare on your system, as it installs Oracle Virtual Box in the background, and VMWare + Virtual Box network components often do not like each other. In more detail, if you have VMNet on Slot #8 with VMWare, Virtual Box will not install giving a meaningless error. Boot2Docker does not check if Virtual Box installed successfully or not.

[Sparky_eMunie]

Why is this coin so under valued? Less than 2,000 BTC?

It's not heavily developed yet. As you can read from the past few pages there are alot of people having trouble with the Linux install.

There are no problems right now. Everything is working fine and smoothly.

This is not true, see my problem with 0.1.5 and 0.1.5b. Crypti does not work at all on Ubuntu 14.04 desktop with nothing else installed but Crypti + the components it needs:

https://bitcointalk.org/index.php?topic=654463.msg8528786#msg8528786

[informer]

I'm not sure what you mean by forever list. This is my first install of Ubuntu/Linux, and it was done for the sole purpose of putting up a node and forging Crypti.

When you run 'forever list' it will tell you how long its been up.



In this image you can see mine has been up 4 hours, 29 minutes, and 20 seconds.

[samsmith16]

If you trying to launch the wallet before it is fully synchronized it will cause the Node to restart the sync process...

This is not true. 
 I can see blockchain syncronizing from scratch in browser on another node. 
Not 20 minutes, 2 hours and no blockchain. 

Docker will launch empty and sync
 However this was in reference to a Forging node on AWS

[atleticofa]

{"level":"warn","message":"Request already added: 4481046574929300723/6127372741261621508C","timestamp":"2014-08-25T04:53:30.540Z"}
{"level":"info","message":"Process blocks from peer: 72.95.14.201","timestamp":"2014-08-25T04:53:31.541Z"}
{"level":"info","message":"Process requests...","timestamp":"2014-08-25T04:53:32.975Z"}
{"level":"info","message":"Get requests from 107.170.126.199","timestamp":"2014-08-25T04:53:32.975Z"}
{"level":"info","message":"Process unconfirmed transactions...","timestamp":"2014-08-25T04:53:32.975Z"}

These are my last lines from the cat logs.log. Now I am trying to access my wallet as per "After it starts,open: http://serverip:6040/ <--- Replace "serverip" with Your Public IP" but It keeps getting stuck on Unable to connect.

What about your firewall or security settings?

You have to allow TCP incomming connections to port 6040

[tk808]

Crypti Review + Score (3.0/5 Great) now available on Coins Source


http://www.coinssource.com/crypto-coins/crypti/

[GreXX]

Crypti Review + Score (3.0/5 Great) now available on Coins Source


http://www.coinssource.com/crypto-coins/crypti/

Thanks TK! Great article btw. Objective and well written!

[starik69]

I'll tell you something that changed things up for me that aren't quite clear in the instruction is adding the legacy properly. In step 1

For me everything is installing without adding that repository 

Oh, blockchain arrived, seems i am forging

[Sparky_eMunie]

{"level":"warn","message":"Request already added: 4481046574929300723/6127372741261621508C","timestamp":"2014-08-25T04:53:30.540Z"}
{"level":"info","message":"Process blocks from peer: 72.95.14.201","timestamp":"2014-08-25T04:53:31.541Z"}
{"level":"info","message":"Process requests...","timestamp":"2014-08-25T04:53:32.975Z"}
{"level":"info","message":"Get requests from 107.170.126.199","timestamp":"2014-08-25T04:53:32.975Z"}
{"level":"info","message":"Process unconfirmed transactions...","timestamp":"2014-08-25T04:53:32.975Z"}

These are my last lines from the cat logs.log. Now I am trying to access my wallet as per "After it starts,open: http://serverip:6040/ <--- Replace "serverip" with Your Public IP" but It keeps getting stuck on Unable to connect.

What about your firewall or security settings?

You have to allow TCP incomming connections to port 6040

I don't think it's related to the firewall, as the client is receiving data.

[crypti]

Why did the block time changed from 61 seconds to 120 seconds?

It can be changed sometimes. Need more forgers with good sync.

[crypti]

{"level":"warn","message":"Request already added: 4481046574929300723/6127372741261621508C","timestamp":"2014-08-25T04:53:30.540Z"}
{"level":"info","message":"Process blocks from peer: 72.95.14.201","timestamp":"2014-08-25T04:53:31.541Z"}
{"level":"info","message":"Process requests...","timestamp":"2014-08-25T04:53:32.975Z"}
{"level":"info","message":"Get requests from 107.170.126.199","timestamp":"2014-08-25T04:53:32.975Z"}
{"level":"info","message":"Process unconfirmed transactions...","timestamp":"2014-08-25T04:53:32.975Z"}

These are my last lines from the cat logs.log. Now I am trying to access my wallet as per "After it starts,open: http://serverip:6040/ <--- Replace "serverip" with Your Public IP" but It keeps getting stuck on Unable to connect.

What about your firewall or security settings?

You have to allow TCP incomming connections to port 6040

I don't think it's related to the firewall, as the client is receiving data.

If it AWS/Google cloud you need to add rule in firewall for 6040 port.

[crypti]

Why is this coin so under valued? Less than 2,000 BTC?

It's not heavily developed yet. As you can read from the past few pages there are alot of people having trouble with the Linux install.

There are no problems right now. Everything is working fine and smoothly.

This is not true, see my problem with 0.1.5 and 0.1.5b. Crypti does not work at all on Ubuntu 14.04 desktop with nothing else installed but Crypti + the components it needs:

https://bitcointalk.org/index.php?topic=654463.msg8528786#msg8528786

You stopped app on read/write db operation. So blockchain.db was crashed. Just remove it and run again.
I will found solution for this problem in next version.

[samsmith16]

{"level":"warn","message":"Request already added: 4481046574929300723/6127372741261621508C","timestamp":"2014-08-25T04:53:30.540Z"}
{"level":"info","message":"Process blocks from peer: 72.95.14.201","timestamp":"2014-08-25T04:53:31.541Z"}
{"level":"info","message":"Process requests...","timestamp":"2014-08-25T04:53:32.975Z"}
{"level":"info","message":"Get requests from 107.170.126.199","timestamp":"2014-08-25T04:53:32.975Z"}
{"level":"info","message":"Process unconfirmed transactions...","timestamp":"2014-08-25T04:53:32.975Z"}

These are my last lines from the cat logs.log. Now I am trying to access my wallet as per "After it starts,open: http://serverip:6040/ <--- Replace "serverip" with Your Public IP" but It keeps getting stuck on Unable to connect.

What about your firewall or security settings?

You have to allow TCP incomming connections to port 6040

I don't think it's related to the firewall, as the client is receiving data.

If it AWS/Google cloud you need to add rule in firewall for 6040 port.

right if you followed the guide https://github.com/crypti/crypti-docs/blob/master/AWSwindows.md you have the inbound rule already set...

However if you already have your instance set up and need to add the Rule...

Go to your console
https://console.aws.amazon.com/ec2/v2/home

Then navigate to the SecurityGroups all the way to the right..

Then click the launch-wizard-1

Once your in the Security Groups you will see tabs in the lower part of the screen Select Inbound

Then click Edit
Then click Add

Add a Custom TPC rule

Port range is 6040
Source is Anywhere

Save it and you should be good



 

[GreXX]

Question...

Do we have anyone here who could do a Chinese Translation? I will personally pay the bounty if we can get a Chinese translation in the next 2-3 days.

What is a good bounty for this? 1000 Crypti?

If you want to help with translations, I am posting a Bounty thread here: http://cryptitalk.com/index.php?topic=112.msg253#msg253

For now, I will personally pay the ones listed for translations to get the ball rolling.