Unable to connect to Heisenberg testnet - bootnodes timeout on port 30333

[kyorozaka-dot]

Summary

I successfully built and configured quantus-node following the official installation guide, but I cannot connect to the Heisenberg testnet. The node consistently shows 0 peers and all bootnode connections timeout.

Environment

• OS: Linux Mint 22.2
• Kernel: 6.14.0-36-generic
• Node Version: 0.4.2-b6c479da194
• CPU: Intel Core Ultra 9 185H (16 cores, 22 threads)
• Memory: 31620MB
• Chain: Heisenberg
• Wallet Address: qzkXpTw5oLkeBwn9SzUbu3jug6VJ5oD4QeRaoqet98eJxPxVi

Build Process

✅ Successfully completed:

• Rust nightly installation
• cargo build --release -p quantus-node (completed in ~5 minutes)
• quantus-miner build (completed in ~45 seconds)
• External miner configured at http://127.0.0.1:4003

Issue Details

Network Diagnostics

✅ DNS Resolution: SUCCESS

$ nslookup a1-heisenberg.quantus.cat
Name:    a1-heisenberg.quantus.cat
Address: 104.21.6.127
Address: 172.67.134.220

$ nslookup a2-heisenberg.quantus.cat
Name:    a2-heisenberg.quantus.cat
Address: 104.21.6.127
Address: 172.67.134.220

✅ Ping Test: SUCCESS

$ ping -c 3 a1-heisenberg.quantus.cat
3 packets transmitted, 3 received, 0% packet loss
rtt min/avg/max/mdev = 42.783/48.892/56.004/5.443 ms

$ ping -c 3 a2-heisenberg.quantus.cat
3 packets transmitted, 3 received, 0% packet loss
rtt min/avg/max/mdev = 29.326/47.121/59.109/12.833 ms

❌ Port 30333 Connection: TIMEOUT

$ nc -zv a1-heisenberg.quantus.cat 30333
nc: connect to a1-heisenberg.quantus.cat (2606:4700:3035::6815:67f) port 30333 (tcp) failed: Connection timed out

$ nc -zv a2-heisenberg.quantus.cat 30333
nc: connect to a2-heisenberg.quantus.cat (2606:4700:3030::ac43:86dc) port 30333 (tcp) failed: Connection timed out

Node Logs

2025-11-29 22:08:26 Quantus Node    
2025-11-29 22:08:26 ✌️  version 0.4.2-b6c479da194    
2025-11-29 22:08:26 📋 Chain specification: Heisenberg    
2025-11-29 22:08:26 🏷  Node name: quizzical-arch-1459    
2025-11-29 22:08:26 👤 Role: FULL    
2025-11-29 22:08:26 🏷  Local node identity is: QmUjAmmqofgPdwrMHNm3dvLgDSbbu7B2mLkBahXhopKCz8    
2025-11-29 22:08:26 🔊 Using pqc (ml-kem) ⚛ for noise!    
2025-11-29 22:08:26 📦 Highest known block at #0    

2025-11-29 22:08:31 💤 Idle (0 peers), best: #0 (0x9efe…979f), finalized #0 (0x9efe…979f), ⬇ 0 ⬆ 0    
2025-11-29 22:08:36 💤 Idle (0 peers), best: #0 (0x9efe…979f), finalized #0 (0x9efe…979f), ⬇ 0 ⬆ 0    
2025-11-29 22:08:46 ❌ Error while dialing /dns/telemetry.res.fm/tcp/443/x-parity-wss/%2Fsubmit%2F: Custom { kind: Other, error: Timeout }    
2025-11-29 22:08:46 ❌ Error while dialing /dns/shard-telemetry.quantus.cat/tcp/443/x-parity-wss/%2Fsubmit%2F: Custom { kind: Other, error: Timeout }    
2025-11-29 22:09:01 💤 Idle (0 peers), best: #0 (0x9efe…979f), finalized #0 (0x9efe…979f), ⬇ 0 ⬆ 0    

(Pattern continues with 0 peers indefinitely)

Bootnode Addresses Tested

From chain spec (heisenberg-raw.json):

"bootNodes": [
  "/dns/a1-heisenberg.quantus.cat/tcp/30333/p2p/Qmdts9fu3NCMFnvLdD1dHAHFer8EPzVDXxVnyPxRKA3Gkt",
  "/dns/a2-heisenberg.quantus.cat/tcp/30333/p2p/QmcKHndoiNRdiT6iVp6ugj8bNse5Vd5WmCoE9YWn9kNaTM"
]

Also tried with IPv4 direct addresses:

--bootnodes "/ip4/104.21.6.127/tcp/30333/p2p/Qmdts9fu3NCMFnvLdD1dHAHFer8EPzVDXxVnyPxRKA3Gkt"
--bootnodes "/ip4/172.67.134.220/tcp/30333/p2p/QmcKHndoiNRdiT6iVp6ugj8bNse5Vd5WmCoE9YWn9kNaTM"

Same result: Connection timeout, 0 peers.

Firewall Configuration

$ sudo ufw status
Status: active

To                         Action      From
--                         ------      ----
30333/tcp                  ALLOW       Anywhere

Port 30333 is open on my system.

Questions

1. Are the Heisenberg testnet bootnodes currently operational?

   • Both a1-heisenberg.quantus.cat:30333 and a2-heisenberg.quantus.cat:30333 appear to be unreachable

2. Is there a known maintenance window or network downtime?

   • Unable to find any announcements about testnet status

3. Are there alternative bootnode addresses available?

   • Would appreciate any working bootnode endpoints

4. What is the expected timeline for testnet availability?

   • I have a full mining setup ready and would like to participate once connectivity is restored

System Information

• Local Peer ID: QmUjAmmqofgPdwrMHNm3dvLgDSbbu7B2mLkBahXhopKCz8
• Miner: Running successfully on http://127.0.0.1:4003
• Network: Stable internet connection (fiber, low latency to bootnode IPs)

Additional Context

I followed the official documentation precisely:

• https://github.com/Quantus-Network/chain/blob/main/README.md
• https://github.com/Quantus-Network/chain/blob/main/MINING.md

My setup appears to be correctly configured based on all the successful components. The only issue is network connectivity to the bootnodes themselves.

Thank you for your assistance! Looking forward to contributing to the Quantus testnet once this connectivity issue is resolved.