That is indeed odd and should not be needed. I am not sure what exactly went wrong in your installation, but you should not have to run those commands as root unless your peer was also started as root.
BR On Tue, 2024-12-17 at 22:25 +0100, aaa aaa wrote: > Also it could be fine to document this issue in the official doc > please. We could also set error when the required permission has not > been reach as well yet. > > On Tue, Dec 17, 2024 at 10:21 PM aaa aaa <[email protected]> > wrote: > > Hello, people! > > > > I fixed my issue. > > > > It did not sounds to be configuration related. Sounds more to be a > > permission issue. When I do not have permission there is no error > > yet. > > > > To fix the issue, I did: > > > > echo "$(sudo /opt/gnunet-bin/bin/gnunet-hello --export-hello -c > > peer1.conf)" | sudo /opt/gnunet-bin/bin/gnunet-hello --import-hello > > -c peer2.conf ; > > > > Thanks very much for help and support for everyone including > > martin!! > >
