...
Now that an account has been created , and a consensus client is operating, Geth & Prysm will begin to automatically synchronize it with the rest of the Ethereum network. This will take quite some time, and is unavoidable. You must be prepared to wait days before the process is complete. Once finished with the initial sync, your Node will keep itself synchronized - but the first time is lengthy.
...
The node will attempt to use all available resources to finish as quickly as possible, and but your server’s host may consider classify it to be as abuse. They’ll respond by automatically “killing” your node. Here’s how to tell in the Geth Server:
...
If you see that, then your node was probably shut down for abusing your host’s “Terms of Service”. Yes, I was guilty of that once. Sorry Google. Explore the use of “cpulimit” to prevent that abuse, or increase the server resources to comply with your hosts demands.
The point is: check in on the process from time-to-time, and restart it (if needed). You lose nothing but time, as the download will be recovered from the moment it was killed.
...
Control.
To monitor the sync progress, you may use the built-in Geth JavaScript client to check up on it. Once you’ve SSH’d in to your server, start the Geth JavaScript console using:
...
This means that your node has stopped synchronizing. This is likely because it has finished successfully, or possibly because your node has been shut down.
The node will attempt to use all available resources to finish as quickly as possible, and your server’s host may consider it to be abuse. They’ll respond by automatically “killing” your node. Here’s how to tell in the Geth Server:
...
If you see that, then your node was probably shut down for abusing your host’s “Terms of Service”. Yes, I was guilty of that once. Sorry Google. Explore the use of “cpulimit” to prevent that abuse, or increase the server resources to comply with your hosts demands.
Assuming that the Geth Server isn’t shutdown, Ensure that the Geth Server isn’t shutdown (i.e. for abuse, see above) and that it continues to process the network, and that . If “eth.syncing” generates a “false” reply in the Geth Console, then your blockchain should is now be fully sync’d synchronized and your node ready for the next step.
...
Backup the account.
You will need both the backup and the password to access your wallet in case of a disaster.
See official documentation for details.
...
Setup
...
a secure tunnel for encrypted communication.
We discourage running any software on your CAS server (except for CAS itself). This warning includes the Geth Node Server. The simple solution is to use port forwarding to enable CAS access to your separate Geth Node Server. Two options are explained:
Option 1: Using the GB Wallet Tunnel (recommended):
General Bytes includes an integrated open-source ssh client in CAS. The client is designed to work effortlessly with the GB Wallet Tunnel Server.Your CAS server and this node must have a secure line. Your passphrase and other sensitive information will be passed back & forth. Encrypt (and protect) this communication by using a secure SSH tunnel.
The GB Wallet Tunnel is recommended.
General Bytes has incorporated an open-source SSH client into CAS.
Click here for instructions to install the GB Wallet Tunnel Server on this node.
...
Alternative (unsupported):
Build an SSH tunnel
...
You may elect to use the native SSH tunnel for secure RPC communication with this Node:
The general usage would be:
| Code Block |
|---|
ssh -f -N -i /home/gb/.ssh/cas-geth-node -L 8545:127.0.0.1:8545 gb@35.237.163.176 |
In the above example (run from your CAS server CLI), the options explained:
"
ssh -f -N" is the "create a permanent tunnel in the background" command."
-i /home/gb/.ssh/cas-geth-node" specifies the SSH private key file to be used."
-L 8545:127.0.0.1:8545" are the Geth's default RPC ports being forwarded."
gb@35.237.163.176" is the SSH user (and IP) of the Node.
This presumes that your private key file is stored at /home/gb/.ssh/ as: cas-geth-node
We do absolutely encourage password-less logins (use a private key).
If the CAS system permits multiple users, you should password-protect the private key.
...
(instead of the GB Wallet Tunnel), see: https://generalbytes.atlassian.net/l/cp/b7j5AVHA
For those instructions, set
FORWARDED_PORT=8545
...
Unlock your account
| Note |
|---|
The Geth Node Server must be running & completely synchronized to successfully proceed. |
...