How to add seeders to config.json

Development
1

  1. Log into your VPS.

  2. Change directory to .znn

cd /root/.znn
  1. Open config.json in nano editor.
nano config.json

  1. Insert a comma after the } as shown.
    Screenshot 2025-04-21 at 8.54.54 PM

  2. Paste the seeders:

    Screenshot 2025-04-21 at 9.09.47 PM
    Screenshot 2025-04-21 at 9.09.47 PM520×770 174 KB

    "Net": {
		"Seeders": [
			"enode://321603fcaa05f94685eed6f21237128ce73426ec8dafda1391d24ff15657e773493b0d3027e8bbb31b026871c34d90e9784bd81f17ebd65c98bb82ba30c1fa1b@109.104.153.179:35995",
			"enode://725d1d2039dfcd18639da9ecaf842c48ad0559d04b6d64b8984973c87a917c761815804a725dd9fc3ebde6207588d40a46677a7ceb8401b82f978529f3f4de87@203.23.128.244:35995",
			"enode://cf747c665d858a521948c61726be2353ba5436d501e24a8947cb5810667fb5e10fecc08aedc8a563da1a105e960e2203025bd494144bd3b22b2f9955e4290212@103.106.228.23:35995",
			"enode://e44faaa3a6936d690bfa7631a16f44ca48ee7932c07e412ed1ae8321f04ca36d27202587ec313041b0d758dbc3bec66630e22ff1ed5f76f156bae69ae321d3a0@147.78.1.111:35995",
			"enode://f24dba632f6c6fcdf11266bb3dd4368f4e19898ef5831afb265c57cbc68d3e78b28750b5f411b86da80390def7c8548d4e4dc84c3c8a120ad177d9d84e3f9a13@23.95.77.201:35995",
			"enode://70bb10c735ca16c122fb108afdab7a1641b977ad9a5c863d0c45195bf24f3b2854a2451d57d35912ce8d1c1309ea86c672dc05c4935f28aa9a76686926f98a0b@185.192.124.162:35995",
			"enode://c26068988ba35648776d800bff9541edf6e4ff20dba45394511659e18ab4c9472e7741778dbc0960c4ed386a679aa1c20a9e904844dba6e282027781059d1a92@103.75.119.93:35995",
			"enode://1b9f3522e91d7a3e6a54b02d57309ae547d985014b6d06e14c29c44865cfd6f08e5abc81b6c45fd41e98c4077a508daaea266711fc9f09ce14f3bf7e0c985279@45.154.205.72:35995",
			"enode://d6a262ca6d9c0429008bf88048a2b8fd6e84482efe59d13709132d710bc6706d24e6ffc426f7f63b8ecd56156763581bb0b6171f2fcd2f0eed3f7132468aa447@37.143.130.57:35995",
			"enode://b64c4289d1ca42fd8af9ad3e6a6ed2d6e79b8ac2c05d6af7187313b7edc001d7ec8296e9081ba514bc511df72463714c99668abfbbff731bac61917c00c98dae@185.186.78.207:35995",
			"enode://1f541366fc3c7ca56cbbe549465a9d100942e27c3fbdda881311c3878f628cd03b08372e607e898afa0ce4655d417b94993602f1a626ee66fe00b5dc42c48d55@65.109.138.231:35995",
			"enode://f23b11c75ea9b3348f6e402096cb717767f577c7ab76aa9a7c6aa6cb0f1cbdee72ca3ac3fad61d761d74f0c6787268f6b9bd51e16d051591f4545d250c7434a2@162.55.53.126:35995",
			"enode://232db9014fbdd94c364ea89733ad6adbc0924f8e7f55b5be4b12a3e8ef4d586053e5af9d50addaab5e52d47a5589b7440ad1f8e9b3dc2d75a8f237dd16bf31a8@49.12.218.89:35995"
		]
	}

  1. ctrl + x, save changes

  2. Restart go-zenon

systemctl restart go-zenon
  1. Make sure go-zenon is running. (An improper config.json will prevent go-zenon from restarting.)
systemctl status go-zenon

(ctrl+c to close status)

Bonus: If you installed the backup script, this command will run a manual backup:

/usr/local/bin/backup.sh go-zenon --backup
2 Likes