CRIT Failed to start beacon node

Jun 13 10:24:54.059 CRIT Failed to start beacon node, reason: Error loading checkpoint state from remote: HttpClient(, kind: timeout, detail: operation timed out), module: lighthouse:641

May 31 09:44:12.048 CRIT Failed to start beacon node             reason: Syncing from genesis is insecure and incompatible with data availability checks. You should instead perform a checkpoint sync from a trusted node using the --checkpoint-sync-url option. For a list of public endpoints, see: https://eth-clients.github.io/checkpoint-sync-endpoints/ Alternatively, use --allow-insecure-genesis-sync if the risks are understood.

Related

• lighthouse beacon_node

See also

• lighthouse beacon_node, --execution-endpoint, --execution-jwt, --allow-insecure-genesis-sync, logs, --checkpoint-sync-url, --help, checkpoint sync, beacon.log