cypherstack / stack_wallet

Stack Wallet, a multicoin, cryptocurrency wallet
https://stackwallet.com
GNU General Public License v3.0
217 stars 61 forks source link

Bug: Unable to use local XMR node through monerod #996

Closed GhostDog98 closed 2 months ago

GhostDog98 commented 2 months ago

Is there an existing issue for this?

Current Behavior

When connecting to a locally hosted monero node, i see the following traffic: Stack sends SYN to server Server responds with [RST, ACK]

Stack wallet says server is offline. My cmdline options for my server are: ./monerod --restricted-rpc --rpc-login redacted:redacted --data-dir ./

And my node details are: Node name: test Url: http://192.168.0.123 Port: 18081 Login: redacted Password: redacted

On the server, I have ports 18081, 18080, and 18089 set to ALLOW. Both the devices are on the same subnet and can clearly communicate, as I can contact a web server hosted on the same host.

Expected Behavior

I put in the details and it works.

Reproduce Steps

Run a node using monerod: ./monerod --restricted-rpc --rpc-login redacted:redacted --data-dir ./ Open up ports 18080, 18081, and 18089 using ufw allow <port> Connect via stack wallet Stack wallet fails to connect

Environment

Server Env:

Stack env:

Logs

No response

Further Information

No response

sneurlax commented 2 months ago

This is probably related to RPC authentication: https://github.com/cypherstack/stack_wallet/issues/981

sneurlax commented 2 months ago

Been working on this, RPC authentication has just been a stumbling-block

GhostDog98 commented 2 months ago

This is probably related to RPC authentication: #981

I believe this is a separate issue, as when running the server using ./monerod --data-dir ./ it still fails, and i am never getting a prompt for the certificate, which suggests a failure earlier in the connection attempt. Here's some more diagnostics should they help:

Currently waiting for monerod to fully sync with the chain, i'll run an nmap after it does...

Edit/Update for nmap: Running nmap from client to server returns that 18080 is open, but 18081 and 18089 are closed. Running with the server enabled rpc, i get the same results, despite the fact that 18081 should be open?

GhostDog98 commented 2 months ago

Ended up fixing my issue, twas a skill issue afterall; ./monerod --restricted-rpc --rpc-bind-port 18081 --rpc-bind-ip <local ipv4 address> --confirm-external-bind --rpc-login <username>:<login> --data-dir ./ is the command you want to use if you are communicating over local network.