Not working
First of all, the support is super helpful.
But this is not working.
If you subscribe to it from the marketplace and create an instance:
a) you can't connect using the preset security group
b) if you update the security group by yourself, you can connect, but no node is running
c) if you start the node manually, it comes to an error state after 5 minutes and doesn't do anything
If you subscribe from EC2 -> AMI -> Marketplace and try to create an instance the security group is preset and you can connect to that one, but there is still no geth-node container running
If you run it, you'll see this message all the time:
Post-merge network, but no beacon client seen. Please launch one to follow the chain!
Hi firstly we are really sorry that you have experienced issues running a Pre-synced Ethereum Geth node. Our comprehensive support means you can speak to our engineering team to resolve your issue. Specific to the points you raised we wanted to let you know that 1. We have tried to replicate the issue and we are unable to and we do not get the error message you mention nor have we seen any unusual outputs. 2. You can definitely use your existing security group but you will be required to configure SSH rules in order to connect with the instance. For more information, you can follow the "Rules to connect to instances from your computer" from this AWS documentation. 3. You must have a Beacon node or Beacon node connection to sync geth with the latest head. We update our marketplace AMI every day to provide the latest pre-synced data for users but to make sure your node is up to date with the current network head you will need a running synced beacon node connection. Could you confirm you have a running synced Beacon node or Beacon node connection? We would really like to help you with the issues you have listed. If you can share more detailed logs of the errors with us at support@launchnodes.com we can book some time with you to get it fixed Sorry that you have had these issues. If you contact our support team we are very confident we can get your issue fixed.
Hi firstly we are really sorry that you have experienced issues running a Pre-synced Ethereum Geth node. Our comprehensive support means you can speak to our engineering team to resolve your issue. Specific to the points you raised we wanted to let you know that 1. We have tried to replicate the issue and we are unable to and we do not get the error message you mention nor have we seen any unusual outputs. 2. You can definitely use your existing security group but you will be required to configure SSH rules in order to connect with the instance. For more information, you can follow the "Rules to connect to instances from your computer" from this AWS documentation. 3. You must have a Beacon node or Beacon node connection to sync geth with the latest head. We update our marketplace AMI every day to provide the latest pre-synced data for users but to make sure your node is up to date with the current network head you will need a running synced beacon node connection. Could you confirm you have a running synced Beacon node or Beacon node connection? We would really like to help you with the issues you have listed. If you can share more detailed logs of the errors with us at support@launchnodes.com we can book some time with you to get it fixed Sorry that you have had these issues. If you contact our support team we are very confident we can get your issue fixed. Launchnodes Support