Show Posts
|
Pages: [1] 2
|
1
|
Bitcoin / Bitcoin Technical Support / ThreadRPCServer incorrect password attempt from 127.0.0.1:<port>
|
on: July 08, 2023, 04:42:21 PM
|
Hello, I have added the following parameters to bitcoin.conf: txindex=1 rest=1 There are requested by a third part application to run a blockchain explorer. Now in the Bitcoin Core file there are a lot of "ThreadRPCServer incorrect password attempt from 127.0.0.1<port>" errors, where port is different each time the error occurs. What does it mean?
|
|
|
2
|
Bitcoin / Bitcoin Technical Support / LN node: balances mismatch
|
on: February 14, 2023, 09:03:41 AM
|
I'm running lnd and I manage it using Thunderhub. I have opened 2 channels (1,3M and 1,0M as capacity) and I had to pay some fees for onchain txs, including extra fees for a CPFP tx for the first channel (using bumpfee command). Since the fees have been charged on BTC balance, shouldn't the total LN balance be 2,3M? Why instead I have this balance?  Missing 6689 sats...
|
|
|
3
|
Bitcoin / Electrum / Running Electrum server: what can I do now?
|
on: January 27, 2023, 09:33:12 AM
|
I'm running an Electrum server (under Tor) using electrs and I successfully connected an Electrum wallet to it.
Now, is it discoverable by others than me? How can I see if any client connect to my server?
|
|
|
4
|
Bitcoin / Bitcoin Technical Support / Bitcoin Core gets wrong bitcoin.conf file
|
on: January 21, 2023, 02:34:55 PM
|
I'm running bitcoin-qt without parameters and with the following settings in ".bitcoin/bitcoin.conf" file: datadir=/media/<my_user>/<external_hdd>/.bitcoin walletdir=/home/<my_user>/.bitcoin/wallets/test On a computer with Ubuntu it works like a charm: it gets blockchain data and wallet. On another computer with Linux Mint in which I copied the same Bitcoin Core (v24.0.1) and the same config folder, located in the same path (".bitcoin/bitcoin.conf"), when I launch bitcoin-qt (with no parameters) it gets the wrong bitcoin.conf file, using that is on the external disk and no wallet is loaded. What the hell is wrong???
|
|
|
5
|
Bitcoin / Bitcoin Technical Support / Can't reach my node
|
on: December 09, 2022, 10:23:12 PM
|
Hello, I'm using Bitcoin Core 24.0 on Ubuntu 20.04. I have installed tor 0.4.2.7-1 and made these changes to "/etc/tor/torrc": uncommented this: ControlPort 9051 CookieAuthentication 1 added this line: CookieAuthFileGroupReadable 1 I run Bitcoin Core with this command: bitcoind -conf=<my_path>/bitcoin.conf -proxy=127.0.0.1:9050 -debug=torHere is part of the debug.log file: 2022-12-09T21:41:56Z New outbound peer connected: version: 70016, blocks=766684, peer=0 (block-relay-only) 2022-12-09T21:41:57Z New outbound peer connected: version: 70016, blocks=766684, peer=1 (block-relay-only) 2022-12-09T21:42:02Z No valid UPnP IGDs found 2022-12-09T21:42:07Z New outbound peer connected: version: 70016, blocks=766684, peer=3 (outbound-full-relay) 2022-12-09T21:42:20Z Imported mempool transactions from disk: 3248 succeeded, 0 failed, 0 expired, 0 already there, 0 waiting for initial broadcast 2022-12-09T21:42:20Z loadblk thread exit 2022-12-09T21:42:28Z New outbound peer connected: version: 70016, blocks=766684, peer=4 (outbound-full-relay) 2022-12-09T21:42:37Z New outbound peer connected: version: 70016, blocks=766684, peer=7 (outbound-full-relay) 2022-12-09T21:42:39Z P2P peers available. Skipped DNS seeding. 2022-12-09T21:42:39Z dnsseed thread exit 2022-12-09T21:43:03Z Socks5() connect to 2001:41d0:700:2052:::8333 failed: general failure 2022-12-09T21:43:04Z New outbound peer connected: version: 70016, blocks=766684, peer=9 (outbound-full-relay) 2022-12-09T21:43:30Z New outbound peer connected: version: 70016, blocks=766684, peer=13 (outbound-full-relay) 2022-12-09T21:43:32Z New outbound peer connected: version: 70016, blocks=766684, peer=14 (outbound-full-relay) 2022-12-09T21:43:34Z New outbound peer connected: version: 70016, blocks=766684, peer=15 (outbound-full-relay) 2022-12-09T21:43:35Z New outbound peer connected: version: 70016, blocks=766684, peer=16 (outbound-full-relay) 2022-12-09T21:44:37Z New outbound peer connected: version: 70016, blocks=766684, peer=17 (outbound-full-relay) 2022-12-09T21:45:38Z New outbound peer connected: version: 70016, blocks=766684, peer=18 (outbound-full-relay) 2022-12-09T21:47:10Z No valid UPnP IGDs found For "No valid UPnP IGDs found" message I have commented upnp=1 line in bitcoin.conf file, but I'm still getting Socks5() connect to ... failed: general failure. Can you tell me what that address (2001:41d0:700:2052:::8333) came from? I also tried to connect Electrum to it with the following command: electrum -1 -s <my_address>.onion:8333:t -p socks5:localhost:9050 but it hangs on "not connected"... What am I missing?
|
|
|
7
|
Bitcoin / Bitcoin Technical Support / bitcoind.pid instance file is not being created
|
on: November 29, 2022, 05:05:03 PM
|
Hello, I have installed Bitcoin Core on Ubuntu 20 and I changed the path of ".bitcoin" folder. When I run "bitcoind" file it does not create "bitcoind.pid" file, as instead it does on another computer. Since the current instance file is not created the client crashes: 2022-11-29T16:56:38Z Bitcoin Core version v23.0.0 (release build) 2022-11-29T16:56:38Z Assuming ancestors of block 000000000000000000052d314a259755ca65944e68df6b12a067ea8f1f5a7091 have valid signatures. 2022-11-29T16:56:38Z Setting nMinimumChainWork=00000000000000000000000000000000000000002927cdceccbd5209e81e80db 2022-11-29T16:56:38Z Using the 'arm_shani(1way,2way)' SHA256 implementation 2022-11-29T16:56:38Z Default data directory /root/.bitcoin 2022-11-29T16:56:38Z Using data directory /mnt/media/<UUID>/.bitcoin 2022-11-29T16:56:38Z Config file: /mnt/media/<UUID>/.bitcoin/bitcoin.conf 2022-11-29T16:56:38Z Config file arg: bind="0.0.0.0" 2022-11-29T16:56:38Z Config file arg: checkblocks="24" 2022-11-29T16:56:38Z Config file arg: checklevel="0" 2022-11-29T16:56:38Z Config file arg: dbcache="64" 2022-11-29T16:56:38Z Config file arg: disablewallet="1" 2022-11-29T16:56:38Z Config file arg: listen="1" 2022-11-29T16:56:38Z Config file arg: maxconnections="64" 2022-11-29T16:56:38Z Config file arg: par="2" 2022-11-29T16:56:38Z Config file arg: port="8333" 2022-11-29T16:56:38Z Config file arg: rpcallowip="127.0.0.1" 2022-11-29T16:56:38Z Config file arg: rpcbind=**** 2022-11-29T16:56:38Z Config file arg: rpccookiefile="/root/bitcoin-core/.bitcoin/.cookie" 2022-11-29T16:56:38Z Config file arg: rpcport="8332" 2022-11-29T16:56:38Z Config file arg: upnp="1" 2022-11-29T16:56:38Z Command-line arg: conf="/mnt/media/<UUID>/.bitcoin/bitcoin.conf" 2022-11-29T16:56:38Z Command-line arg: daemon="" 2022-11-29T16:56:38Z Command-line arg: datadir="/mnt/media/<UUID>/.bitcoin" 2022-11-29T16:56:38Z Using at most 64 automatic connections (32768 file descriptors available) 2022-11-29T16:56:38Z Using 16 MiB out of 32/2 requested for signature cache, able to store 524288 elements 2022-11-29T16:56:38Z Using 16 MiB out of 32/2 requested for script execution cache, able to store 524288 elements 2022-11-29T16:56:38Z Script verification uses 1 additional threads 2022-11-29T16:56:38Z Wallet disabled! 2022-11-29T16:56:38Z scheduler thread start 2022-11-29T16:56:38Z HTTP: creating work queue of depth 16 2022-11-29T16:56:38Z Using random cookie authentication. 2022-11-29T16:56:38Z Unable to open cookie authentication file /root/bitcoin-core/.bitcoin/.cookie.tmp for writing 2022-11-29T16:56:38Z Error: Unable to start HTTP server. See debug log for details. 2022-11-29T16:56:38Z Shutdown: In progress... 2022-11-29T16:56:38Z scheduler thread exit 2022-11-29T16:56:38Z Shutdown: done Do you see any useful hint in this log file? Why the client still use default data directory for some paths? What could be the problem? I have also tried versione 24.0, but nothing changed.
|
|
|
11
|
Alternate cryptocurrencies / Service Discussion (Altcoins) / Crypto.org DeFi Wallet
|
on: June 03, 2021, 08:52:12 AM
|
Hello, I open this thread about Crypto.org DeFi Wallet, I have tried to search for it here on forum but I can't see any topic about it. I have 2 questions now: - For staking CRO I have need to swap from Ethereum to buy CRO ERC20 token and then use migration tool to have native CRO. Couldn't I directly buy native CRO from DeFi Wallet and then save fees? How to do that? - I finally staked native CRO tokens... but after some hours I get this message: "This validator is currently being jailed". Have I to do anything to "unjail" it?  Thank you.
|
|
|
12
|
Bitcoin / Electrum / RBF feature on 4.0.2?
|
on: February 12, 2021, 10:04:40 AM
|
Hello, I have sent a transaction with low fee (5 sat/byte) and it is a couple of hours that is unconfirmed. I see that since Electrum 4.0.4 there is the RBF feature. I have Electrum 4.0.2 and I see an option in the contextual menu related to transaction to set an high fee. Is it the RBF feature?
|
|
|
14
|
Bitcoin / Electrum / Electrum 3.3.4 doesn't start (Linux)
|
on: April 24, 2019, 01:41:31 PM
|
Hello, I'm on Ubuntu and I have upgraded my Electrum wallet from 3.2.3 to 3.3.4. Now if I run it from the application menu it doesn't start anymore. If I try from the command line, I get the following error: ~$ electrum Error: No module named 'aiorpcx'. Try 'sudo python3 -m pip install <module-name>'
~$ sudo python3 -m pip install aiorpcx Requirement already satisfied: aiorpcx in ./.local/lib/python3.6/site-packages Requirement already satisfied: attrs in ./.local/lib/python3.6/site-packages (from aiorpcx)
~$ electrum Error: No module named 'aiorpcx'. Try 'sudo python3 -m pip install <module-name>'
What could I do to fix it?
|
|
|
17
|
Bitcoin / Bitcoin Discussion / How to run Bitcoin Core behind corporate proxy?
|
on: January 30, 2018, 03:59:30 PM
|
Hello, I'm running Bitcoin Core on TestNet and I would like to set a proxy. Since I'm using Squid to set proxy for my system I should set "localhost:3128" somewhere... but bitcoin-qt options have only SOCK5 proxy field.  So, it can't connect... How can I solve? Thank you in advance.
|
|
|
18
|
Bitcoin / Electrum / Using Electrum on TestNet under corporate proxy
|
on: January 30, 2018, 12:43:24 PM
|
Hello, I'm trying to make my Electrum connect to server but I'm experiencing problems. I installed versione 3.0.5 and run it in TestNet mode (`--testnet`). I filled the proxy settings with my data but it stucks on "Not connected" or "Waiting for fee estimates"...  I also tried to connect it manually, but none works. What could be the problem? Does exist any log to see to figure out why it is not connecting to any server?
|
|
|
19
|
Local / Italiano (Italian) / Notizie spazzatura su bitcoin/blockchain
|
on: November 03, 2017, 08:22:21 AM
|
Ieri sono venuto a conoscenza di questo topic grazie alla segnalazione dell'utente Micio. Avrei voluto aggiungere tutti gli articoli, maggiormente pubblicati su edizioni cartacee, che mi è capitato di incontrare negli ultimi mesi, ma il topic è chiuso. Apro dunque quest'altro thread in cui magari continuare a raccogliere questo genere di articoli "spazzatura" e farci due risate!
|
|
|
|