with all options configured, you first need to create an instance: (you should still be in: ~/deployment-playbooks)
this script will ask you for your SSH key passphrase unless you didn't set a passphrase or you entered it recently.
after this process is complete, examine script's output and write down IP (e.g.
192.0.2.1) address and AWS InstanceID (e.g.
i-0123456789abcdef0) for later use. If you chose to use elastic IP, write down node's final IP address.
hosts with the server's ip address (e.g. 192.0.2.1):
run ansible playbook
ansible-playbook -i hosts site.yml
NETSTATS_SERVER url in the browser and check that the node named
NODE_FULLNAME appeared in the list.
login to the node and get enode from parity logs:
ssh email@example.com enode /home/bootnode/logs/parity.log
enode uri and send it to Master of Ceremony. If this line is not found, restart parity
systemctl restart poa-parity
and try again. If
enode uri is still not found, use the commands below to restart all services.
su bootnodepm2 restart all
after that refresh
NETSTATS_SERVER url and check again your node's block number. If your node is still not active or missing
enode, log in to root account and reboot the OS.
sushutdown -r now