First Dawarich, now BTCPayServer!

[scooke]

I think I messed up something specific. I entered the IP for the Bitcoin node I have running elsewhere. Do I need to make a user, too, on that instance to login to the PRC?

And, I entered my.ip for the last item, explorer_bind, but I think that needed to stay as the local Docker IP, right> Well, I forget what that was. Could someone check and tell me what it should be please?

Bitcoin RPC Configuration

bitcoin:
rpc_user: "user"
rpc_password: "password"
rpc_host: "my.ip"
rpc_port: 8332
node_endpoint: "my.ip:8333"

Network Configuration

network: "mainnet"

Database Configuration (Cloudron managed)

These are automatically set by Cloudron environment variables

postgres:

host: ${CLOUDRON_POSTGRESQL_HOST}

port: ${CLOUDRON_POSTGRESQL_PORT}

username: ${CLOUDRON_POSTGRESQL_USERNAME}

password: ${CLOUDRON_POSTGRESQL_PASSWORD}

database: ${CLOUDRON_POSTGRESQL_DATABASE}

BTCPay Server Configuration

btcpayserver:
host: "${CLOUDRON_APP_DOMAIN}"
protocol: "https"
datadir: "/app/data/btcpayserver"

NBXplorer Configuration

nbxplorer:
network: "mainnet"
chaintype: "BTC"
explorer_port: 32838
explorer_bind: "WHAT WAS THIS:32838"

[nostrdev]

If you install bitcoin core, the btcpay server will automatically use your local (cloudron) instance

we didn't test the install against a remote server but your config looks good. Your IP is a regular IP right, not a domain?

  rpc_user: "bitcoin"
  rpc_password: "pass"
  rpc_host: "172.28.0.2"
  rpc_port: 8332
  node_endpoint: "172.28.0.2:8333"

The nbexplorer thing is internal to btcpay server (this was the hardest part about setting up the container)

Does your remote btc core instance have rpc enabled? something like this in your bitcoin.conf file:

rpcauth=bitcoin:pass

[scooke]

@nostrdev said in First Dawarich, now BTCPayServer!:

bitcoin.conf file

Yes, I'm using the IP of the server where the node is running. I made a rpc_user and password, but am not sure where to put it. They have an editable field, plus an editable app.env field... but no direction as to which file takes info like rpc_user, etc.

Thank you @nostrdev . This is the last thing, I think, stopping things from working... there is no bitcoin.conf! And though I know I have to make it, their setup is so niche that there also isn't a bitcoin directory, nor a .bitcoin directory, within which the conf file normally resides. I'm trying to figure out where to put it, if it is even called bitcoin.conf. Their docker-compose.yml AND docker-compose.json each reference so many locations, none of which are simply called "bitcoin" as a directory. Very frustrating!

Of course, I've posted help on the rt forums.... ONE person after days and days, who isn't even familiar with Bitcoin, tried to help. Pretty sad. I had more well-intentioned replies on a Reddit post within minutes. THIS is why I love Cloudron. It works, and if needed, help is not far.

[nostrdev]

any reason you can't just run your Bitcoin node on your cloudron instance? it's prunable, which means it won't take loads of space.

The rpc user/ pass definitely needs to be in the bitcoin.conf, it also needs to be salted/hashed, see: https://github.com/jlopp/bitcoin-core-rpc-auth-generator

[timconsidine]

@nostrdev maybe I should add bitcoin.core to CCAI ?

I didn't realise it was needed when I added BTCPayServer.

Maybe that will resolve @scooke issue, or help others.

Searching for a built docker image for bitcoin which Custom App Installer can use ....

EDIT #1 : found it at git.nostrdev.com/stuff/cloudron-bitcoin-core:latest

EDIT #2 : bitcoin core now added to ccai.appx.uk so both it and BTCpayserver can be installed. (untested currently)

[scooke]

@timconsidine Oh boy, now you've done it. Now I need to scrupulously go through my Cloudron and get rid of all the non-running fluff to make sure I have enough room to install this! I read somewhere that even if I run it pruned, it still needs to download the entire blockchain which is somewhere over 500GB+; it wasn't clear if the entire 500GB is downloaded, and then pruned, or if it prunes as it goes (so using 500GB in bandwidth but space-wise no more than you've set the prune).

[timconsidine]

@scooke ooops sorry

Well you could stick to your original approach and run it separately ?

[nostrdev]

Hi guys

The latest instance of core is in the playground: https://git.cloudron.io/playground/bitcoin (yes, it's a dependency for btcpay server)

It's true that the entire blockchain is always downloaded (consuming bandwidth) but you don't need more than your pruned size setting in terms of disk storage.

The package also contains instructions to allow you to set a volume, so that the blockchain is not part of your backups.

Happy to jump on a call to assist if needed

[timconsidine]

@scooke just out of interest, did you get Bitcoin Core installed ? Downloaded the data ?

What size did you decide to prune the data down to ?

My Bitcoin Core sync is almost complete, I set 3Gb prune, purely because I had no idea really what to prune it to.

Next stop : install BTC Payserver …

[scooke]

Hi @timconsidine You know, it never did finish downloading, or syncing, the node. It got stuck at 97%... something for which I found many other posts, and though solutions were offered, none ever worked with mine. I tried for weeks, waiting for an updated effort to produce fruit, always restarting before trying a new one, so I gave up. The whole point for me was to use it to use/accept Lightning payments for my Nostr account, but since the BTC node would never finish syncing, it was useless. I haven't tried since (that was my third attempt anyway in as many years). Oh well.

[timconsidine]

@scooke ah well maybe I will get stuck at 97-98. 96 currently.

[timconsidine]

@scooke my AI says that I might be able to transfer my 100% sync to you, and your system then catches up on changes, which are faster from a "seed".
But maybe you've moved on and don't need it anymore.
Let's see if I can get to 100%
Ai tells me the last few % are painfully slow, not that it's been very quick so far anyway !

[timconsidine]

Yay ! my Bitcoin Core data sync reached 100%