Try with sudo.
1 Like
sudo: safenode-manager: command not found
You may need to launch it from where it is (~/.local/bin?).
1 Like
Had it, did every erase but no help in the end i reinstalled ubuntu on server with 70 nodes, now it works.
1 Like
Wow, finally I made some progress and my nodes are running on my Linux via safenode-manager… Now, how can I add my Discord ID and finally see some nanos coming in? 
4 Likes
You use safenode-manager add --owner <discord-id>. I think you have to do that before you launch the nodes, not sure.
2 Likes
yes, it seems so. So I stopped and removed my nodes, then one by one adding with your command.
This is what I get:
1 service(s) to be added
The safe user already exists
Retrieving latest version for safenode…
Then I will start my nodes. Is that a correct procedure?
1 Like
That should do it!
1 Like
Not so sure about that…
And also choose home argument or ports?
I haven’t needed to do that. I’m just going on what worked for me
When my node is “RUNNING” and connected to dozens of peers, does it mean I don’t have to worry about it now? 
6 Likes
Mmh this is an error that I’ve been getting for some time, also in the previous network tests
1 Like
Oh I see! The modern development of the Power line. It might be a bit niche for MaidSafe to produce a binary but it might be possible to compile for it.
2 Likes
if your on safe node manager
you can use sudo env "PATH=$PATH" safenode-manager status --details
to look at the details of your nodes and select one you want to use as a boot strap peer
then when you add the node use the --peer argument to specify that node
here is one i made earlier treat her gentley lol
--peer "/ip4/38.102.85.104/udp/12040/quic-v1/p2p/12D3KooWHQGYbYoMy8Fayb1tspbcVQ3YKkWNJz52KsoNYkJ54YjQ"
2 Likes
No, but if they are running and showing there, then they are not not running… If you do a reset do the node processes stop?
Do you have some logs from the nodes to share, perchance?
As soon as makes sense, but there are bugfixes etc to come first I think that are higher priority (see your second issue).
IMPORTANT NOTE:
If you are building nodes yourself for some reason, you will need to set some env variables otherwise your nodes will not forward earnings correctly.
We can see several users are running nodes using the default forwarding pk for encryption. This is not currently supported in the DAG.
If you want to build the software you will need to set your env variables to:
PAYMENT_FORWARD_PK=8c2f406a52d48d48505e1a3fdbb0c19ab42cc7c4807e9ea19c1fff3e5148f3bbe53431ec5a07544aaeef764e073e4b2fGENESIS_PK=b38f61b8df2cc7d86ceb1039cc23c9e1e2857a97e59ce01a6b1a5d6f7fa5311b521efb158fcdb66113986058ec9e25c8NETWORK_ROYALTIES_PK=8c027130571cea2387a0ceb37c14fec12849015be1573ea6d0a8e4d48da2c1fbe2907ae7503bb7c385b21e2d7ac9d6ff
4 Likes
Hey, brother. Sorry for the late reply. I followed the instructions in the attached link. Hope this helps. https://derflounder.wordpress.com/2020/11/17/installing-rosetta-2-on-apple-silicon-macs/
2 Likes
I currently use the following configuration when starting new nodes, before testing with it use safenode-manager reset. I have specified the ports as allowed in the firewall.
safenode-manager add --count 10 --node-port 12001-12010 --owner dimitarsafenetworkbulgaria --peer /ip4/142.93.42.123/udp/52692/quic-v1/p2p/12D3KooWBeZVDUQ6zCH6v4TyDxmYYY8HEg47LWnTNVSL2UZbXGkh,/ip4/68.183.36.156/udp/35703/quic-v1/p2p/12D3KooWL9LBbD13U5tRmCwuRbkQkXFM4gLEmf7DdN1r3Ek7yAkF,/ip4/167.71.134.146/udp/56898/quic-v1/p2p/12D3KooWQWTEJ4ngwDAE6oLgYdiZk3ejRYxp4do8Akx9GAWUEe9b,/ip4/167.71.130.219/udp/40949/quic-v1/p2p/12D3KooWBA2qjGDmnZd2GyNC5qVw82bSvWDoQj1FBjuj4h11zXaL
EDIT:
@joshuef has given the following peers in Discord:
/ip4/144.126.232.39/udp/54398/quic-v1/p2p/12D3KooWNdBSU88464gHJGdEETisFjvsX6GYsRDB7cqFwJW2hq7m
/ip4/178.128.34.57/udp/42231/quic-v1/p2p/12D3KooWSn9FhKHBbTRuS9FfydrfQ17tGGDByW6SJiSMeW3Gogdo
/ip4/167.99.202.50/udp/36305/quic-v1/p2p/12D3KooWSrS7er3SDMdX5TMuirQWbek7kmbHRtmv1zzEpgB1Wbsw
Privacy. Security. Freedom
3 Likes
That is frickin cool! 
3 Likes