Do make sure the port forwarding setting is changed from TCP to UDP (or both).
2 Likes
Thanks, yes, definitely done that. It was already in place for the last testnet. No change.
1 Like
I can see your ndoe from the logs @Josh attempting to connect to our nodes:
[2024-02-14T15:15:48.075462Z INFO sn_networking::event] received identify info from undialed peer for not full kbucket Some(248), dail back to confirm external accesable peer_id=12D3KooWAsV2tcs2SP9XmYD1AZ5bf1NRN9u99TmgBKEcJ8sSD13f addrs={}
[2024-02-14T15:15:48.075549Z WARN sn_networking::event] dialing error: NoAddresses peer_id=12D3KooWAsV2tcs2SP9XmYD1AZ5bf1NRN9u99TmgBKEcJ8sSD13f addrs={}
Seemingly a full MultiAddress is not being provided 
not sure why that would be.
But thatās why youāre not getting on the network. (Still not sure if autonat related or no. But a good place to start from. Iād wager this is similar for other folk haveing issues here,m cc @peca , @storage_guy, if you can give me a PeerId of an unearning node you started, Iāll double check)
edit:
@josh et al.
The node looks like it never started listening on the WAN. All Local node is listening on addresses appear local.
from your logs:
[2024-02-14T15:15:46.918301Z INFO sn_networking::event] Local node is listening on "/ip4/127.0.0.1/udp/6005/quic-v1/p2p/12D3KooWAsV2tcs2SP9XmYD1AZ5bf1NRN9u99TmgBKEcJ8sSD13f"
[2024-02-14T15:15:46.918395Z INFO sn_networking::event] Local node is listening on "/ip4/192.168.254.157/udp/6005/quic-v1/p2p/12D3KooWAsV2tcs2SP9XmYD1AZ5bf1NRN9u99TmgBKEcJ8sSD13f"
weāre digging into what might have caused this now.
7 Likes
My nodes donāt have this problem:
[2024-02-14T15:28:18.107038Z INFO sn_networking::event] Local node is listening on "/ip4/192.168.12.26/udp/
13054/quic-v1/p2p/12D3KooW9pbtTKaX7GS3yFRBmpeVEnBhdUaWVQVPaF8fUMqQqvVZ"
LAN address should be OK, I believe I have port forwarding setup correctly. It worked fine in the last testnet and these lines in logs looked the same.
1 Like
Itās not. Or rather it should, but the autonat removal has removed (it looks like) some code flows that add the external address for broadcasting. So there youāll have the same problem, I think.
@bzee is whipping up a PR for this now, so anyone feeling intrepid could try building it, or just wait a couple of hours for the hopeful new node release.
11 Likes
Removing AutoNAT had a side effect that I wasnāt aware of. libp2p has the concept of an external address. Normally, the flow is that we try to get candidate (public) addresses and then confirm that these are in fact reachable for our peers.
AutoNAT did the last part: confirming reachability of these candidates. As AutoNAT doesnāt function properly under QUIC, this would āconfirmā a candidate without actually confirming.
Iāve introduced a change just now that manually confirms a candidate. This also has the important effect of switching us to āserver modeā.
Letās hope weāve diagnosed it properly and the change will fix what I think it will! 
15 Likes
Whoooo 
about to board a plane so probably not going to be able to build for rapid testing.
Mucho happy that I am not being relegated to the cloud though!!
Will hopefully test the fix shortly.
7 Likes
Popping out to the shops? 
1 Like
Cattle class on your equivalent of easy jet, glamorous it is not. If it had wifi Iād be building 
Edit: engine ignition issues, was fun knowing you all. Put my name up on the network one day 
5 Likes
No luck Iām afraid. Tried two peers from the log of one of my nodes:
export SAFE_PEERS="/ip4/46.101.12.135/udp/42763/quic-v1/p2p/12D3KooWQGTGdhfVFHC6zGs7H25F1rdRyoictZYz4VkTqP8qag37"
and
export SAFE_PEERS="/ip4/209.97.141.205/udp/47332/quic-v1/p2p/12D3KooWQz1tN54F6rNM2s132RRmzdZPxHiiywPiiEXy9WKdyePP"
Both with and without --features=network-contacts
I think it would be good to be able to run examples against a live network. Shall I open an issue for this?
2 Likes
Yeh please do, I agree it would be nice to have!
1 Like
cc @Josh @peca @storage_guy or anyone having poor nodes from home experiences.
A new node release is on the way: chore(release): sn_networking-v0.13.19/sn_faucet-v0.3.67/sn_client-v0ā¦ Ā· maidsafe/safe_network@07afae7 Ā· GitHub
Iāll post again once itās built.
9 Likes
standing by to test was about to try building but if @happybeing dident get it to work Im not even trying lol
1 Like
Iāve got chunks!!! latest release works.
11 Likes
Super work! And super fast resolution!
Yes, getting records and payments on AWS node and ones at home now.
10 Likes
i broke the folders upload command 
looks like my mp3 collection wins again 
**************************************
* Payment Details *
**************************************
Made payment of 0.000000000 for 6 chunks
Made payment of 0.000000000 for royalties fees
New wallet balance: 99.999975465
Error:
0: Register error Cannot add another entry since the register entry cap has been reached: 1024.
1: Cannot add another entry since the register entry cap has been reached: 1024
Location:
sn_cli/src/subcommands/folders.rs:104
Backtrace omitted. Run with RUST_BACKTRACE=1 environment variable to display it.
Run with RUST_BACKTRACE=full to include source snippets.
4 Likes
It is working! I have started 5 nodes on version 0.104.22 and they are all storing chunks and earning
8 Likes
Confirmed here as well, nodes on version 0.104.22 are getting chunks.
11 Likes
I re-uploaded a folder with following results:
Made payment of 0.000000000 for 0 chunks
Made payment of 0.000000000 for royalties fees
New wallet balance: 100.000000000
Paying for folders hierarchy and uploading...
Made payment of 0.000005900 for 4 Folders. New balance: 99.999994100
So, even though I didnāt repay for chunks, I needed to pay for folders hierarchy and uploading... whatever they are. Iām not complaining, just observing how it is working, which I guess is as expected.
I then re-uploaded a couple time more. Took quite a long and varied time, for a 72MB folder with a few subfolders:
First round:
real 1m53,395s
user 0m36,759s
sys 0m13,634s
Second round:
real 5m7,245s
user 0m46,477s
sys 0m17,218s
Third round:
real 2m6,302s
user 0m34,113s
sys 0m15,179s
All of those with no changes in the files or folders. The number (address?) at the end of Folder hierarchy from "foldertest" uploaded successfully at 832db... is different each time.
Paging @bochaco.
4 Likes
nodes from home start and uploads start stalling not sure what this means
ubuntu@safe-hamilton:~/safe/images$ safe files upload -p linuxmint-21.2-mate-64bit.iso --batch-size 400
Logging to directory: "/home/ubuntu/.local/share/safe/client/logs/log_2024-02-15_12-37-49"
Built with git version: 358f475 / main / 358f475
Instantiating a SAFE client...
Trying to fetch the bootstrap peers from https://sn-testnet.s3.eu-west-2.amazonaws.com/network-contacts
Connecting to the network with 48 peers
š Connected to the Network "linuxmint-21.2-mate-64bit.iso" will be made public and linkable
Starting to chunk "linuxmint-21.2-mate-64bit.iso" now.
Chunking 1 files...
Uploading 5823 chunks
ā [00:11:02] [################################>-------] 4698/5823 Retrying failed chunks 1125 ...
ā ² [00:15:53] [######################################>-] 5634/5823 ā [00:17:38] [######################################>-] 5641/5823 ^C
ubuntu@safe-hamilton:~/safe/images$ safe files upload -p linuxmint-21.2-mate-64bit.iso --batch-size 64
Logging to directory: "/home/ubuntu/.local/share/safe/client/logs/log_2024-02-15_12-57-00"
Built with git version: 358f475 / main / 358f475
Instantiating a SAFE client...
Trying to fetch the bootstrap peers from https://sn-testnet.s3.eu-west-2.amazonaws.com/network-contacts
Connecting to the network with 48 peers
š Connected to the Network "linuxmint-21.2-mate-64bit.iso" will be made public and linkable
Starting to chunk "linuxmint-21.2-mate-64bit.iso" now.
Uploading 182 chunks
ā [00:01:03] [###############>------------------------] 71/182 ā [00:01:05] [###############>------------------------] 71/182
1 Like