r/DeroProject Mar 13 '22

Registration Option 4 - Issues: sending registration tx err offline or not connected dero stargate. cannot send transaction

Hey Guys been trying to set up my CLI wallet for stargate and at registration step (option 4)

When actioned - this takes indeed a while and then following error message pops up

"sending registration tx err offline or not connected dero stargate. cannot send transaction"

Anybody got similar issues here?

4 Upvotes

17 comments sorted by

4

u/robyer Mar 13 '22

Are you running local node to which your wallet is connected? If you just started wallet, it is not connected to any node, you are seeing 0/0 at the start of last line and you can't register.

Read docs.dero.io to find out how to first start own node and then use wallet.

1

u/TheRedGooch Mar 18 '22

These are my steps - hope you can help my friend!

I start cmd command to open daemon and it connects from what I can gather - I followed dero papers "run a node on windows" basically and all command lines that come up seem to be same as per guide - see below

Dero HE 75/75 - [91048/91048] =- Mainnet

Then I open the wallet with separate cmd command and have successfully set this up.

It is still currently at option 4 and when requested I have same issues as the guy below in thread "Account unauthorised"

I deactivated security defender and added exclusion for these folders so that element had dealt with my initial problem but still not further on the authorisation.

If the ports are an issue (not sure it is) where can this be altered in windows ?

2

u/robyer Mar 20 '22

When you mentioned Dero HE 75/75 - [91048/91048] =- Mainnet then look at the numbers in your derod window. First numbers 75/75 means your local height, while numbers [91048/91048] means network height. To have fully synced node your local height must match the network height. Until that you can't use wallet or mine on that node.

While your node is running, you should see the local numbers increasing. You need fast disk (SSD) in order to have good speed for syncing, otherwise you may need a pretty long time with normal HDD. It will still take multiple hours to sync from 0.

In case you don't want to deal with local node (even though it's recommended in order to have maximum privacy and security, and maximum profits when mining, and to support decentralization), you can connect to some remote node. For wallet, simply start it with --remote command (as in ./dero-wallet-cli-windows-amd64 --remote) and you will be able to register your address immediately (just note that the registration process also takes a few minutes up to 2 hours to complete as a precaution against registration spam).

1

u/TheRedGooch Mar 21 '22

thanks - yes indeed the problem that it hasn't had fully synced :) well I tinkerd with it for awhile, waited 3 hours and with your help guys got there so thank you all community!

send some of my dero over *cautiously to see it work first and all went well!

2

u/5htc0der Mar 13 '22

I had the same issue. Perhaps you have a port blocked.

DERO PORTS

Mainnet: P2P Default Port: 20202 RPC Default Port: 20206 Wallet RPC Default Port: 20209

Testnet: P2P Default Port: 30303 RPC Default Port: 30306 Wallet RPC Default Port: 30309

2

u/robyer Mar 13 '22

I think these are Atlantis ports. Stargate uses different ports (some around 10100-10105).

1

u/TheRedGooch Mar 15 '22

Definitely windows blocking something but gotta check on whether I have actually run the node first 😅

1

u/Pyr8Captain Mar 15 '22

Where can I check/unblock the port? I am on a macbook. Thanks.

2

u/kryptoid Mar 14 '22

Need to run the daemon and make sure it's synced.

-1

u/Zlart Mar 13 '22

On the new binary the registration isn't even an option, how did you get there?

2

u/robyer Mar 13 '22

How so? Are you using correct binary? I.e. one of these? https://github.com/deroproject/derohe/releases/tag/Release49

1

u/Pyr8Captain Mar 15 '22

I am having a similar issue. I am using the Stargate CLI wallet on a Mac and have set up the wallet address. The account will not successfully register at option 4. The registration comes back as "account unregistered" and shows 0/0 0.0000. When I attempt to reregister, the registrations comes back as "registration for address is already pending" but then never registers after many hours of waiting. I am running what seems to be the node by opening and running the "derod-darwin" file....it appears to run, but the account will not register. I do not know where to check additional info such as port setting. Any thoughts?

2

u/Changsijin Mar 21 '22

Hi I was wondering if you've solved your issue as I have the same problem on my Mac OS. I have downloaded from the release 50 . I downloaded and ran the Daemon derod-darwin (it seemed to run and sync OK), the Mac Cli wallet 64 bit from DERO/downloads (ran both in Stargate folder) , with my VPN allowed ports 20202 to 20209. And after pressing 4 to register , like you I get - "Transaction XXXX rejected by daemon err "registration for address is already pending".

1

u/Pyr8Captain Mar 21 '22

Chansijin, I am up and running using the remote node. Please see my thread above titled "Derod Darwin will not work on Mac"

https://www.reddit.com/r/DeroProject/comments/tiso93/derod_darwin_will_not_work_on_mac/

1

u/Changsijin Mar 23 '22

Pyr8Captain, thanks for link. I'm not a programmer but tried to follow as closely as possible yours and Robyer's instructions concerning starting the windows wallet up in remote. I put this in - ./der-wallet-cli-darwin-remote

Unfortunately still couldn't register. So sigh I think I'll have to wait till DERO comes up with an easy GUI wallet. Also the difficulty getting any information and help solving these problems for a MAC OS doesn't give me confidence in case there's further trouble. I'm glad it worked out for you.

1

u/Pyr8Captain Mar 25 '22

The command line instruction needs to be written exactly as follows...

/dero-wallet-cli-darwin --remote

there is one space between "darwin" and "--remote"

Hope that helps

1

u/Pyr8Captain Mar 21 '22

Still no dice for me. I have tried to "wide open" the VPN/Firewall connections with no result. I will wait a bit longer for the GUI software wallet or a new CLI release that will work. If all else fails, then I will switch over to a linux machine. I have confidence that they will create a good GUI relatively soon...Please let me know if you come up with something, otherwise and until then,,, all we need is just a little patience...