Tabaffo

Ive removed RealTek driver and now all works, tnx! ps: I use jumbo because is only a 1to1 connection tnx guys!

Et voilà the diagnostics, tnx server-diagnostics-20250116-1354.zip

Hi, after upgrade at 7.0 I've no connection with my server. I can use my 10gbt lan connected to my computer, but I cant use a 1gbt lan connected with internet. So I cant check update etc. Screen attached. I've only updated, no other change at all.

Hi! Tnx for your job! I'm trying to run it under tor, is my first time with an node, so I'm a newbie. If I've understood right i've only to put the setting in my bitcoin.conf, right? Mine is like this: printtoconsole=1 # Only connect to peers via Tor. onlynet=onion But if I try to start the node I've this logs: 2024-02-11T11:43:53Z Bitcoin Core version v26.0 (release build) 2024-02-11T11:43:53Z InitParameterInteraction: parameter interaction: -onlynet excludes IPv4 and IPv6 -> setting -dnsseed=0 2024-02-11T11:43:53Z Using the 'x86_shani(1way,2way)' SHA256 implementation 2024-02-11T11:43:53Z Using RdSeed as an additional entropy source 2024-02-11T11:43:53Z Using RdRand as an additional entropy source 2024-02-11T11:43:53Z Default data directory /root/.bitcoin 2024-02-11T11:43:53Z Using data directory /root/.bitcoin 2024-02-11T11:43:53Z Config file: /root/.bitcoin/bitcoin.conf 2024-02-11T11:43:53Z Config file arg: onlynet="onion" 2024-02-11T11:43:53Z Config file arg: printtoconsole="1" 2024-02-11T11:43:53Z Command-line arg: printtoconsole="" 2024-02-11T11:43:53Z Using at most 125 automatic connections (40960 file descriptors available) 2024-02-11T11:43:53Z Using 16 MiB out of 16 MiB requested for signature cache, able to store 524288 elements 2024-02-11T11:43:53Z Using 16 MiB out of 16 MiB requested for script execution cache, able to store 524288 elements 2024-02-11T11:43:53Z Script verification uses 11 additional threads 2024-02-11T11:43:53Z scheduler thread start 2024-02-11T11:43:53Z Binding RPC on address ::1 port 8332 2024-02-11T11:43:53Z [libevent:warning] getaddrinfo: no address associated with nodename 2024-02-11T11:43:53Z Binding RPC on address ::1 port 8332 failed. 2024-02-11T11:43:53Z Binding RPC on address 127.0.0.1 port 8332 2024-02-11T11:43:53Z [http] creating work queue of depth 16 2024-02-11T11:43:53Z Using random cookie authentication. 2024-02-11T11:43:53Z Generated RPC authentication cookie /root/.bitcoin/.cookie 2024-02-11T11:43:53Z [http] starting 4 worker threads 2024-02-11T11:43:53Z Using wallet directory /root/.bitcoin 2024-02-11T11:43:53Z init message: Verifying wallet(s)… 2024-02-11T11:43:53Z Using /16 prefix for IP bucketing 2024-02-11T11:43:53Z init message: Loading P2P addresses… 2024-02-11T11:43:53Z Loaded 1883 addresses from peers.dat 7ms 2024-02-11T11:43:53Z init message: Loading banlist… 2024-02-11T11:43:53Z SetNetworkActive: true 2024-02-11T11:43:53Z Cache configuration: 2024-02-11T11:43:53Z * Using 2.0 MiB for block index database 2024-02-11T11:43:53Z * Using 8.0 MiB for chain state database 2024-02-11T11:43:53Z * Using 440.0 MiB for in-memory UTXO set (plus up to 286.1 MiB of unused mempool space) 2024-02-11T11:43:53Z init message: Loading block index… 2024-02-11T11:43:53Z Assuming ancestors of block 00000000000000000001a0a448d6cf2546b06801389cc030b2b18c6491266815 have valid signatures. 2024-02-11T11:43:53Z Setting nMinimumChainWork=000000000000000000000000000000000000000052b2559353df4117b7348b64 2024-02-11T11:43:53Z Opening LevelDB in /root/.bitcoin/blocks/index 2024-02-11T11:43:54Z Opened LevelDB successfully 2024-02-11T11:43:54Z Using obfuscation key for /root/.bitcoin/blocks/index: 0000000000000000 2024-02-11T11:43:54Z LoadBlockIndexDB: last block file = 0 2024-02-11T11:43:54Z LoadBlockIndexDB: last block file info: CBlockFileInfo(blocks=1, size=293, heights=0...0, time=2009-01-03...2009-01-03) 2024-02-11T11:43:54Z Checking all blk files are present... 2024-02-11T11:43:54Z Initializing chainstate Chainstate [ibd] @ height -1 (null) 2024-02-11T11:43:54Z Opening LevelDB in /root/.bitcoin/chainstate 2024-02-11T11:43:54Z Opened LevelDB successfully 2024-02-11T11:43:54Z Using obfuscation key for /root/.bitcoin/chainstate: 06805bf65eaf887c 2024-02-11T11:43:54Z Loaded best chain: hashBestChain=000000000019d6689c085ae165831a934ff763ae46a2a6c172b3f1b60a8ce26f height=0 date=2009-01-03T18:15:05Z progress=0.000000 2024-02-11T11:43:54Z Opening LevelDB in /root/.bitcoin/chainstate 2024-02-11T11:43:55Z Opened LevelDB successfully 2024-02-11T11:43:55Z Using obfuscation key for /root/.bitcoin/chainstate: 06805bfa5edf887c 2024-02-11T11:43:55Z [Chainstate [ibd] @ height 0 (000000000019d6689c085ae165831e934ff763ae46a2a6c172b3f1b60a8ce26f)] resized coinsdb cache to 8.0 MiB 2024-02-11T11:43:55Z [Chainstate [ibd] @ height 0 (000000000019d6689c085ae165831e934ff763ae46a2a6c172b3f1b60a8ce26f)] resized coinstip cache to 440.0 MiB 2024-02-11T11:43:55Z init message: Verifying blocks… 2024-02-11T11:43:55Z block index 2117ms 2024-02-11T11:43:55Z Setting NODE_NETWORK on non-prune mode 2024-02-11T11:43:55Z block tree size = 1 2024-02-11T11:43:55Z nBestHeight = 0 2024-02-11T11:43:55Z initload thread start 2024-02-11T11:43:55Z torcontrol thread start 2024-02-11T11:43:55Z Imported mempool transactions from disk: 0 succeeded, 0 failed, 0 expired, 0 already there, 0 waiting for initial broadcast 2024-02-11T11:43:55Z Bound to 127.0.0.1:8334 2024-02-11T11:43:55Z initload thread exit 2024-02-11T11:43:55Z Bound to [::]:8333 2024-02-11T11:43:55Z Bound to 0.0.0.0:8333 2024-02-11T11:43:55Z Loaded 0 addresses from "anchors.dat" 2024-02-11T11:43:55Z 0 block-relay-only anchors will be tried for connections. 2024-02-11T11:43:55Z init message: Starting network threads… 2024-02-11T11:43:55Z DNS seeding disabled 2024-02-11T11:43:55Z net thread start 2024-02-11T11:43:55Z opencon thread start 2024-02-11T11:43:55Z addcon thread start 2024-02-11T11:43:55Z msghand thread start 2024-02-11T11:43:55Z init message: Done loading And after hours I've this message: Potential stale tip detected, will try using extra outbound peer (last tip update: Do I have to install Tor separately? I've tried to install it (using obfs4-bridge) but I think this is a relay node not the thing I need to use the normal tor. At the end, If I try to run the node without bitcoin.conf all run very well, I see downloading blocks in the logs, so, for sure is a tor problem. I only want to run the node without make it public I'm running it. Any advice? help? tnx!

up

Hi, yesterday I was doing a restore with my software of backup (Kopia), where I've to put the destination folder instead insert "app/data/folder" I've insert only "/folder" and I've started the restore. Where can I find this folder? I've searched everywhere, my "data path" of Kopia is: "/mnt/user/" Tnx

Hi, I cant login with my account of unraid.net for doing a backup of my keys. I'm in a lifetime " Performing actions Please keep this window open while we perform some actions" Any suggestion?