Buy crypto anonymously on the Incognito pDEX   

[solved] Need help setting up vnode

#1

I’ve been unsuccessful at setting up my vnode. Hopefully someone can help me out or give me some suggestions. I’ve detailed the steps I took below…

I followed the “How to host a Virtual Node” instructions on the forum (tried method 1 and method 2). After I run the script, no containers are showing under “sudo docker ps” & “sudo docker stats”. The wallet still shows the import button, and the incognito monitor just shows unknown status.

Here is what I’ve done so far (tried both Ubuntu 18 & 22):

  1. Created a new Master Key (new keychain) in my incognito wallet.
    -Copied the Validator Key & Validator Public Key of the newly created address.

  2. Transferred 1751 to the new address.

  3. Created infura account and copied the WEB3/Ethereum mainnet url.
    -https://mainnet.infura.io/v3/############################

  4. Redirected ports 8334 & 9433 to local ip.

  5. Installed fresh image of Ubuntu (VM has 4 cores & 8gb memory, 300GB SSD).

5a. used interactive script to install incognito node:
sudo bash -c “apt install curl -y && curl -L https://raw.githubusercontent.com/incognitochain/incognito-chain/production/bin/blink.sh -O && chmod +x blink.sh && ./blink.sh”

5b. Settings used: validator key (from step 1), default ports, default index, default access token, infura from step 3: https://mainnet.infura.io/v3/############################

Results:
-Went to https://monitor.incognito.org/node-monitor, and used the validator public key from step 1; Role: Not Stake, Status: Unknown.
-Added vNode under power in app. The button shows “Import”.
-sudo docker ps & stats shows no containers.
-System Monitor shows no CPU activity.

Let me know if I can provide anymore info/screenshots of anything etc…

Thanks!

1 Like
#2

What does docker ps show?

#3

nothing shows under CONTAINER ID or any other header:
image

#4

You don’t have to redirect the port, I guess you config this on your Modem Router?
So let remove these rules.

Please make sure your VM can go to internet, config VM’s network adapter in Bridged mode.

try docker ps -a to see if there any crashed container
try docker image ls to see if the script able to pull latest incognito image tag
show us the the error log in /home/incognito/node_data/

1 Like
#5

Please send a direct message to @Support with the output of the following commands. (don’t paste them here)

> docker ps -a
> docker logs inc_mainnet_0 
> docker container inspect inc_mainnet_0
(the 2 commands above can be ignored if the very first one does not show anything)
> sudo systemctl status IncognitoUpdater.service
> sudo systemctl status IncognitoUpdater.timer
> journalctl --since "1 week ago" | grep IncN
>

Also, please check and send any log file that can be found in /home/incognito/node_data/

1 Like
#6

I solved the problem by changing the network connection from bridged to NAT network connection in the vmware settings. Ping returned DUPs when using bridged, so I thought about messing with that and out of luck it works now.

I still wish I could solve the actual underlying problem (with bridge) or at least understand why bridge is causing these issues.

Now I’m currently running the bootstrap script! Thanks of the help and support!

2 Likes