Probably make sure that you’ve forwarded to the correct internal IP. As you said I also have nodes running on X86 Linux and every thing works fine. which makes me think/assume that your 4001 port might be forwarded to a different local ip.
Also make sure you can dial your own node within your own local network. If you can’t then there’s probably an ip setting in the config prohibiting it like a 127.0.0.1 (allow only on-node traffic) that you might want to have as 0.0.0.0 (allow the local network).
I didn’t change the config file. The swarm is listening on 0.0.0.0 and not on the backloop address.
Port 4001 tcp + udp is forwarded correctly.
I guess most people using the X86 versions, so it might be that there is a undetected bug in the 64 bit arm version that’s cause it not to function well.
It’s a fresh install off v0.32.1 not an update form a previous version.
I guess most people using the X86 versions, so it might be that there is a undetected bug in the 64 bit arm version that’s cause it not to function well.
FWIW, I’ve been running a swarm of ~100-200 nodes on arm64, with maybe one x86_64 node. Mostly Raspberry Pi 4B, and it works well most of the time, the only problem I experience is `ipfs pin add` often hangs with a wantlist of ~7 CIDs - #5 by hector, and I’m told that may be fixed in 0.33.0-rc1 but I’ve not yet had a chance to try it.
So I don’t think your system being a Raspberry Pi 5 should cause you any problems. As the other posters have mentioned, I would be suspicious of your network setup - firewalls, NAT, etc.
if check.ipfs.network is showing failure to connect, then inbrowser.link with default settings won’t be able to access the content either.
If you can get a valid endpoint and access that, you can configure your own node as your trustless gateway, but ideally you shouldn’t have to do that at all
Could be? I don’t have rpi5 at hand, but docker run --rm -it --net=host ipfs/kubo:v0.33.0-rc3 works fine on rpi4.
Would be good to have someone with rpi5 to confirm if they have similar issue, until we have second data point from other rpi5 user, this looks more like something specific your network setup somehow.
All or just WAN? Are you able to dial Raspbery PI Peer from within LAN?