![]() ![]() I have now updated the instructions on the adapter’s homepage. It appears my installation instructions are outdated, so please accept my apologies hope you didn’t waste too much time on this. I tested again with Monero 0.16.0.0 and I got the same result. Server has been reboot many times but still facing with this issue. 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,:ERROR,stacktrace:INFO,logging:INFO,msgwriter:INFO Use “help ” to see a command’s documentation.Īnd In monero-wallet-cli.log has this issue: Use the “help” command to see the list of available commands. Opened wallet: 43JEbYhRcPwVsacHt5dDxLLeqh9kNzRFY4eYpiPB1bR6TkdSMZyjA8AYfensaKs2MwLtZnwLN1NN2dxM1JgrvtGj28Jx圆d If the wallet doesn’t exist, it will be created. Specify wallet file name (e.g., MyWallet). WARNING: Do not reuse your Monero keys on another fork, UNLESS this fork has key reuse mitigations built in. I’ve tried with –daemon-adress before and saw: Ncat: 0 bytes sent, 0 bytes received in 0.01 seconds. Check with netcat (nc) as shown above, to make sure the local port is open. In summary, it’s clear that monero-wallet-cli is looking for the daemon at 127.0.0.1 and port 18081 and it’s not finding it. If necessary, reboot your server to make sure that you don’t run any duplicate processes. Some times there are more than one processes running, and only the first one can get a hold of a TCP listen port. Is the daemon running on the same server as the machine where you’re running monero-wallet-cli? If not, use monero-wallet-cli with -daemon-address to specify a different IP/port pair, but in that case you’d need to check your firewalls too. You can check if the daemon port is open with nc -zv 127.0.0.1 18081 Ideally you should set up a service to make sure it’s always running. Here’s some thoughts:Īre you sure the daemon is still running? It should be listening on 18081 by default. In this case, you’re running the daemon, but monero-wallet-cli cannot connect to the daemon to create a new wallet. Focus on completing each step before continuing to the next. It looks like you haven’t managed to create a wallet yet (step 3), so there’s no point in attempting any more steps. ![]() ![]() Wallet synchronization has been completed. I’m sure all ports are listening but still have error. 07:48:12.179 E Failed to initialize wallet RPC server 07:48:12.179 F Error starting server: Failed to bind IPv4 (set to required) 07:48:09.838 E Failed to setup background mining: BUSY THROW EXCEPTION: error::wallet_internal_error THROW EXCEPTION: error::out_of_hashchain_bounds_error 07:48:08.927 W Loaded wallet keys file, with public address: 43JEbYhRcPwVsacHt5dDxLLeqh9kNzRFY4eYpiPB1bR6TkdSMZyjA8AYfensaKs2MwLtZnwLN1NN2dxM1JgrvtGj2xxxxx Monero ‘Nitrogen Nebula’ (v0.16.0.0-release) The next step also not complete with monero-wallet-rpc command at step (6) in this instruction: While Monero daemon still running and listen to this port. Please make sure daemon is running or change the daemon address using the ‘set_daemon’ command. Daemon either is not started or wrong port was passed. But when follow to your guy create wallet, it returned this error message:Įrror: wallet failed to connect to daemon: 127.0.0.1:18081. I’ve successfully run monero daemon on server and saw it’s listening on the same port in rpc configure file. WooCommerce Cryptocurrency Payment Gateway extension support forum.Monero Wallet Adapter extension support.Wallet Adapter extension support forum.HOWTO: Choose between available wallet adapters.WooCommerce Cryptocurrency Payment Gateway extension.Bitcoin and Altcoin Wallets WordPress plugin. ![]()
0 Comments
Leave a Reply. |