IPFS error

[vksputnik]

Immediately after installation on VPS I get the following errors:

Installed under root user on Ampere arm64, with the same configuration on amd64 instance works without problems.

Core DAppNode Packages versions
bind.dnp.dappnode.eth: 0.2.11
dappmanager.dnp.dappnode.eth: 0.2.84, commit: 657ee5f4
https.dnp.dappnode.eth: 0.2.1
ipfs.dnp.dappnode.eth: 0.2.22
vpn.dnp.dappnode.eth:
wifi.dnp.dappnode.eth: 0.2.9
wireguard.dnp.dappnode.eth: 0.1.3
System info
dockerComposeVersion: 2.24.6
dockerServerVersion: 25.0.3
dockerCliVersion: 25.0.3
os: ubuntu
versionCodename: focal
architecture: arm64
Disk usage: 29%

[alexpeterson91]

Are you still having this issue? There have been several core updates since you opened this. Will be closing this if you don't reply shortly since there's been updates to the IPFS software and many to the other core packages. Impossible to know what's going on from the provided screenshots and it shouldn't be reproducible anymore since the updates. But if you still have an issue just reply here. Also to note when using a cloud server whether it's a VPS, VDS, or full dedicated servers many hosting providers (Hetzner being most notorious, but by no means the only provider that will promptly take action on fresh dappnode installs due to the IPFS package. The IPFS package default setting will cause IPFS to look for peers when it starts but it will scan private IP ranges which are considered abuse by most providers and they will immediately lock your account and if you can't fix the issue right away and provide an explanation within 24 hours you may lose your server. I don't know who you host with or if this was a contributing factor but for any future cloud dappnode deployments make sure to as soon as possible go to the IPFS package (Left Navbar select packages, then at the top of this page select the system tab and you'll see the core dappnode packages IPFS included. Open the IPFS package navigate to its config tab and select the profile as server this will ensure that your IPFS does not scan private ip ranges and protect you from inadvertently throwing alarms for abuse due to netscans of private IPs.