Can I transfer the nkn node from 1 device to another, with changing Ip, area and without changing the id node

Nodes & Mining
#1

Hello. When my trial period ends on Google cloud, can I transfer my id, wallet file, and password to another provider’s VPS? if so, which files need to be moved, as far as I understand chaindb is not necessary and can be re-synchronized. Can you tell me if this will work? and how to do it?

#2

As I understand, as long as you transfer your current (Google Cloud) wallet.json and wallet.pswd to your new server, the node will be working as it at new server.

In your Google Cloud: Login root. Your wallet should be located at nkn-node folder.
#Navigate to it with command
cd "$(find / -type d -name "nkn-node")"

See whether wallet.json and wallet.pswd is inside the folder.
ls

#Show the whole string in wallet.json and wallet.pswd. Manually copy the string to your local PC.
cat wallet.json
cat wallet.pswd

In your new server:
#Backup your default wallet.
cd "$(find / -type d -name "nkn-node")"
mkdir backup
systemctl stop nkn-commercial
mv --backup=t wallet.json backup
mv --backup=t wallet.pswd backup

#Create new wallet .json
touch wallet.json
Paste your Google Cloud wallet.json content into it and save.
nano wallet.json

#Create new wallet .pswd
touch wallet.pswd
#Paste your Google Cloud wallet.pswd content into it and save.
nano wallet.pswd

#Restart nkn-commercial
systemctl start nkn-commercial

(You should backup your new default wallet as well, just in case any unexpected happen.)

Btw, I never used Google Cloud. Hope this help. :grinning:

3 Likes
Rollback error: local ledger has forked for more than 180 blocks
#3

This is perfect.

#4

I’ve tried this for two times now but haven’t gotten it to work. I get this error:

root@xxxxxxxxxxx:/home/nkn/nkn-commercial/services/nkn-node# ./nknc info -s
2021/05/09 23:39:30.982300 [ERROR] GID 1, POST request: Post http://localhost:30003: dial tcp 127.0.0.1:30003: connect: connection refused

Systemctl says that the service is running:

● nkn-commercial.service - NKN Commercial
Loaded: loaded (/etc/systemd/system/nkn-commercial.service; enabled; vendor preset: enabled)
Active: active (running) since Sun 2021-05-09 23:33:52 UTC; 9min ago
Main PID: 24233 (nkn-commercial)
Tasks: 45 (limit: 1151)
CGroup: /system.slice/nkn-commercial.service
├─24233 /home/nkn/nkn-commercial/nkn-commercial -d /home/nkn/nkn-commercial
├─24254 ./nkn-commercial service -d="/home/nkn/nkn-commercial/services" -b=NKNXfgWAhS4zpUJhj6M5mjM6fHNBiJww2PWr -c="/home/nkn/nkn-commercial/config.json"
├─24270 ./generator -r http://127.0.0.1:30003 -e 3600
├─24275 ./outline-server -s ss://AEAD_CHACHA20_POLY1305:@127.0.0.1:30488
├─24277 ./outline-server -c ss://AEAD_CHACHA20_POLY1305:@127.0.0.1:30488 -socks 127.0.0.1:30489
├─24284 ./goproxy -addr 127.0.0.1:30080
└─24644 ./nknd --password-file=wallet.pswd --beneficiaryaddr=NKNXfgWAhS4zpUJhj6M5mjM6fHNBiJww2PWr

But nstatus.org says this that the node is offline.