I decided to launch a new AWS Ubuntu instance for my IPFS node and still I’m encountering errors. Been launching 8 instances with setting up 8 times to no avail. It’s been very frustrating. Experiencing Murphy’s Law in every step.
Aug 14 13:49:10 ip-172-31-35-57 systemd[1]: Started ipfs daemon.
Aug 14 13:49:10 ip-172-31-35-57 ipfs[218510]: Initializing daemon...
Aug 14 13:49:10 ip-172-31-35-57 ipfs[218510]: Kubo version: 0.22.0
Aug 14 13:49:10 ip-172-31-35-57 ipfs[218510]: Repo version: 14
Aug 14 13:49:10 ip-172-31-35-57 ipfs[218510]: System version: amd64/linux
Aug 14 13:49:10 ip-172-31-35-57 ipfs[218510]: Golang version: go1.19.12
Aug 14 13:49:10 ip-172-31-35-57 ipfs[218510]: Error: no IPFS repo found in /data/ipfs.
Aug 14 13:49:10 ip-172-31-35-57 ipfs[218510]: please run: 'ipfs init'
Aug 14 13:49:10 ip-172-31-35-57 systemd[1]: ipfs.service: Main process exited, code=exited, status=1/FAILURE
Aug 14 13:49:10 ip-172-31-35-57 systemd[1]: ipfs.service: Failed with result 'exit-code'.
But when I ran ipfs init, I get this.
ubuntu@ip-172-31-35-57:~$ ipfs init
generating ED25519 keypair...done
peer identity: 12D3KooWQt2nmHF...
initializing IPFS node at /home/ubuntu/.ipfs
Error: ipfs configuration file already exists!
Reinitializing would overwrite your keys
If you read the error messages closely you will notice you are running ipfs init with IPFS_PATH unset (so it uses default path), while systemd is trying to use /data/ipfs, which is still uninitialized.