Forum Replies Created
first, I must say that your plugin work perfectly. This was not a problem with the adapter, this was a Problem with VirtualBox where the wallets run.
Here is the solution why i cannot get an IPv4 :
“In the Settings for the VirtualBox VM, go to Network and then drop down the Advanced settings in the right-hand pane and check the “Adapter Type.” The default appears to be “Intel PRO/1000 MT Desktop (82540EM).” With that adapter type, I had the exact same problem, so I tried changing the Adapter Type to “Intel PRO/1000 MT Server (82545EM)” and then updating the /etc/network/interfaces file (if you change the adapter type before you install Ubuntu Server it should create the interfaces file with the correct info) and it now works fine. The version of VBox I’m using is 5.1.28 r117968 (Qt5.6.2) on a Windows 10 host and using Bridged networking.”deutsche-emarkParticipant
Thanks for the answer.
I have static IP 18.104.22.168
After some testings around I have figured out that if I use the IPv6, the adapter is responding but the padlock is closed. I’m unable to open the padlock and no address is generated.
Now I have disabled the IPv6 in the Router and restart the server. Now I have only IPv4. But the BTC Wallet adapter is not connecting to my Bitcoind.
Then I have installed the newest Dogecoind on my server. I see, that there are the same problems as Bitcoin. No remote connection under IPv4, responding under IPv6 but padlock closed.
The wp error log cannot help. There are errors like “Failed to connect to 22.214.171.124 port 8332: Connection refused” or “Could not get info about coin with symbol BTC: Adapter for “BTC” did not respond to the getnewaddress RPC command with a valid address string.”
Other Coins like Litecoin, Feathercoin or eMark running fine.