First Dawarich, now BTCPayServer!
-
Thanks to @timconsidine and his https://ccai.appx.uk/ I've installed BTCPayServer. Quick questions...
The Dashboard tells me the nodes are syncing... but there are NO nodes, correct, by default? I need to connect it to a Bitcoin node elsewhere, yes? I ask because I don't want to wake up tomorrow to find out my server has run out of space!
Any other tips on how to connect that BTC node, as well as Lightning stuff?
Thank you!
-
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" -
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 -
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@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.
-
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
-
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
@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)
-
@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)
@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 it an 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).