renaming to josh-run5.sh
1 Like
Find this out by running the join command then scrolling back up to about 3 lines from the top and looking for your own external IP and the then get the port that was assigned
1 Like
@Southside will it help you if i set up a small network for you to refine a script?
2 Likes
Very much - I am failing to download the connection_info config for comnet from
safe networks add comnet https://sn-comnet.s3.eu-west-2.amazonaws.com/node_connection_info.config
Switching to ācomnetā networkā¦
Fetching ācomnetā network connection information from āhttps://sn-comnet.s3.eu-west-2.amazonaws.com/node_connection_info.configā ā¦
Error:
0: expected value at line 1 column 1
Location:
/rustc/f1edd0429582dd29cccacaf50fd134b05593bd9c/library/core/src/result.rs:1914
1 Like
Ok, DM details in a few so that it wonāt be used otherwise. Will only be baby.
3 Likes
Muchas gracias, senor 
3 Likes
I just think out loud, and you guys start working on a script like Giant Amazonian ants (Dinoponera - Wikipedia). No script is really necessary. I just thought it might further remove some silly mistakes like forgetting to remove .safe and/or inputting some old version numbers. Iām not here to manage or pressure anybody. But thanks all the same!
3 Likes
If everyone is starting from the same commands then it removes a possible source of error/confusion.
So IMHO its entirely worthwhile.
Edit: The less time we waste on silly config errors and no-quite-right command lines, the more time we have to look for real problems
3 Likes
just to confirm here,
that command does not include nohup so closing the terminal kills the node.
as @bochaco said regular safe node join --skip-auto-port-forwarding
will work and directs logs also.
alternatively I think we need nohup or something along the lines of
nohup ~/.safe/node/sn_node --skip-auto-port-forwarding --log-dir ~/.safe/node/logs --json-logs &
2 Likes
OK as soon as I can get a connnection-info.config that works, I will try this out.
Certainly makes sense to me
1 Like
There is also $ safe node install which pulls the latest version available of sn_node and installs it at ~/.safe/node/ ready to then be used by other CLIās node commands. There is an issue at the moment which doesnāt allow to specify a specific version of sn_node but latest, although thatās being fixed as well for future use.
6 Likes
Thats disabled for now - sadly would have saved much faffingā¦
willie@gagarin:~$ safe node install
Error:
0: Self updates are disabled
Location:
sn_cli/src/operations/node.rs:73
6 Likes
ā¦I see, ok, thanks!
5 Likes
This was unintentional. A PR Iām submitting shortly will fix it. I wanted to do all these testnets after we had better UX :).
8 Likes
It is extremely unfortunate that the command to copy from the terminal Ctrl-Shift-c is so similar to Ctrl-c
Also unfortunate is that my advice above about how to find the assigned port may not be correct in all circumstances ā seems like it is caching an old port somehow despite me nujking ~/.safe on every runā¦ Obv something simple Im missingā¦
Luckily the hour has just changed so I have a fresh log file to pore over
1 Like
No shortage of eagerness to run tests. Better UX, good reason for more testing, just give us a reason 
8 Likes
Can you open the port and then set it with --public-address in the join command?
Not ideal for a script though.
2 Likes
Can you restart that baby-test Looks like its caching port 54705 for my IP
addr: 9n.nnn.nnn.nn5:54705, connection: None }
but then fails with
Node cannot join the network since it is not externally reachable: 9n.nnn.nn.nn5:33174
Mostly due to me ctrl-Cing instead of actually copying from the terminal
1 Like
Unsure how I would (quickly) put that in a scriptā¦
1 Like
Just a general comment: the node join command should expose the necessary arguments now.
4 Likes