BTCpayserver

[timconsidine]

@nostrdev I'm trying to install btcpayserver after installing btc-core (and node fully synced)

I change the rpc auth in btcpayserver config.yml to match what is in btc-core bitcoin.conf

I restarted btcpayserver

I get a blank page on btcpay.domain.tl in Safari and a 500 error in Firefox.

btcpayserver logs :
Jan 07 16:57:24 fail: Microsoft.AspNetCore.Server.Kestrel: Connection id "0HNIE1J43J819", Request id "0HNIE1J43J819:00000001": An unhandled exception was thrown by the application.

I tried to set sysctl values but they're in RO location so will need a rebuild if wrong

Am I doing something wrong ?

Using https://git.nostrdev.com/stuff/cloudron-btcpay

[robi]

@timconsidine awesome, how much space does btc-core take up fully synced?

[nostrdev]

@timconsidine when you say the config matches, you mean this part right?

# Bitcoin RPC Configuration
bitcoin:
  rpc_user: "bitcoin"
  rpc_password: "xxxxx"

Note that the rpc_password should be the actual password, NOT the rpcauth= value in the bitcoin.conf file (which is derived from the password)

[nostrdev]

@robi for info, this is a non-pruned (full) node, as of today:

root@d1f00579-9662-4a14-896e-cf7cd8127709:/media/core# ls
banlist.json  bitcoind.pid  blocks  chainstate  debug.log  fee_estimates.dat  peers.dat  settings.json
root@d1f00579-9662-4a14-896e-cf7cd8127709:/media/core# du -sh
766G    .
root@d1f00579-9662-4a14-896e-cf7cd8127709:/media/core# 

[robi]

@nostrdev thanks, good to know.

You know the next question..

Pruned?

And is it sync-able already pruned?

I can't install it if it's not..

[timconsidine]

@robi I pruned mine to 3Gb
I think somewhere I read pruning down to 600Mb might be possible. Maybe not lower.

[timconsidine]

@nostrdev thank you

Yes, I used the password value printed below that line as a comment.

I will dig bit deeper later

[LoudLemur]

It seems that we are very nearly there with BTCpayserver. Lets wrap up this project and publish it officially on cloudron.

Here are the main improvements on BTCserver just over the past year (2025):

BTCPay Server Main Improvements (Jan 2025 - Jan 2026)

POS & Checkout

• Tax rates applied to items with breakdowns in checkout/receipts
• Improved total breakdown, receipts, and cart views
• POS reports now include tips/subtotals
• Numeric keypad shows input amount (not total); item list support
• Receipts displayable in iframes; hide back-to-store link in iframes
• Disable zero-amount invoices; improved mobile UX

Wallet & Transactions

• Wallet policy output descriptors (BIP388/389) and Taproot signing (BIP86) for hardware wallets
• RBF sweeping transactions and CPFP UX improvements
• Manual coin selection with advanced filters ("Clear All")
• Browse generated addresses; fiat amount previews in tx details
• Tx fee/fee rate info; exchange rate tracking; additional rates via store settings
• BBQr PSBT support (up to 16MB); improved PSBT error messages

API & Greenfield

• New webhooks: InvoiceExpiredPaidPartial, InvoicePaidAfterExpiration
• amountPaid on invoices; email settings endpoint
• Subscriptions API; store users API (update/retrieve by ID/email)
• Payment requests link to external invoices (e.g., QuickBooks) via Reference ID
• PoS data without auth; payout methods optional for pull payments
• Histograms with Lightning data; image upload for app items

Reporting & Invoices

• Renamed/reordered invoice report columns; export all metadata
• Payment request reports with improved filtering
• Refund reports; "Reporting" button for quick access
• Responsive UI; sales stats filter to paid invoices only
• Admin can view users' invoices; manual payout state transitions (InProgress → AwaitingPayment)

Subscriptions & Automation

• Recurring payments with reminders; prefilled subscriber email
• Ambassadors can monetize server access
• Installable backend language packs
• Advanced server email rules (conditions, placeholders, CC/BCC)

UI/UX & Accessibility

• Custom HTML meta tags/lang for SEO (crowdfund/PoS)
• Improved hardware wallet import (no confirm addresses page; auto-label by model)
• Dashboard tweaks (remove store headline, hide LN balance for non-admins)
• Tooltip/link for pull-payment tags; copy link button
• Auto-disable crashed plugins; cleanup expired data

Integrations & Providers

• Phoenixd, Coinmate (CZK), Kraken (CAD), Yadio, Norwegian exchanges (Bitmynt/Bare Bitcoin)
• Fallback rate sources; rate providers configurable
• Shopify integration deprecation warning + new plugin link
• Multisig flow improvements (BTCPay-only users); confirmation prompts

Bug Fixes & Reliability

• RBF label consistency; fee rate crashes; Yadio rate lookup
• Archived invoices private; status filter 500 errors
• Lightning payment detection post-connection string swap
• Vault signing for large PSBTs; pending payouts on unresponsive LN
• Notifications API crashes; Boltcard reset issues; escaped HTML in UTXOs
• Zero-amount payment requests; receipt options from store settings

Sources: GitHub releases (up to v2.3.3), Changelog.md. Full notes: Releases.

[nostrdev]

BTCPayServer has now been updated to v2.3.3 (from 2.1.6)

Tested on our instance and it's running fine

https://git.cloudron.io/playground/btcpayserver/

[timconsidine]

@nostrdev just checking in

• what are the latest current versions of BTCCore and BTCPayserver ?
• any plans to make BTCPayServer into a Community App Release ?

I have BTCCore running but BTCPayServer is not responding. Just wanted to check in before I invest time in resolving.

[nostrdev]

Hi @timconsidine

BTC Core is v29 and it should not be updated. There were contentious changes added in v30, and to be pragmatic, it would be best to stick with v29 for the foreseeable future. This does not affect BTCPay Server.

About the community app release, can you give more details? What would need to happen?

BTC Pay Server should run independently of BTC Core (the core part is only needed when you set up the wallet within a shop). So if it is not responding, it is not due to Core.

[timconsidine]

@nostrdev thank you !

BTC Core is running 29.0.0 and is fully synced to network

About the community app release, can you give more details? What would need to happen?

Community Apps are a new feature of Cloudron 9.1.3.
https://docs.cloudron.io/packaging/publishing

A Community App is a custom app which does not have to be accepted into the official AppStore, but the user can install it almost as if it were.

Community App can be made with some simple additional steps to a traditional custom app :

• make sure you are on 9.1.3
• in project directory run cloudron versions init
• ensure extra fields in CloudronManifest.json are populated
• ensure you use a CHANGELOG or CHANGELOG.md file (specified in CloudronManifest.json)
• build as normal
• run cloudron versions add
• the populated CloudronVersions.json can be shared (git repo, static website, or static link here in forum even)

User can use that link to install the Community App to their Cloudron instance. It's sweet !

My BTC Core is working and I can get a curl response from it.

My BTC Pay does not login, I must have screwed up the config.yaml, investigating it.

[LoudLemur]

Well done!