Topic: [XCR] Crypti | Dapps | Sidechains | Dapp Store | OPEN SOURCE | 100% own code | DPoS - page 349. (Read 804713 times)
August 23, 2014, 03:42:55 PM
https://wallet.crypti.me/ - Down again....
August 23, 2014, 03:40:45 PM
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
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
August 23, 2014, 03:40:28 PM
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?
Maybe we can use the http://cryptitalk.com bug report for that?
August 23, 2014, 03:37:19 PM
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..
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"
Code:
sudo rebuild
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?
August 23, 2014, 03:34:40 PM
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..
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"
Code:
sudo rebuild
So you're saying I should rebuild the droplet?
In your digital oceans dashboard
Destroy
then
Rebuild
Rebuild from your image or original
August 23, 2014, 03:23:52 PM
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
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
August 23, 2014, 03:20:48 PM
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
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
August 23, 2014, 03:12:11 PM
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..
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"
Code:
sudo rebuild
So you're saying I should rebuild the droplet?
August 23, 2014, 03:07:00 PM
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..
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"
August 23, 2014, 02:59:31 PM
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..
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..
August 23, 2014, 02:48:52 PM
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
August 23, 2014, 02:42:40 PM
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
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.
August 23, 2014, 02:36:18 PM
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
Code:
dir
I'm restoring my initial backup and starting afresh. I didn't create a backup before I enabled forging, so I have to start over. Once I create a backup with everything working before forging is enabled I'll give it another try
If your going to start fresh then follow these steps at #4
Upload Crypti archive to server.
Code:
wget http://downloads.crypti.me/crypti-node/0.1.x/crypti-linux-0.1.3.zip
Unzip it:
Code:
sudo apt-get install unzip
Code:
unzip crypti-linux-0.1.3.zip
Go to crypti folder:
Code:
cd 0.1.3
Run command:
Code:
npm install
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
August 23, 2014, 02:30:48 PM
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
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
August 23, 2014, 02:22:51 PM
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
Code:
dir
I'm restoring my initial backup and starting afresh. I didn't create a backup before I enabled forging, so I have to start over. Once I create a backup with everything working before forging is enabled I'll give it another try
August 23, 2014, 02:06:15 PM
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
Code:
dir
August 23, 2014, 02:02:03 PM
Da fAck with Cryptsy, how long we have to wait? This is unprofessional and embarrassing for an exchange!
SHAME ON YOU CRYPTSY!
SHAME ON YOU CRYPTSY!
I actually think cryptsy has been very fast and is working hard on their end. The issues for many stem from Bter I think or their own personal wallet not syncing to the current version. Our Dev team is working with all parties to ensure we get everyone on the same version and the once syncs are complete everyones balances will reflect what they should.
GreXX could you at least shorten me the info about forging. How many Crypti should I have into wallet to forget something daily? It would be very helpful.
The wallet associated with the passphrase you are sing for forging must have 1000 Crypti for forging to initiate.
I have more than that on my online wallet, more than 24 hours, and still nothing forged.
You need to manually enable forging.
Sorry but how? And where this is explained?
Check here : https://github.com/crypti/crypti-docs/blob/master/install.md#6-enable-forging
So on online wallet I will not forge at all yes?
Correct
OK so, clear answer at last. Thanks.
August 23, 2014, 01:59:52 PM
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
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
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
August 23, 2014, 01:59:32 PM
Da fAck with Cryptsy, how long we have to wait? This is unprofessional and embarrassing for an exchange!
SHAME ON YOU CRYPTSY!
SHAME ON YOU CRYPTSY!
I actually think cryptsy has been very fast and is working hard on their end. The issues for many stem from Bter I think or their own personal wallet not syncing to the current version. Our Dev team is working with all parties to ensure we get everyone on the same version and the once syncs are complete everyones balances will reflect what they should.
GreXX could you at least shorten me the info about forging. How many Crypti should I have into wallet to forget something daily? It would be very helpful.
The wallet associated with the passphrase you are sing for forging must have 1000 Crypti for forging to initiate.
I have more than that on my online wallet, more than 24 hours, and still nothing forged.
You need to manually enable forging.
Sorry but how? And where this is explained?
Check here : https://github.com/crypti/crypti-docs/blob/master/install.md#6-enable-forging
So on online wallet I will not forge at all yes?
Correct
August 23, 2014, 01:58:44 PM
Da fAck with Cryptsy, how long we have to wait? This is unprofessional and embarrassing for an exchange!
SHAME ON YOU CRYPTSY!
SHAME ON YOU CRYPTSY!
I actually think cryptsy has been very fast and is working hard on their end. The issues for many stem from Bter I think or their own personal wallet not syncing to the current version. Our Dev team is working with all parties to ensure we get everyone on the same version and the once syncs are complete everyones balances will reflect what they should.
GreXX could you at least shorten me the info about forging. How many Crypti should I have into wallet to forget something daily? It would be very helpful.
The wallet associated with the passphrase you are sing for forging must have 1000 Crypti for forging to initiate.
I have more than that on my online wallet, more than 24 hours, and still nothing forged.
You need to manually enable forging.
Sorry but how? And where this is explained?
Check here : https://github.com/crypti/crypti-docs/blob/master/install.md#6-enable-forging
So on online wallet I will not forge at all yes?
Jump to: