active peer addresses for the Aptos testnetQuestion Title

[neshac]

Discord user ID

nesha_60743

Describe your question in detail.

Hi,

Could you share some active peer addresses for the Aptos testnet?

I'm having trouble connecting my full node to the Aptos testnet. My node is not discovering any peers, and I keep getting errors like NoConnectedPeers("No available peers found!")
I’m using the latest snapshot from BWareLabs , but my node still can’t connect to the network
My fullnode.yaml configuration includes discovery_method: "onchain"

My node is running and ready to connect. Here’s my peer address: /ip4/95.216.243.80/tcp/6182/noise-ik/0xcc34863f93daf3469bab29b73dca87b4d9cfa65c815c2d956376e74689291a72/handshake/0

What error, if any, are you getting?

No response

What have you tried or looked at? Or how can we reproduce the error?

No response

Which operating system are you using?

Linux (Ubuntu, Fedora, Windows WSL, etc.)

Which SDK or tool are you using? (if any)

Aptos CLI

Describe your environment or tooling in detail

No response

[justlstn]

Hey @neshac.

May I ask you to share your fullnode.yaml file content?

My node is running and ready to connect. Here’s my peer address: /ip4/95.216.243.80/tcp/6182/noise-ik/0xcc34863f93daf3469bab29b73dca87b4d9cfa65c815c2d956376e74689291a72/handshake/0

The content above shouldn't exist in the fullnode.yaml file for Public Fullnode (PFN). It is only needed for VFN.
Depends on what you use to run the node, either docker or from source, the config may look like this:

Screenshot

Besides, make sure you use the correct genesis.blob and waypoint.txt files.

[neshac]

Hi,
Waypoint.txt and genesis.blob files are downloaded from:
https://raw.githubusercontent.com/aptos-labs/aptos-networks/main/testnet/waypoint.txt
and
https://raw.githubusercontent.com/aptos-labs/aptos-networks/main/testnet/genesis.blob

This is my fullnode.yaml:

base:
role: "full_node"
data_dir: "/home/aptos/.aptos/data"
waypoint:
from_file: "/home/aptos/.aptos/genesis/waypoint.txt"

execution:
genesis_file_location: "/home/aptos/.aptos/genesis/genesis.blob"

storage:
rocksdb_configs:
enable_storage_sharding: true

full_node_networks:

• network_id: "public"
  discovery_method: "onchain"
  listen_address: "/ip4/95.216.243.80/tcp/6182"
  identity:
  type: "from_file"
  path: "/home/aptos/.aptos/validator-full-node-identity.yaml"

api:
enabled: true
address: "127.0.0.1:8080"

[justlstn]

Hi @neshac,

Yep, the file sources are correct.

There are quite a few more suggestions from me:

• you don't need to use your public address for listen_address. Simply use 0.0.0.0. Otherwise you add additional network overhead.
• as per the documentation, check if the port 6182 is open and there's no firewall (software or hardware) blocking incoming requests to this port.

[neshac]

Thanks for your reply,
I'll change to 0.0.0.0
port 6182 is open
iptables -vnL
Chain INPUT (policy DROP 40M packets, 2770M bytes)
pkts bytes target prot opt in out source destination
..................................
90 5380 ACCEPT tcp -- * * 0.0.0.0/0 0.0.0.0/0 tcp dpt:6182
..................................

You can try from your local machine
telnet 95.216.243.80 6182
and you will see that port is open

What to do now?
Stil in logl:
2025-04-22T18:46:21.005931Z [data-client-9] WARN state-sync/aptos-data-client/src/poller.rs:296 {"error":"NoConnectedPeers("No available peers found!")","event":"aggregate_summary","message":"Unable to update global summary cache!","name":"data_summary_poller"}
2025-04-22T18:46:21.005942Z [data-client-9] WARN state-sync/aptos-data-client/src/client.rs:174 {"error":"NoConnectedPeers("No available peers found!")","event":"priority_and_regular_peers","message":"Unable to update priority and regular peer metrics!","name":"peer_states"}
2025-04-22T18:46:21.005943Z [data-client-9] WARN state-sync/aptos-data-client/src/client.rs:189 {"error":"NoConnectedPeers("No available peers found!")","event":"priority_peer_categories","message":"Unable to update peer priority metrics!","name":"peer_states"}
2025-04-22T18:46:21.005944Z [data-client-9] WARN state-sync/aptos-data-client/src/poller.rs:319 {"error":"NoConnectedPeers("No available peers found!")","event":"peer_polling_error","message":"Unable to identify peers to poll!","name":"data_summary_poller"}
2025-04-22T18:46:21.044142Z [stream-serv-7] INFO state-sync/data-streaming-service/src/streaming_service.rs:467 {"message":"Latest global data summary is empty.","name":"refresh_global_data"}

[justlstn]

I also missed one point here.

identity:
type: "from_file"
path: "/home/aptos/.aptos/validator-full-node-identity.yaml"

This part doesn't need to be included also, as identity for PFN is generated automatically. I'd suggest you to eliminate it and try to run the node. However, if you want the identity to be set for the PFN, you may follow these docs.

In fact, I don't really see much why the node doesn't connect to peers automatically. The upstream seed would help here, obviously, but I cannot find any in Discord server or docs. Unfortunately I can't bring any other ideas more, will think about it though.