[angrybird]

Many thanks, seem I’ve modified the alert and look better.

[angrybird]

Alexg,

Thank you. I got it now.

[angrybird]

Alexg,

Very clear and great information. I still have a misunderstanding about this function.

Our model is :

Vendor: post item to our shop for sell
Customer: buy and purchase for the item
Payment method: Monero/BTC.

I’ve installed full node for all payment method. But during installation, it required a wallet for enable RPC.

When hand-over shop to the owner, how did they edit the default address of wallet receiver?

Their model is :

customer >> made payment >> site owner wallet >> after 2 weeks will send to Vendor’s wallet.

Please help to advise the correct configuration, I’ve checked in wallets_deposit but don’t see too much information. All it show is administrator’s wallet and can’t modify.

[angrybird]

Alexg,

I’ve done to resolve this issue by change port of from 18082 to another due to monerod has been owned this port and all thing working well. I have another question relating to wallet.

My customer hired my team to build a website and payment through XMR. For running, I created a wallet address at /coin/abc (abc is wallet name) but it’s not wallet address of website owner.
Could you please how him can change the address without touch to server or disclosure his wallet password? He only want to access to admin and change to his wallet address.

[angrybird]

Hi Alexg,

Please see:

nc -zv 127.0.0.1 18081
Ncat: Version 7.70 ( https://nmap.org/ncat )
Ncat: Connected to 127.0.0.1:18081.
Ncat: 0 bytes sent, 0 bytes received in 0.01 seconds.
–>> connected status.

netstat -tlupn |grep monero
tcp 0 0 0.0.0.0:18080 0.0.0.0:* LISTEN 4229/./monerod
tcp 0 0 127.0.0.1:18081 0.0.0.0:* LISTEN 4229/./monerod
tcp 0 0 127.0.0.1:18082 0.0.0.0:* LISTEN 4229/./monerod

I’ve tried with –daemon-adress before and saw:

./monero-wallet-cli –daemon-address 127.0.0.1:18081
This is the command line monero wallet. It needs to connect to a monero
daemon to work correctly.
WARNING: Do not reuse your Monero keys on another fork, UNLESS this fork has key reuse mitigations built in. Doing so will harm your privacy.

Monero ‘Nitrogen Nebula’ (v0.16.0.0-release)
Logging to ./monero-wallet-cli.log
Specify wallet file name (e.g., MyWallet). If the wallet doesn’t exist, it will be created.
Wallet file name (or Ctrl-C to quit): gy
Wallet and key files found, loading…
Wallet password:
Opened wallet: 43JEbYhRcPwVsacHt5dDxLLeqh9kNzRFY4eYpiPB1bR6TkdSMZyjA8AYfensaKs2MwLtZnwLN1NN2dxM1JgrvtGj28Jxx6d
**********************************************************************
Use the “help” command to see the list of available commands.
Use “help <command>” to see a command’s documentation.
**********************************************************************
Error: wallet failed to connect to daemon: 127.0.0.1:18081. Daemon either is not started or wrong port was passed. Please make sure daemon is running or change the daemon address using the ‘set_daemon’ command.
Background refresh thread started

and In monero-wallet-cli.log has this issue:

2020-06-22 10:25:11.891 7f83a82f27c0 INFO logging contrib/epee/src/mlog.cpp:273 New log categories: *:WARNING,net:FATAL,net.http:FATAL,net.ssl:FATAL,net.p2p:FATAL,net.cn:FATAL,global:INFO,verify:FATAL,serialization:FATAL,daemon.rpc.payment:ERROR,stacktrace:INFO,logging:INFO,msgwriter:INFO

Server has been reboot many times but still facing with this issue. Could you please advise.

[angrybird]

Hi Alexg,

I’ve successfully run monero daemon on server and saw it’s listening on the same port in rpc configure file. But when follow to your guy create wallet, it returned this error message:

Error: wallet failed to connect to daemon: 127.0.0.1:18081. Daemon either is not started or wrong port was passed. Please make sure daemon is running or change the daemon address using the ‘set_daemon’ command.

While Monero daemon still running and listen to this port. The next step also not complete with monero-wallet-rpc command at step (6) in this instruction: https://www.dashed-slug.net/bitcoin-altcoin-wallets-wordpress-plugin/monero-coin-adapter-extension/
The error message:

This is the RPC monero wallet. It needs to connect to a monero
daemon to work correctly.

Monero ‘Nitrogen Nebula’ (v0.16.0.0-release)
Logging to ./monero-wallet-rpc.log
2020-06-22 07:48:06.562 W Loading wallet…
2020-06-22 07:48:08.927 W Loaded wallet keys file, with public address: 43JEbYhRcPwVsacHt5dDxLLeqh9kNzRFY4eYpiPB1bR6TkdSMZyjA8AYfensaKs2MwLtZnwLN1NN2dxM1JgrvtGj2xxxxx
2020-06-22 07:48:09.432 E Blocks start before blockchain offset: 0 2092500
2020-06-22 07:48:09.585 E !m_blockchain.is_in_bounds(current_index). THROW EXCEPTION: error::out_of_hashchain_bounds_error
2020-06-22 07:48:09.833 E (m_blockchain.size() == stop_height || (m_blockchain.size() == 1 && stop_height == 0) ? false : true). THROW EXCEPTION: error::wallet_internal_error
2020-06-22 07:48:09.838 E Failed to setup background mining: BUSY
2020-06-22 07:48:09.839 I Binding on 127.0.0.1 (IPv4):18082
2020-06-22 07:48:12.179 F Error starting server: Failed to bind IPv4 (set to required)
2020-06-22 07:48:12.179 E Failed to initialize wallet RPC server

I’m sure all ports are listening but still have error. Wallet synchronization has been completed.

[Author]

Posts