Closed kosuodhmwa closed 5 months ago
this is really a bug, so the current version is "buggy by default" ?
or do i need to change the PHP version to 7.3, not higher?
???
If you run with docker add the following in your bitcoin.conf :
rpcallowip=172.0.0.0/8 rpcallowip=10.0.0.0/8 rpcallowip=192.0.0.0/
Try also to set Config.php RPC_IP to local server IP addr instead of 127.0.0.1
Thanks, but i don't use docker
Then your rpc credentials are wrong, be sure that they are in bitcoin.conf. In the bitcoin logs you must see an invalid password attempt.
no
Still the same issue after 2 months with installed new versions. Why?
This
Maybe somebody knows a good alternative to https://github.com/Mirobit if they don't move up...?
THank you for your feedback(s) ;-)
Additional info from bitcoind screens logs:
PAssword is EXACTLY the same WTF (you see that in screenshots above)
Maybe i need to put it in quotes in bitcoin.conf??
Can you try it without spaces before and after the =
?
Btw i recomend to use rpcauth, not rpcuser and rpcpassword. https://jlopp.github.io/bitcoin-core-rpc-auth-generator/
Same... :-(
<Btw i recomend to use rpcauth, not rpcuser and rpcpassword. https://jlopp.github.io/bitcoin-core-rpc-auth-generator/> - thx, but user/pw auth shoud also work. At least theoretically... ;-)
i can also send the whole Oracle VirtualBox Debian 12.5 VM for debug purposes to @Mirobit if you want... it's not big when i subtract the .bitcoin data dir which contains the blockchain (.bitcoin is a symlink to another drive [than the OS drive] configured in VirtualBox VM settings)
Wait, i just realize why did u use rpcpass
? its rpcpassword
thank you very much. i also read about
Config.php:
// RPC username / rpcauth specified in bitcoin.conf const RPC_USER = "myuser"; // RPC password / rpcauth specified in bitcoin.conf const RPC_PASSWORD = "mypass";
bitcoin.conf:
proxy=127.0.0.1:9050 listen=1 bind=127.0.0.1
server = 1 rpcallowip = 127.0.0.1 rpcport = 8332 rpcuser = myuser rpcpass = mypass txindex = 1
PHP Version is 8.2.x