Kubo works best with an incoming port, similar to qBittorrent. While it can function without one, having a port open allows the node to fully participate in the IPFS network which improves peer discovery, DHT functionality, and overall performance (especially for hosting content). Without it, the node needs to rely on relays, which limits efficiency.
Hi binhex,
Thank you for your excellent work on the arch-qbittorrentvpn image - it’s been incredibly helpful!
I’d like to suggest an idea that seems like a natural extension of your work: arch-kubovpn, a Docker container for running the Kubo (IPFS) daemon through a VPN. Like qBittorrent, Kubo includes a built-in web UI, which makes it easier to manage, and it feels like a good fit for a containerized VPN setup.
I hope you’ll consider it!