Topic: [ANN] Nxt :: descendant of Bitcoin - page 64. (Read 384036 times)
Using a VPS for this is a TERRIBLE IDEA. Do NOT do it. Run Nxt locally.
I connected to remote host with PuTTy and did this
[root@Nxt ~]# ssh -L localhost:7885:localhost:7875 192.161.175.142
The authenticity of host '192.161.175.142 (192.161.175.142)' can't be established.
RSA key fingerprint is xxxxxxxx
Are you sure you want to continue connecting (yes/no)? y
Please type 'yes' or 'no': yes
Warning: Permanently added '192.161.175.142' (RSA) to the list of known hosts.
[email protected]'s password:
Last login: Mon Nov 25 17:40:31 2013 from nnnnnnnn
[root@Nxt ~]#
Try connecting to http://localhost:7885/ but unsuccessful.
What did I do wrong?
Edit: local machine is windows
Wait, you don't run ssh on the remote machine... you run ssh on your local machine. Looks like you just connected the remote machine to itself
Since you are on windows and using PuTTY instead of ssh, use the PuTTY configuration under Connection/SSH/Tunnels... to define the ports to be forwarded. But I would need to figure it out too what exactly to enter where, it has been many years since I used PuTTY and windows...
lol! await your advise on PuTTy config... or any other method for windows. Thx
Edit: Also, pls help how to unconnect the remote machine to itself
Figured that out. Thanks.
I suggest other users with VPS should do the same. Here is an excellent guide to help you securely connect to your VPS from browser
http://collaboradev.com/2011/08/03/browsing-the-web-through-an-ssh-tunnel-putty-firefox/
I've had my account unlocked for over 24 hours now, but no transaction indicating any earnings from mining. How will I know if i get any earnings? Should I expect some after 24 hours?
You need to wait for 1440 blocks to be solved on top of your first receipt before mining will begin.
eid
Ok,thanks! 1440 is the magic number then
Do mining earnings appear as a deposit transaction? I've had my account unlocked for over 24 hours now, but no transaction indicating any earnings from mining. How will I know if i get any earnings? Should I expect some after 24 hours?
You need to wait for 1440 blocks to be solved on top of your first receipt before mining will begin.
eid
Where does it say "You will mine the next block in X time"? I don't see that anywhere.
Account has to be a day old (I think) and have coins for mining. But, the mining reward = ALL FEES in the block mined. Not much fees right now as more blocks have no transactions in them at this state of the game. This will be a few weeks out before the new functionality comes out.
Where does it say "You will mine the next block in X time"? I don't see that anywhere.
Uhhhhh did NXT just get pwned? I see a recent transaction of 1billion coins and all other transactions are now orphaned....
edit: no, i'm retarded, looks like it got bumped to a bad chain. deleted all the files and its working again.
edit: no, i'm retarded, looks like it got bumped to a bad chain. deleted all the files and its working again.
I've had my account unlocked for over 24 hours now, but no transaction indicating any earnings from mining. How will I know if i get any earnings? Should I expect some after 24 hours?
I connected to remote host with PuTTy and did this
[root@Nxt ~]# ssh -L localhost:7885:localhost:7875 192.161.175.142
The authenticity of host '192.161.175.142 (192.161.175.142)' can't be established.
RSA key fingerprint is xxxxxxxx
Are you sure you want to continue connecting (yes/no)? y
Please type 'yes' or 'no': yes
Warning: Permanently added '192.161.175.142' (RSA) to the list of known hosts.
[email protected]'s password:
Last login: Mon Nov 25 17:40:31 2013 from nnnnnnnn
[root@Nxt ~]#
Try connecting to http://localhost:7885/ but unsuccessful.
What did I do wrong?
Edit: local machine is windows
Wait, you don't run ssh on the remote machine... you run ssh on your local machine. Looks like you just connected the remote machine to itself
Since you are on windows and using PuTTY instead of ssh, use the PuTTY configuration under Connection/SSH/Tunnels... to define the ports to be forwarded. But I would need to figure it out too what exactly to enter where, it has been many years since I used PuTTY and windows...
lol! await your advise on PuTTy config... or any other method for windows. Thx
Edit: Also, pls help how to unconnect the remote machine to itself
I connected to remote host with PuTTy and did this
[root@Nxt ~]# ssh -L localhost:7885:localhost:7875 192.161.175.142
The authenticity of host '192.161.175.142 (192.161.175.142)' can't be established.
RSA key fingerprint is xxxxxxxx
Are you sure you want to continue connecting (yes/no)? y
Please type 'yes' or 'no': yes
Warning: Permanently added '192.161.175.142' (RSA) to the list of known hosts.
[email protected]'s password:
Last login: Mon Nov 25 17:40:31 2013 from nnnnnnnn
[root@Nxt ~]#
Try connecting to http://localhost:7885/ but unsuccessful.
What did I do wrong?
Edit: local machine is windows
Wait, you don't run ssh on the remote machine... you run ssh on your local machine. Looks like you just connected the remote machine to itself
Since you are on windows and using PuTTY instead of ssh, use the PuTTY configuration under Connection/SSH/Tunnels... to define the ports to be forwarded. But I would need to figure it out too what exactly to enter where, it has been many years since I used PuTTY and windows...
How many peers does everyone see atm?
I see 11 (one is red flag 5.135.165.137)
I see 11 (one is red flag 5.135.165.137)
same for me 11, but ny 5.135.x.x peer isnt in red. then i could still not be authorized. i jhave no idea what im doing. why are my 2 transactions the only 2 still unauthorized?
I have finally up & running my VPS client @ http://94.102.63.115:7875/
Does that mean that other users can connect there with their accounts? If so I would be glad to host them (and a good opportunity to test if everything is ok)!
Does that mean that other users can connect there with their accounts? If so I would be glad to host them (and a good opportunity to test if everything is ok)!
They could connect, but please be aware passwords are submitted in clear text - better use accounts holding only small amounts.
Here is a security tip for those running Nxt on a remote server:
The Nxt server uses plain http, not https. So if you a running a VPS server at http://my-server.example.com:7875, every time you unlock your account there is a risk that the password will be captured in transit. There is another annoyance in such a setup: since you are not running on localhost, the Nxt interface disables access to certain features, e.g. you cannot remove peers from the blacklist / active list by clicking on the trash icon. But as long as you have ssh access to the remote server, there is a simple solution. Just use ssh tunneling:
Code:
ssh -L localhost:7885:localhost:7875 my-server.example.com
The above command will establish an ssh tunnel between your machine (localhost) and the remove server where Nxt is running, my-server.example.com, from port 7885 on localhost to port 7875 on the remote host. Then, instead of going to http://my-server.example.com:7875 , open http://localhost:7885 , and you will be connected to the remote Nxt instance. Except, your connection will be encrypted so nobody can listen to it. And, from the point of view of the remote Nxt process, your connection is coming from localhost, so editing the peers lists will be enabled.
Once you make sure it is working, the next time you invoke ssh you can just put it in the background, and also use the -N flag so that it does not open a terminal connection (unless you need it):
Code:
ssh -L localhost:7885:localhost:7875 -N my-server.example.com &
(Note: I use port 7885 on localhost, in case 7875 is already used by a local Nxt instance. But any available port can be used instead.)
Obviously, in your case you can securely access your VPS server over this ssh tunnel, but other users are still at risk - and you can't give everyone ssh access.
Thank you very much. This is exactly what I've been waiting for. Will try it
I connected to remote host with PuTTy and did this
[root@Nxt ~]# ssh -L localhost:7885:localhost:7875 192.161.175.142
The authenticity of host '192.161.175.142 (192.161.175.142)' can't be established.
RSA key fingerprint is xxxxxxxx
Are you sure you want to continue connecting (yes/no)? y
Please type 'yes' or 'no': yes
Warning: Permanently added '192.161.175.142' (RSA) to the list of known hosts.
[email protected]'s password:
Last login: Mon Nov 25 17:40:31 2013 from nnnnnnnn
[root@Nxt ~]#
Try connecting to http://localhost:7885/ but unsuccessful.
What did I do wrong?
Edit: local machine is windows
How many peers does everyone see atm?
I see 11 (one is red flag 5.135.165.137)
I see 11 (one is red flag 5.135.165.137)
Well all I was saying that a "dev team" would be faster then just one dev alone...
This is not always true, it takes time for a new developer to get up to speed with an unfamiliar project. And a big team of developers often wastes time arguing back and forth how things should be done, while a single developer will just do it as he seems fit, and get it working.As a Java developer myself (and Nxt stakeholder), I would love to start helping with Nxt. But I understand the need to keep the source closed, so I can wait. Finally, there is a innovative new coin done in Java, and not just another BTC clone.
I expect we will have to wait for the source, but does anyone know how consensus on the current time is reached in NXT? The mining mechanism seems to rely on everyone being in agreement (as that sets the "difficulty").
Thanks.
Thanks.
I have finally up & running my VPS client @ http://94.102.63.115:7875/
Does that mean that other users can connect there with their accounts? If so I would be glad to host them (and a good opportunity to test if everything is ok)!
Does that mean that other users can connect there with their accounts? If so I would be glad to host them (and a good opportunity to test if everything is ok)!
They could connect, but please be aware passwords are submitted in clear text - better use accounts holding only small amounts.
Here is a security tip for those running Nxt on a remote server:
The Nxt server uses plain http, not https. So if you a running a VPS server at http://my-server.example.com:7875, every time you unlock your account there is a risk that the password will be captured in transit. There is another annoyance in such a setup: since you are not running on localhost, the Nxt interface disables access to certain features, e.g. you cannot remove peers from the blacklist / active list by clicking on the trash icon. But as long as you have ssh access to the remote server, there is a simple solution. Just use ssh tunneling:
Code:
ssh -L localhost:7885:localhost:7875 my-server.example.com
The above command will establish an ssh tunnel between your machine (localhost) and the remove server where Nxt is running, my-server.example.com, from port 7885 on localhost to port 7875 on the remote host. Then, instead of going to http://my-server.example.com:7875 , open http://localhost:7885 , and you will be connected to the remote Nxt instance. Except, your connection will be encrypted so nobody can listen to it. And, from the point of view of the remote Nxt process, your connection is coming from localhost, so editing the peers lists will be enabled.
Once you make sure it is working, the next time you invoke ssh you can just put it in the background, and also use the -N flag so that it does not open a terminal connection (unless you need it):
Code:
ssh -L localhost:7885:localhost:7875 -N my-server.example.com &
(Note: I use port 7885 on localhost, in case 7875 is already used by a local Nxt instance. But any available port can be used instead.)
Obviously, in your case you can securely access your VPS server over this ssh tunnel, but other users are still at risk - and you can't give everyone ssh access.
Thank you very much. This is exactly what I've been waiting for. Will try it
Is the online wallet atm safe enough to be keeping my NXT or should I be using the java program?
I have finally up & running my VPS client @ http://94.102.63.115:7875/
Does that mean that other users can connect there with their accounts? If so I would be glad to host them (and a good opportunity to test if everything is ok)!
Does that mean that other users can connect there with their accounts? If so I would be glad to host them (and a good opportunity to test if everything is ok)!
They could connect, but please be aware passwords are submitted in clear text - better use accounts holding only small amounts.
EDIT: Thanks for the info!
I have finally up & running my VPS client @ http://94.102.63.115:7875/
Does that mean that other users can connect there with their accounts? If so I would be glad to host them (and a good opportunity to test if everything is ok)!
Does that mean that other users can connect there with their accounts? If so I would be glad to host them (and a good opportunity to test if everything is ok)!
They could connect, but please be aware passwords are submitted in clear text - better use accounts holding only small amounts.
Here is a security tip for those running Nxt on a remote server:
The Nxt server uses plain http, not https. So if you a running a VPS server at http://my-server.example.com:7875, every time you unlock your account there is a risk that the password will be captured in transit. There is another annoyance in such a setup: since you are not running on localhost, the Nxt interface disables access to certain features, e.g. you cannot remove peers from the blacklist / active list by clicking on the trash icon. But as long as you have ssh access to the remote server, there is a simple solution. Just use ssh tunneling:
Code:
ssh -L localhost:7885:localhost:7875 my-server.example.com
The above command will establish an ssh tunnel between your machine (localhost) and the remove server where Nxt is running, my-server.example.com, from port 7885 on localhost to port 7875 on the remote host. Then, instead of going to http://my-server.example.com:7875 , open http://localhost:7885 , and you will be connected to the remote Nxt instance. Except, your connection will be encrypted so nobody can listen to it. And, from the point of view of the remote Nxt process, your connection is coming from localhost, so editing the peers lists will be enabled.
Once you make sure it is working, the next time you invoke ssh you can just put it in the background, and also use the -N flag so that it does not open a terminal connection (unless you need it):
Code:
ssh -L localhost:7885:localhost:7875 -N my-server.example.com &
(Note: I use port 7885 on localhost, in case 7875 is already used by a local Nxt instance. But any available port can be used instead.)
Obviously, in your case you can securely access your VPS server over this ssh tunnel, but other users are still at risk - and you can't give everyone ssh access.
I have finally up & running my VPS client @ http://94.102.63.115:7875/
Does that mean that other users can connect there with their accounts? If so I would be glad to host them (and a good opportunity to test if everything is ok)!
I get this:Does that mean that other users can connect there with their accounts? If so I would be glad to host them (and a good opportunity to test if everything is ok)!
java.nio.channels.ClosedChannelException
Only 3 peers connected with red flags and stuck at genesis block!
Timing issues??
Exception in thread "pool-1-thread-1" java.lang.NullPointerException
at Nxt$1.completed(Unknown Source)
at Nxt$1.completed(Unknown Source)
at sun.nio.ch.Invoker.invokeUnchecked(Unknown Source)
at sun.nio.ch.Invoker$2.run(Unknown Source)
at sun.nio.ch.AsynchronousChannelGroupImpl$1.run(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)
Exception in thread "pool-1-thread-2" java.lang.NullPointerException
at Nxt$1.completed(Unknown Source)
at Nxt$1.completed(Unknown Source)
at sun.nio.ch.Invoker.invokeUnchecked(Unknown Source)
at sun.nio.ch.Invoker$2.run(Unknown Source)
at sun.nio.ch.AsynchronousChannelGroupImpl$1.run(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)
I bet BCNext is sleeping now. Just restart everything.
Jump to: