btcpayserver / btcpayserver-docker

Docker resources for hosting BTCPayServer easily

BTCPay Server

Accept Bitcoin payments ₿

BTCPay Server is a free and open-source Bitcoin payment processor which allows you to accept bitcoin without fees or intermediaries.

Website | Documentation | API | Contribute | YouTube | Chat

_{"This is lies, my trust in you is broken, I will make you obsolete" 💚}

View Demo · Report a bug · Request a feature · FAQ

💼 Table of Contents

• Features
• Getting Started
• Documentation
• Contributing
• Developing
  • API
• Community
• License
• Supporters

🎨 Features

• Direct, peer-to-peer Bitcoin payments
• No transaction fees (other than the network fee)
• No fees, middleman or KYC
• Non-custodial (complete control over the private key)
• Enhanced privacy & security
• Self-hosted
• SegWit support
• Lightning Network support (LND, Core Lightning (CLN), Eclair)
• Tor support
• Share your instance with friends (multi-tenant)
• Invoice management and Payment requests
• Apps: Point of sale, crowdfunding, donation button
• Full-node reliant wallet with hardware wallet integration and SegWit support
• Bitcoin-only build, separate community-maintained altcoin build (supported altcoins)

🚀 Getting Started

Firstly, decide if you want to host an instance yourself or use a third-party host. If you've chosen to self-host, there are plenty of documented ways to deploy BTCPay Server.

After successful deployment, make sure to check our getting started and walkthrough guides. In case you would like to use Lightning Network, see Lightning guide.

📗 Documentation

Please check out our official website, complete documentation and FAQ for more details.

If you have trouble using BTCPay Server, consider joining communities listed on the official website to get help from other contributors. Only create a GitHub issue for technical issues you can't resolve through other channels or feature requests you've validated with other members of the community.

🤝 Contributing

BTCPay Server is built and maintained entirely by volunteer contributors around the internet. We welcome and appreciate new contributions.

If you're a developer looking to help, but you're not sure where to begin, check the good first issue label, which contains small pieces of work that have been specifically flagged as being friendly to new contributors.

Contributors looking to do something a bit more challenging, before opening a pull request, please join our community chat or start a GitHub discussion to get early feedback, discuss the best ways to tackle the problem, and ensure there is no work duplication.

There are many other ways to get involved with the project. Check our contribution guidelines. To get the big-picture of the project development, visit our evolving roadmap.

🧑‍💻 Developing

To begin developing locally, visit our local development guide. There are also several video-tutorials:

• Setting up development environment on Windows
• Setting up development environment Linux (Ubuntu)
• Setting up development environment MacOS

How to build

While the documentation advises using docker-compose, you may want to build BTCPay Server yourself.

First, install .NET SDK v8.0 as specified by the Microsoft website.

On Powershell:

.\build.ps1

On linux:

./build.sh

How to run

Use the run scripts to run BTCPay Server, this example shows how to print the available command-line arguments of BTCPay Server.

On Powershell:

.\run.ps1 --help

On linux:

./run.sh --help

How to debug

If you want to debug, use Jetbrain's Rider or Visual Studio 2022.

You need to run the development time docker-compose as described in the test guide.

You can then run the debugger by using the Launch Profile Docker-Regtest.

If you need to debug ledger wallet interaction, install the development time certificate with:

# Install development time certificate in the trust store
dotnet dev-certs https --trust

Then use the Docker-Regtest-https debug profile.

Other dependencies

For more information, see the documentation: How to deploy a BTCPay Server instance.

🧪 API

BTCPay Server has two APIs:

• Greenfield API (New)
  • Greenfield API documentation
  • Greenfield API examples with CURL
• Legacy API

The Greenfield API is our brand-new API which is still in development. Once complete, it will allow you to run BTCPay Server headlessly. The Legacy API, is fully compatible with BitPay's API. It has limited features, but allows instant migration from BitPay.

💚 Community

Our community is the ❤️ of the project. To chat with other community members in real-time, join our Mattermost chat. We're also on GitHub discussions.

📝 License

BTCPay Server software, logo and designs are provided under MIT License.

🙏 Supporters

The BTCPay Server Project is proudly supported by these entities through the BTCPay Server Foundation.

If you'd like to support the project, please visit the donation page.

btcpayserver-docker's Issues

Create automated backup

Leverage https://github.com/blacklabelops/volumerize

Unable to connect to host: Failed to connect before the deadline

I've the BTCPay server up and running (fabulous bit of software by the way). It sits behind my apache server and as far as I can tell it works (https://btcpay.flat18.co.uk). SSL is a wildcard and appears to work just fine.

Following the instructions for linking the Zap client to BTCPay, I get the error in the title.

Zap version 0.2.2-beta (0.2.2-beta.4225) (macOS)

BTCPay version v1.0.2.103 Docker / Ubuntu 18.04LTS / Apache2

Constant 500 Internal Server Error

Despite having correct configuration settings, and despite restarting everything, I'm still getting 500 Internal Server Error - all HTTP connections are redirected to HTTPS.

Error from docker logs for letsencrypt instance:

Creating/renewal btcpay.nodecheck.io certificates... (btcpay.nodecheck.io)
2019-01-17 08:50:56,081:INFO:simp_le:1479: Generating new certificate private key
2019-01-17 08:51:00,919:ERROR:simp_le:1446: CA marked some of the authorizations as invalid, which likely means it could not access http://example.com/.well-known/acme-challenge/X. Did you set correct path in -d example.com:path or --default_root? Are all your domains accessible from the internet? Please check your domains' DNS entries, your host's network/firewall setup and your webserver config. If a domain's DNS entry has both A and AAAA fields set up, some CAs such as Let's Encrypt will perform the challenge validation over IPv6. If your DNS provider does not answer correctly to CAA records request, Let's Encrypt won't issue a certificate for your domain (see https://letsencrypt.org/docs/caa/). Failing authorizations: https://acme-v01.api.letsencrypt.org/acme/authz/yyuBsA2i8cdTx33AnZk69brkFncK2G9cRPd02eGbsj0
Challenge validation has failed, see error log.

I have never used example.com for configuring this, I had set all the parameters prior to setting it up, and yet it constantly fails. My parameters:

export BTCPAY_HOST="btcpay.nodecheck.io"
export NBITCOIN_NETWORK="mainnet"
export BTCPAYGEN_CRYPTO1="btc"
export BTCPAYGEN_REVERSEPROXY="nginx"
export BTCPAYGEN_LIGHTNING="lnd"
export BTCPAY_PROTOCOL="https"
export BTCPAY_HOST_SSHKEYFILE="/root/.ssh/id_rsa_btcpay"

What can I do to finally get this working, and get btcpay accessible? Seems to be something with nginx making the 500 errors, so just need to get nginx working properly.

`Status Code: 404; Not Found` with pay button

I run my own server at https://sosthenebtcpay.pw, I did an update about 30 min ago.
I want to try the pay button, so I copied the following lines of code in a dummy page of my blog https://www.sosthene.net/Dons/ :

<form method="POST" action="https://sosthenebtcpay.pw/stores/2uZB4Ud6LQVhRCNxq1wAphjhMNPhokXRdVJ8dpADSrpy/pay">
    <input type="hidden" name="price" value="0.00000100" />
    <input type="hidden" name="currency" value="BTC" />
    <input type="hidden" name="checkoutDesc" value="Tip" />
    <input type="image" src="https://sosthenebtcpay.pw/img/paybutton/pay.png" name="submit" style="width:209px" alt="Pay with BtcPay, Self-Hosted Bitcoin Payment Processor">
</form>

When I click on the button, I open the page https://sosthenebtcpay.pw/stores/2uZB4Ud6LQVhRCNxq1wAphjhMNPhokXRdVJ8dpADSrpy/pay
The page is blank with a Status Code: 404; Not Found error.

Expand pruning to other crypto nodes

We need to allow pruning to other crypto nodes. Guessing we should add a key to the crypto definition file at this point? We should also duplicate the exisitng btc ones to have fragments starting with btc-* to scale. :)

Server not accessible on https

Background

I've deployed the server using docker-compose and the front-end is accessible via http. The issues are the links for the css are expecting https, resulting in the front-end is displaying correctly and nginx returns 500 errors when trying to access https://<domain>

Your environment

• Ubuntu 18.04 x64

Steps to recreate

apt-get update && apt-get install -y git

git clone https://github.com/btcpayserver/btcpayserver-docker
cd btcpayserver-docker

export BTCPAY_HOST="8.9.5.37"
export NBITCOIN_NETWORK="testnet"
export LIGHTNING_ALIAS="myalias"
export BTCPAYGEN_CRYPTO1="btc"
export BTCPAYGEN_REVERSEPROXY="nginx"
export BTCPAYGEN_LIGHTNING="lnd"

export ACME_CA_URI="https://acme-staging.api.letsencrypt.org/directory"
ssh-keygen -t rsa -f /root/.ssh/id_rsa_btcpay -q -P ""
echo "# Key used by BTCPay Server" >> /root/.ssh/authorized_keys
cat /root/.ssh/id_rsa_btcpay.pub >> /root/.ssh/authorized_keys
export BTCPAY_HOST_SSHKEYFILE=/root/.ssh/id_rsa_btcpay

export BTCPAY_PROTOCOL=https
export BTCPAYGEN_ADDITIONAL_FRAGMENTS="opt-save-storage-s"

. ./btcpay-setup.sh -i

Expected behaviour

Access the front-end on https.

Actual behaviour

Unable to access the front-end on https and only http which results in broken css links.

AWS - t2.small testing

Hi! I tried to run the server on a t2.small AWS instance (amzn-ami-hvm-2018.03.0.20180412-x86_64-gp2 (ami-6b8cef13)), with 200GB of hard drive space.

• The setup worked, even though it wasn't a strictly Ubuntu machine (I had already installed docker, lines like apt-key did fail though).
• The logs appeared in docker logs x for bitcoind, but were very very slow
• I was able to register and create a store and an app
• The BTCPayServer GUI showed bitcoind to be syncing, with its progress as far as 3%
• But, periodically, bitcoind seems to restart, without even saving block DL progress (because it is crashing instead of being bitcoin-cli stopped. I cannot get into the docker logs to view the cause of failure, but it seems to be making the download process go in circles.
• The cache does sucessfully fill to >200mb, so that doesn't seem to be the problem.

I will try it on an instance with more CPUs maybe?

LTC Lightning Node won't sync

My LTC Lightning Node will not sync. For some reason it is downloading the entire LTC LN chain >1M blocks (with BTC LN it starts WhenLightningBecameCool chopping off most of the chain) and once it reaches the end of the chain, it dumps and starts over. It usually takes 2ish days for it to fully sync, so seeing it start over is pretty heartbreaking. I am unsure if this is a problem with LTC CLightning or with BTC Payserver. I can post over there if you want me too.

Whats the maintenance password?

I believe I followed the instructions to setup. I got informed that BTCpayserver got upgraded yesterday and it is easy to do, just go to Server settings / Maintenance and click upgrade.

It filled in as User btcpayserver and I am puzzled what the password is.
The os does not have a user btcpayserver.

NBXplorer won't start

When I run docker-compose up the BTCPay Server starts fine, but when I try to access the site, I get the error below.

Here is the output I keep getting:

nbxplorer_1                          | info: Configuration:  Network: Main
nbxplorer_1                          | warn: Configuration:  RPC Cookie file not found at /btc/.cookie
nbxplorer_1                          | fail: Configuration:  RPC connection settings not configured
nbxplorer_1                          | Application is shutting down...

And here my env variables.

NBITCOIN_NETWORK="mainnet"
BTCPAY_HOST="payment.mywebsite.org"
LETSENCRYPT_EMAIL="[email protected]"
BITCOIND_COOKIEFILE=".cookie"
BITCOIND_NETWORKPARAMETER="#mainnet=1"
ACME_CA_URI="https://acme-v01.api.letsencrypt.org/directory"

If I run echo $NBITCOIN_NETWORK it outputs the value of the variable, I don't think there's anything wrong with them.

I guess it's the .cookie file that is not being generated or maybe a permission problem. I have also tried to run the docker as root, but the same error happened.

Wrong Repo's on Debian

May you can check the distro and add the correct repo's?

add-apt-repository "deb [arch=amd64] https://download.docker.com/linux/ubuntu artful stable" else add-apt-repository "deb [arch=amd64] https://download.docker.com/linux/ubuntu $(lsb_release -cs) stable"

Thank's 4 the great work!

Error while running docker

I am following the process to run btcpayserver with a docker container as stated here https://github.com/btcpayserver/btcpayserver-docker/tree/master/Regtest but I cannot make it work.

I have docker installed and ran docker-compose up -d within the Regtest directory. Some dependencies where downloaded. Then i ran docker-compose up and the process was started with

Creating network "regtest_default" with the default driver

Then I get some error messages:

nbxplorer_1 | fail: Configuration: Error connecting to RPC server The remote server returned an error: (401) Unauthorized.

Then I get this:

btcpayserver_1 | fail: Configuration: Could not connect to NBXplorer, The operation was canceled.
regtest_btcpayserver_1 exited with code 0
bitcoind_1 | 2017-10-22 04:50:04 Adding fixed seed nodes as DNS doesn't seem to be available.

Finally, I cannot access to btcpay through http://localhost:8080/

Thanks for your help!

How to update to clightning 0.7?

Clightning has a new release (0.7)
I tried to login and run win the directory bitpayserver-docker/ the command btcpay-update.sh
It gives me again the older 0.63 version of clightning.

What do I need to do to get the newer version?

updating

Current Version is BTCPayServer v1.0.3.54
Tried it with Server Settings > Maintenance > Update "The server might restart soon if an update is available..." but version stays the same.
Then via ssh with
sudo su -
btcpay-update.sh

Updating c02d7c4..52d987a
error: Your local changes to the following files would be overwritten by merge:
Production/nginx.tmpl
docker-compose-generator/docker-fragments/bitcoin-clightning.yml
docker-compose-generator/docker-fragments/bitcoin-lnd.yml
docker-compose-generator/docker-fragments/btcpayserver.yml
docker-compose-generator/docker-fragments/groestlcoin-clightning.yml
docker-compose-generator/docker-fragments/groestlcoin.yml
docker-compose-generator/docker-fragments/litecoin-lnd.yml
Please commit your changes or stash them before you merge.
Aborting

How do i commit/stash changes? (what changes are meant by the way?), couldn't find anything in the FAQs.

Updating docker-ce to 18.09.03 on raspbian stretch displays "Cannot connect to the Docker daemon at unix:///var/run/docker.sock"

service docker status

● docker.service - Docker Application Container Engine
   Loaded: loaded (/lib/systemd/system/docker.service; enabled; vendor preset: enabled)
   Active: failed (Result: exit-code) since Sun 2019-03-10 15:05:31 AST; 5min ago
     Docs: https://docs.docker.com
  Process: 2917 ExecStart=/usr/bin/dockerd -H unix:// (code=exited, status=2)
 Main PID: 2917 (code=exited, status=2)
      CPU: 961ms

Mar 10 15:05:28 raspberrypi dockerd[2917]:         /go/src/github.com/docker/docker/cmd/dockerd/docker.go:70 +0x90
Mar 10 15:05:28 raspberrypi systemd[1]: Failed to start Docker Application Container Engine.
Mar 10 15:05:28 raspberrypi systemd[1]: docker.service: Unit entered failed state.
Mar 10 15:05:28 raspberrypi systemd[1]: docker.service: Failed with result 'exit-code'.
Mar 10 15:05:31 raspberrypi systemd[1]: docker.service: Service hold-off time over, scheduling restart.
Mar 10 15:05:31 raspberrypi systemd[1]: Stopped Docker Application Container Engine.
Mar 10 15:05:31 raspberrypi systemd[1]: docker.service: Start request repeated too quickly.
Mar 10 15:05:31 raspberrypi systemd[1]: Failed to start Docker Application Container Engine.
Mar 10 15:05:31 raspberrypi systemd[1]: docker.service: Unit entered failed state.
Mar 10 15:05:31 raspberrypi systemd[1]: docker.service: Failed with result 'exit-code'.

journalctl -xe

Mar 10 15:17:17 raspberrypi dockerd[3300]:         /go/src/github.com/docker/docker/daemon/daemon.go:419 +0xa80
Mar 10 15:17:17 raspberrypi dockerd[3300]: github.com/docker/docker/daemon.NewDaemon(0x2473748, 0x1398b800, 0x13a58500, 0x134abec0, 0x0, 0x0, 0x0)
Mar 10 15:17:17 raspberrypi dockerd[3300]:         /go/src/github.com/docker/docker/daemon/daemon.go:987 +0x249c
Mar 10 15:17:17 raspberrypi dockerd[3300]: main.(*DaemonCli).start(0x1398a700, 0x134ab3e0, 0x0, 0x0)
Mar 10 15:17:17 raspberrypi systemd[1]: docker.service: Main process exited, code=exited, status=2/INVALIDARGUMENT
Mar 10 15:17:17 raspberrypi dockerd[3300]:         /go/src/github.com/docker/docker/cmd/dockerd/daemon.go:180 +0x614
Mar 10 15:17:17 raspberrypi dockerd[3300]: main.runDaemon(0x134ab3e0, 0x134e6780, 0x0)
Mar 10 15:17:17 raspberrypi dockerd[3300]:         /go/src/github.com/docker/docker/cmd/dockerd/docker_unix.go:7 +0x34
Mar 10 15:17:17 raspberrypi dockerd[3300]: main.newDaemonCommand.func1(0x13982140, 0x1341cd50, 0x0, 0x2, 0x0, 0x0)
Mar 10 15:17:17 raspberrypi dockerd[3300]:         /go/src/github.com/docker/docker/cmd/dockerd/docker.go:29 +0x54
Mar 10 15:17:17 raspberrypi dockerd[3300]: github.com/docker/docker/vendor/github.com/spf13/cobra.(*Command).execute(0x13982140, 0x1349e108, 0x2, 0x3, 0x13982140, 0x134
Mar 10 15:17:17 raspberrypi dockerd[3300]:         /go/src/github.com/docker/docker/vendor/github.com/spf13/cobra/command.go:762 +0x364
Mar 10 15:17:17 raspberrypi dockerd[3300]: github.com/docker/docker/vendor/github.com/spf13/cobra.(*Command).ExecuteC(0x13982140, 0x245c5a0, 0x21caaa0, 0x245c5a8)
Mar 10 15:17:17 raspberrypi dockerd[3300]:         /go/src/github.com/docker/docker/vendor/github.com/spf13/cobra/command.go:852 +0x220
Mar 10 15:17:17 raspberrypi dockerd[3300]: github.com/docker/docker/vendor/github.com/spf13/cobra.(*Command).Execute(0x13982140, 0x1349c0f0, 0x1)
Mar 10 15:17:17 raspberrypi dockerd[3300]:         /go/src/github.com/docker/docker/vendor/github.com/spf13/cobra/command.go:800 +0x1c
Mar 10 15:17:17 raspberrypi dockerd[3300]: main.main()
Mar 10 15:17:17 raspberrypi dockerd[3300]:         /go/src/github.com/docker/docker/cmd/dockerd/docker.go:70 +0x90
Mar 10 15:17:17 raspberrypi systemd[1]: Failed to start Docker Application Container Engine.
-- Subject: Unit docker.service has failed
-- Defined-By: systemd
-- Support: https://www.debian.org/support
-- 
-- Unit docker.service has failed.
-- 
-- The result is failed.
Mar 10 15:17:17 raspberrypi systemd[1]: docker.service: Unit entered failed state.
Mar 10 15:17:17 raspberrypi systemd[1]: docker.service: Failed with result 'exit-code'.
Mar 10 15:17:19 raspberrypi systemd[1]: docker.service: Service hold-off time over, scheduling restart.
Mar 10 15:17:19 raspberrypi systemd[1]: Stopped Docker Application Container Engine.
-- Subject: Unit docker.service has finished shutting down
-- Defined-By: systemd
-- Support: https://www.debian.org/support
-- 
-- Unit docker.service has finished shutting down.
Mar 10 15:17:19 raspberrypi systemd[1]: docker.service: Start request repeated too quickly.
Mar 10 15:17:19 raspberrypi systemd[1]: Failed to start Docker Application Container Engine.
-- Subject: Unit docker.service has failed
-- Defined-By: systemd
-- Support: https://www.debian.org/support
-- 
-- Unit docker.service has failed.
-- 
-- The result is failed.
Mar 10 15:17:19 raspberrypi systemd[1]: docker.service: Unit entered failed state.
Mar 10 15:17:19 raspberrypi systemd[1]: docker.service: Failed with result 'exit-code'.

Failed to create symbolic link on Amazon Linux AMI

Prevents starting BTCPayServer

 Amazon ECS-Optimized Amazon Linux AMI 2018.03.h

BTCPay Server started
Creating network "generated_default" with the default driver
Creating generated_postgres_1 ... 
Creating btcpayserver_bitcoind ... 
Creating generated_postgres_1
Creating btcpayserver_bitcoind ... done
Creating generated_nbxplorer_1 ... 
Creating generated_nbxplorer_1 ... done
Creating generated_btcpayserver_1 ... 
Creating generated_btcpayserver_1 ... done
Creating nginx ... 
Creating nginx ... done
Creating nginx-gen ... 
Creating nginx-gen ... done
Creating letsencrypt-nginx-proxy-companion ... 
Creating letsencrypt-nginx-proxy-companion ... done
Adding symlink of bgold-cli.sh to /usr/bin

ln: failed to create symbolic link ‘/usr/bin/bgold-cli.sh’: File exists

Cloudflare and ssl

Hi guys pls check the error whit cloudflare because i try point cnam ----> domain and a ---> ip but not work always error 503 nginx

[Feature Request] Database Backups

It would be nice to be able to easily backup and restore a BTCPay instance.

The backup could be just a shell script that executes this command that @lightbo_lt uses: https://chat.btcpayserver.org/btcpayserver/pl/bi15ze9iipgrueaw7zcj4pmd4r Maybe that could even run as like a cron job.

I'm not a PostgreSQL expert so I'm not sure exactly how the restore side of that would work, but if you've got the dump from the command above there must be a way straightforward way to restore it.

Additional Fragments ignore networks section

Added a custom fragment with a

networks:
  web:
    external: true

and included it in the ADDITIONAL FRAGMENTS var

but the generated docker compose did not include it and the generator did no throw any exceptions

The lnd works fine but the c-lightning not (invoices)

Hello!

I got errors (a generation an invoice from app) from c-lightning as:

{"error":"No payment method available for this store\n10/9/18 4:06:39 PM: Creation of invoice starting\n10/9/18 4:06:39 PM: BTC_CZK: The rating rule is coinaverage(BTC_CZK)\n10/9/18 4:06:39 PM: BTC_CZK: The evaluated rating rule is 148972.603090763\n10/9/18 4:06:39 PM: BTC_USD: The rating rule is coinaverage(BTC_USD)\n10/9/18 4:06:39 PM: BTC_USD: The evaluated rating rule is 6613.95322581253\n10/9/18 4:06:40 PM: BTC: The amount of the invoice is too low to be paid on chain\n10/9/18 4:06:44 PM: BTC: Payment method unavailable (Impossible to create lightning invoice (Resource temporarily unavailable))\n"}

When i try to create an invoice in the admin area throough web - i got same error but by red text in web

Before this:

I set up BTCPay (MS Azure - Docker container) with lnd - it works fine.
Then i changed config to c-lightning by:

btcpay-down.sh
export BTCPAYGEN_LIGHTNING=clightning
. btcpay-setup.sh -i

docker ps shows to me the container 'btcpayserver_clightning_bitcoin'
There is logs as:

Waiting for the node to start and sync
BTC: Is offline
-----trying again in 1 seconds-----
BTC: Is offline
-----trying again in 2 seconds-----
BTC: Is offline
-----trying again in 4 seconds-----
BTC: Is offline
-----trying again in 8 seconds-----
BTC: Is offline
-----trying again in 16 seconds-----
BTC: Is fully synched
Node synched
Replaced network mainnet by bitcoin in /root/.lightning/config
2018-10-09T16:05:29.076Z lightningd(35): Server started with public key 02c163829275ee68d33290f393459d57a1559af09307208bf0f3448d08e37e720c, alias  (color #02c163) and lightningd 3c8001d-modded
2018-10-09T16:07:34.842Z lightningd(35): lightning_channeld-02908b1a203349f963d52a32cc12a19d06ee920380ed14ae01d1cfbc3f16886678 chan #3: Peer connection lost
2018-10-09T16:07:34.842Z lightningd(35): 02908b1a203349f963d52a32cc12a19d06ee920380ed14ae01d1cfbc3f16886678 chan #3: Peer transient failure in CHANNELD_NORMAL: lightning_channeld: Owning subdaemon lightning_channeld died (62208)

Then i update BTCPay to last commit

Then i change BTCPay again to lnd - again it works fine. Then i changed to c-lightning - again same error (Resource temporarily unavailable). Through cli interface i can create invoice under c-lightning...

Calling webdocket (ledger) routes from a different origin

I have BTCPay deployed and I am trying to call the ledger route

[Route("{walletId}/send/ledger/ws")]

from a different origin (another web app with different domain). It works fine when I run BTCPay with RegTest profile on my machine but when I deploy it using btcpay-setup.sh for some reason the request always times out and there is no trace of it in nginx logs.

Is this by design? Should I have different config for my nginx?

[feature request] - Configuration option to specify volume mount for Bitcoin datadir

This is a feature I've hardcoded into the generated docker-compose file, to volume mount the Bitcoin datadir to a persistent disk.

It would be great if there was a fragment or configuration that could let users persist the chaindata to another directory instead of the default path of the docker volume mounts.

[question] Running bitcoind and lnd behind tor

I'm not quite sure this is the right place, but anyway : I used to run my bitcoind node behind tor, and I was wondering if it was possible/easy to run the node in the bctpay docker compose behind tor as well.

Additional fragment can't replace image name

export BTCPAYGEN_ADDITIONAL_FRAGMENTS="mybtcpayserver.custom.yml"

mybtcpayserver.custom.yml

version: "3"

services:
  btcpayserver:
    image: xxxxx.dkr.ecr.xx-xxxx-x.amazonaws.com/btcpayserver:latest

. ./btcpay-setup.sh -i

output:

Unhandled Exception: System.InvalidOperationException: Sequence contains more than one matching element
   at System.Linq.Enumerable.SingleOrDefault[TSource](IEnumerable`1 source, Func`2 predicate)
   at DockerGenerator.DockerComposeDefinition.<>c.<Merge>b__16_2(IGrouping`2 group) in /source/DockerComposeDefinition.cs:line 97
   at System.Linq.Enumerable.SelectEnumerableIterator`2.MoveNext()
   at System.Linq.Enumerable.WhereSelectEnumerableIterator`2.ToArray()
   at DockerGenerator.DockerComposeDefinition.Build() in /source/DockerComposeDefinition.cs:line 82
   at DockerGenerator.Program.Main(String[] args) in /source/Program.cs:line 26

BTCPay generates bitcoin addresses with big gap limit

Hello!

UPDATE: first message here about problem when i didn't understand a root of problem. From second message here i described a problem.

I installed BTCPay and tested Lightning & Bitcoin

After first installation there everything worked fine. I had put "xpub" key, i sent bitcoins and created by BTCPay addresses were valid. I redeemed bitcoins from wallet (Mycelium)
But after i made reconfiguration (#50) of lighting node. I reconfigured lighting but i didn't change bitcoin settings and not tested addresses again.

Now i see in bitcoin configuration right XPUB key but now it has suffix as -[legacy]
Now i see under xpub field there "No ledger wallet detected. If you own one, use chrome, open the app, and refresh this page" but invoices are created and bitcoin addresses too. But now bitcoin addresses are not valid for my wallet (for xpub).

I sent $132 to invoice created by me for deponstration to people but now i cannot understand what deriviation path was used for this (1CRacBeizMMwoNZ9BAMTqPRPxihxnuXLCH). If i will know path i will be able to get private key from xpriv key by (https://iancoleman.io/bip39/) tool. I tried many times other paths but i cannot get same address (1CRacBeizMMwoNZ9BAMTqPRPxihxnuXLCH)

What i see there in BTCPay ("Manage Store" -> "General settings" -> Derivation Scheme -> Modify -> DerivationScheme field):

xpub6CpyqzBEEhGepbeMk5FXsNawsDzgckrpH7oS3AJj4YQdhmQnFJxfPov3j3iRUTrPMF1SBbPvb9evsgUdALjjy7RxaDv1VeM16GeYGtX1fLX-[legacy]

If i press Continue button i didn't see stage of verification of addresses. I see only green message "Derivation scheme for BTC has been modified." in Profile.

I checked this xpub. It's valid without "-[legacy]" suffix and it's BIP32 m/0 path. Last valid address generated by BTCPay there was 19CFM9nQFKLN1TqiK3BxKC9rKmxgyvGkLe (path is m/0/3). BTCPay should generate address 18nTz4zEVTMpaEFsQitnpqHFdWD3QvGQCF (now there is transaction but i sent from other wallet). But BTCPay generated as 1CRacBeizMMwoNZ9BAMTqPRPxihxnuXLCH

And some strange now. In Manage wallet in Transaction tab i see invalid address transaction https://www.smartbit.com.au/tx/688b6db41bab71dca303c871ea616f35986b60bb943660cef89c1aea3439d232 and i see later my other transaction from other wallet to valid address (https://www.smartbit.com.au/tx/e187f74d29d5b36ab3377f03a9fe604b2c162a77757847c4724439063083f053) of same xpub key! So inside BTCPay operates as valid addresses and as invalid ones from one xpub key.

Please help me if possible to understand how can i get private key for 1CRacBeizMMwoNZ9BAMTqPRPxihxnuXLCH

Thanks

Can't connect Zap Desktop to BTCPay Server

Getting the following error when submitting the gRPC configuration file from BTCPay server in ZapDesktop:

Unable to connect to host: Failed to connect before the deadline

Setup: Ubuntu 18.04, latest BTCPay Server Docker, using ZapDesktop v0.3.3

I can create lightning invoices and when I test the connection in the store settings I get "Connection to the lightning node succeeded" and when I open the public node info page it shows online.

I've tried Zap Desktop on the same server the docker instance of BTCPay server is installed with no luck as well as a few other machines.

Please let me know if there are more details that I can provide that can help find a resolution here.

Thanks!

Payment request HELP needed

I tried to create a payment request and it resulted in a link:

https://btcpay.elmit.comment-requests/hub?id=PmLR05JB8HY8dAS_nvSlWw

It should be something with btcpay.elmit.com/
I use Docker, where did it go wrong?

I want to use this payment request in a calendar for online teachers. If the time slot is still free then a student can pay this invoice. If it is already occupied, then the time slot would be already be paid and not anymore available. How can I "distinguish" on a web page if the invoice is already paid or not? I would use then different images.

Specify nginx web ports to allow apache/other reverse proxying

I want to use btcpay behind my existing apache installation. Any way to specify alternatives for nginx other than 80,443?

LunaNode deployment results in 503

I did a LunaNode deployment just like BitcoinTShirt's video, and can connect via SSH and watched it sync to 100%. Unfortunately though, it is stuck at a 503 error. The only custom option I used was my own SSH key, but that doesn't seem to be the problem. docker ps shows no problems with bitcoind/cli, but:

2018-10-13 18:41:38 UpdateTip: new best=000000000000000000241e5ee9e6ba8f5b138d048d4bc7cc5d60622c5d1308ec height=545634 version=0x20000000 log2_work=89.845344 tx=348458521 date='2018-10-13 18:41:19' progress=1.000000 cache=176.7MiB(892979txo) warning='4 of last 100 blocks have unexpected version'
2018-10-13 18:45:28 connect() to 176.109.1.225:8333 failed after select(): Connection refused (111)
2018-10-13 18:47:33 connect() to [2605:e000:1523:821f:cee:96bd:cdc9:9712]:8333 failed: Cannot assign requested address (99)
2018-10-13 18:50:14 connect() to 62.205.132.245:8333 failed after select(): Connection refused (111)

in the bitcoin docker, and some other erring logs in the btcpayserver docker:

info: Configuration:  BTC: Cookie file is /root/.nbxplorer/Main/.cookie
info: Configuration:  SSH settings detected, testing connection to [email protected] on port 22 ...
info: PayServer:      Starting listening NBXplorer (BTC)
warn: Configuration:  SSH connection issue: No such device or address
info: Events:         NBXplorer BTC: NotConnected => Synching
info: PayServer:      Start watching invoices
info: Configuration:  Listening on http://0.0.0.0:49392
fail: PayServer:      BTC: NBXplorer error `The operation was canceled.`
info: Events:         NBXplorer BTC: Synching => NotConnected
fail: PayServer:      BTC: NBXplorer error `The operation was canceled.`
info: Events:         NBXplorer BTC: NotConnected => Synching
fail: PayServer:      BTC: NBXplorer error `The operation was canceled.`
info: Events:         NBXplorer BTC: Synching => NotConnected
fail: PayServer:      BTC: NBXplorer error `The operation was canceled.`
info: Events:         NBXplorer BTC: NotConnected => Synching
warn: PayServer:      Error while contacting cryptopia: The operation has timed out.
warn: PayServer:      Error while contacting kraken: Error while copying content to a stream.
warn: PayServer:      Error while contacting hitbtc: The operation has timed out.
fail: PayServer:      BTC: NBXplorer error `The operation was canceled.`
info: Events:         NBXplorer BTC: Synching => NotConnected
fail: PayServer:      BTC: NBXplorer error `The operation was canceled.`
info: Events:         NBXplorer BTC: NotConnected => Synching
warn: PayServer:      Error while contacting cryptopia: The operation has timed out.
fail: PayServer:      BTC: NBXplorer error `The operation was canceled.`
info: Events:         NBXplorer BTC: Synching => NotConnected
info: Events:         NBXplorer BTC: NotConnected => Synching
warn: PayServer:      Error while contacting cryptopia: Cannot access child value on Newtonsoft.Json.Linq.JValue.
warn: PayServer:      Error while contacting cryptopia: Cannot access child value on Newtonsoft.Json.Linq.JValue.
warn: PayServer:      Error while contacting cryptopia: Cannot access child value on Newtonsoft.Json.Linq.JValue.
warn: PayServer:      Error while contacting cryptopia: Cannot access child value on Newtonsoft.Json.Linq.JValue.
warn: PayServer:      Error while contacting cryptopia: Cannot access child value on Newtonsoft.Json.Linq.JValue.
warn: PayServer:      Error while contacting cryptopia: Cannot access child value on Newtonsoft.Json.Linq.JValue.
fail: PayServer:      BTC: NBXplorer error `The operation was canceled.`
info: Events:         NBXplorer BTC: Synching => NotConnected

warn: PayServer:      Error while contacting bittrex: The operation has timed out.
warn: PayServer:      Error while contacting poloniex: The operation has timed out.
warn: PayServer:      Error while contacting binance: The operation has timed out.
warn: PayServer:      Error while contacting cryptopia: The operation has timed out.
warn: PayServer:      Error while contacting hitbtc: Resource temporarily unavailable Resource temporarily unavailable
fail: PayServer:      BTC: NBXplorer error `The operation was canceled.`
info: Events:         NBXplorer BTC: Synching => NotConnected
info: Events:         NBXplorer BTC: NotConnected => Synching
warn: PayServer:      Error while contacting hitbtc: The operation has timed out.
warn: PayServer:      Error while contacting hitbtc: The operation has timed out.
warn: PayServer:      Error while contacting hitbtc: The operation has timed out.
warn: PayServer:      Error while contacting hitbtc: The operation has timed out.
warn: PayServer:      Error while contacting hitbtc: The operation has timed out.
warn: PayServer:      Error while contacting hitbtc: <html>
      <head><title>502 Bad Gateway</title></head>
      <body bgcolor="white">
      <center><h1>502 Bad Gateway</h1></center>
      <hr><center>nginx</center>
      </body>
      </html>

warn: PayServer:      Error while contacting hitbtc: The operation has timed out.
warn: PayServer:      Error while contacting hitbtc: <html>
      <head><title>502 Bad Gateway</title></head>
      <body bgcolor="white">
      <center><h1>502 Bad Gateway</h1></center>
      <hr><center>nginx</center>
      </body>
      </html>

warn: PayServer:      Error while contacting hitbtc: The operation has timed out.
warn: PayServer:      Error while contacting cryptopia: Cannot access child value on Newtonsoft.Json.Linq.JValue.
warn: PayServer:      Error while contacting hitbtc: The operation has timed out.
warn: PayServer:      Error while contacting hitbtc: The operation has timed out.
fail: PayServer:      BTC: NBXplorer error `The operation was canceled.`
info: Events:         NBXplorer BTC: Synching => NotConnected
info: Events:         NBXplorer BTC: NotConnected => Synching
warn: PayServer:      Error while contacting binance: The operation has timed out.
warn: PayServer:      Error while contacting cryptopia: The operation has timed out.
warn: PayServer:      Error while contacting hitbtc: The operation has timed out.
warn: PayServer:      Error while contacting binance: The operation has timed out.

IP for reference:
http://172.81.177.59/

Gonna reboot shortly

Bitcoin Core Version

I have btcpayserver-docker installed and running just fine, however, when I view the version of Bitcoin Core installed via the bitcoind --version or bitcoin-cli.sh getnetworkinfo, the install of btcpayserver is only installing v.0.17.0 and not v.0.17.1 which is the latest version of Bitcoin Core. Is there a way to upgrade this as I had a BC full node running before installing btcpayserver and it still shows from the bitcoind program that it is the latest version of v.0.17.1 which is the code base I would prefer for my node to be running. Or is there no way to install an upgrade to Bitcoin Core while running btcpayserver on the same hardware?

IPN sent only for confimed invoices

Hello!
I am running dockerized btcpayserver. 4 days ago i updated btcpay docker container (only btcpayserver) to the latest btcpayserver version regarding to this issue: btcpayserver/btcpay-python#2

While i got python library working, i am getting weird problem - now i have callbacks (IPN) only when payment is confirmed (before it was also paid / expired notifications, now gone).

Attaching screenshots of invoice events:

Lightning payment (paid):

Expired invoice:

completed on-chain payment:

Consider switching to FluentDocker Compose Construction

Just found this super slick project called FluentDocker which would allow us to clean up that generator code and enable some new possibilities.

C-lightning takes forever to sync

Issue

I'm on testnet. Everything seems to run fine, bitcoind already synced, but after about 6 hours run c-lightning only catched up to block 319281 and is really slow.

Should I open an issue with c-lightning instead ?

getinfo outputs

Bitcoin-cli getblockchaininfo gives the following :

{
 "chain": "test",
 "blocks": 1363017,
 "headers": 1363017,
 "bestblockhash": "0000000000016f60cfe53ff1af0d4cb265f46f11e51851d8121264e5851a74df",
 "difficulty": 66.18234607252185,
 "mediantime": 1533312925,
 "verificationprogress": 0.9999999961738156,
 "initialblockdownload": false,
 "chainwork": "0000000000000000000000000000000000000000000000857d53010e68d49087",
 "size_on_disk": 15166898774,
 "pruned": false,
 "softforks": [
   {
     "id": "bip34",
     "version": 2,
     "reject": {
       "status": true
     }
   },
   {
     "id": "bip66",
     "version": 3,
     "reject": {
       "status": true
     }
   },
   {
     "id": "bip65",
     "version": 4,
     "reject": {
       "status": true
     }
   }
 ],
 "bip9_softforks": {
   "csv": {
     "status": "active",
     "startTime": 1456790400,
     "timeout": 1493596800,
     "since": 770112
   },
   "segwit": {
     "status": "active",
     "startTime": 1462060800,
     "timeout": 1493596800,
     "since": 834624
   }
 },
 "warnings": "Warning: unknown new rules activated (versionbit 28)"
}

bitcoin-lightning-cli gives the following :

{
  "id": "033179c6fe94edeb5d4047a0a23d615d350a8bc1c0eb21e462019f58ffc3ac5a8c", 
  "port": 9735, 
  "address": [
    {
      "type": "ipv4", 
      "address": "5.51.82.169", 
      "port": 9735
    }
  ], 
  "binding": [
    {
      "type": "ipv4", 
      "address": "0.0.0.0", 
      "port": 9735
    }
  ], 
  "version": "basedon-aeafe4dbe7d5c61f664c18417698866b0d70252f-modded", 
  "blockheight": 319281, 
  "network": "testnet"
}

Setup

Description:    Ubuntu 18.04 LTS
Release:        18.04
4.15.0-23-generic

btcpayserver-docker commit 511db652e8228f566b87620fe94a8d00f162d120

docker-compose fails on raspberry pi

I've been trying to get btcpayserver-docker to work on raspberry pi 1 b (armv6) but it keeps failing with:
BTCPay Server starting... this can take 5 to 10 minutes... Job for btcpayserver.service failed because the control process exited with error code. See "systemctl status btcpayserver.service" and "journalctl -xe" for details. BTCPay Server started **ERROR: .IOError: [Errno 2] No such file or directory: '/root/BTCPayServer/btcpayserver-docker/Generated/docker-compose.generated.yml'**

I tried raspbian, kali-linux and now hypriot which has docker working but no luck. It seems the docker-compose-generator doesn't create any files at that directory. Is it possible the image is not built for armv6/armel ? Or is there something else I'm missing?

docker ps gives below. It seems like everything except postgres is restarting with cause 139:
HypriotOS/armv6: pirate@black-pearl in ~ $ docker ps CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES f430ef6dbba2 btcpayserver/btcpayserver:1.0.3.45 "dotnet BTCPayServer…" 2 minutes ago Restarting (139) 5 seconds ago generated_btcpayserver_1 e5264ba13ea1 btcpayserver/lnd:v0.5.1-beta-2 "/docker-entrypoint.…" 11 minutes ago Restarting (139) 16 seconds ago btcpayserver_lnd_bitcoin 228f9372aa0d btcpayserver/bitcoin:0.17.0 "/entrypoint.sh bitc…" 2 hours ago Restarting (139) 3 minutes ago 8332-8333/tcp, 18332-18333/tcp, 18443-18444/tcp, 28332-28333/tcp, 39388/tcp, 43782/tcp btcpayserver_bitcoind 2a4ea19d55ab postgres:9.6.5 "docker-entrypoint.s…" 2 hours ago Up 2 hours 5432/tcp generated_postgres_1 25af99673077 nicolasdorier/nbxplorer:2.0.0.11 "dotnet NBXplorer.dll" 2 hours ago Restarting (139) 27 seconds ago

Utilize new log option in docker image

We should allow users to make use of the new debuglog and debugloglevel through the docker setup.

FastSync snapshot old?

Are the FastSync snapshots still being published regularly?

The listing shows one snapshot per chain from November:
http://utxosets.blob.core.windows.net/public?restype=container&comp=list&include=metadata

Unable to connect zap, joule etc to BTCPayServer

I am unable to connect zap, joule etc to LND through BTCPayServer

I am not using the internal nginx reverse proxy because I am using a single IP which already has a server hosted with various other services behind a nginx reverse proxy.

Everything else works just fine just can't connect to a wallet LND

Is this supposed to be null "certificateThumbprint": null,

I have also tried clightning and spark and just get a 404 error from btcpay
Basically everything is working just fine except I am unable to connect any lightning wallets to manage the channels

{
"configurations": [
{
"host": "btcpay.xxxxxxxxxxxxxxxxxxxxxx",
"port": 443,
"ssl": true,
"chainType": "Mainnet",
"type": "grpc",
"cryptoCode": "BTC",
"certificateThumbprint": null,
"macaroon": "xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx",
"adminMacaroon": "xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx",
"readonlyMacaroon": "xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx",
"invoiceMacaroon": "xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx"
}
]
}

I installed BTCPaySever with the variables

export BTCPAY_HOST="btcpay.xxxxxxxxxxxxxxxxxxxxxxxx"
export NBITCOIN_NETWORK="mainnet"
export BTCPAYGEN_CRYPTO1="btc"
export BTCPAYGEN_CRYPTO2="ltc"
export BTCPAYGEN_REVERSEPROXY="none"
export BTCPAYGEN_LIGHTNING="lnd"
export LIGHTNING_ALIAS="xxxxxxxxxxxxxxxxxxxxxx"
export BTCPAY_PROTOCOL="https"
. ./btcpay-setup.sh -i

I have removed various fields with xxxxxxxxxxxxx for security and privacy

[question] I've finished setting up with Docker, but get a 503 Service Temporarily Unavailable

Just finished the installation with docker, followed all the steps to the letter, but get a 503 Service Temporarily Unavailable error when browsing to the server's IP.

Could this be because I am browsing to the servers IP and not the domain name I configured?
My DNS change is not fully propagated yet (may take up to 1 day) and I dont wanna wait :-)

Can I save time by using changedomain.sh?

I can't seam to find any troubleshooting steps on this.

What can I expect when browsing to the IP under normal conditions?

When running docker ps, I can see lots of containers running and at 100% CPU...

Local btcpayserver-docker image builder is broken

Something with the new dokcer wizardry has broken the local generator builder flag (BTCPAYGEN_DOCKER_IMAGE to btcpayserver/docker-compose-generator:local)

Error in setup:

unable to prepare context: unable to evaluate symlinks in Dockerfile path: lstat /root/BTCPayServer/btcpayserver-docker/docker-compose-generator/Dockerfile: no such file or directory
Unable to find image 'btcpayserver/docker-compose-generator:local' locally
docker: Error response from daemon: manifest for btcpayserver/docker-compose-generator:local not found.

Errors in nginx container when running with BTCPAYGEN_REVERSEPROXY="nginx"

I have encountered errors with the configuration associated with the nginx container when running with BTCPAYGEN_REVERSEPROXY="nginx"

If I run with BTCPAYGEN_REVERSEPROXY="none" all the associated docker containers start and the server is available via the web where it is hosted.

Originally (2019/03/15) the following error was being reported by the nginx container (via docker logs nginx)

nginx: [emerg] invalid number of arguments in "upstream" directive in /etc/nginx/conf.d/default.conf:63
2019/03/15 06:59:34 [emerg] 1#1: invalid number of arguments in "upstream" directive in /etc/nginx/conf.d/default.conf:63

I later pulled the most recent changes from GitHub and when I re-ran the setup command the nginx container continued to fail to start - however due to a different issue (as per docker logs nginx):

2019/03/17 03:31:19 [emerg] 1#1: invalid number of arguments in "server_name" directive in /etc/nginx/conf.d/default.conf:108
nginx: [emerg] invalid number of arguments in "server_name" directive in /etc/nginx/conf.d/default.conf:108

Let me know if you require more information. I can reliably reproduce it by simply re-enabling the nginx reverse proxy.

These are the other environment configuration setting in use (domains have been changed below):

-------SETUP-----------
Parameters passed:
BTCPAY_PROTOCOL:https
BTCPAY_HOST:btcpay.mydomain.com
LIBREPATRON_HOST:
WOOCOMMERCE_HOST:
BTCPAY_HOST_SSHKEYFILE:/root/.ssh/id_rsa_btcpay
LETSENCRYPT_EMAIL:[email protected]
NBITCOIN_NETWORK:mainnet
LIGHTNING_ALIAS:
BTCPAYGEN_CRYPTO1:btc
BTCPAYGEN_CRYPTO2:ltc
BTCPAYGEN_CRYPTO3:
BTCPAYGEN_CRYPTO4:
BTCPAYGEN_CRYPTO5:
BTCPAYGEN_CRYPTO6:
BTCPAYGEN_CRYPTO7:
BTCPAYGEN_CRYPTO8:
BTCPAYGEN_CRYPTO9:
BTCPAYGEN_REVERSEPROXY:nginx
BTCPAYGEN_LIGHTNING:clightning
BTCPAYGEN_ADDITIONAL_FRAGMENTS:opt-save-storage-xs;opt-add-librepatron
BTCPAY_IMAGE:
ACME_CA_URI:https://acme-v01.api.letsencrypt.org/directory
----------------------
Additional exported variables:
BTCPAY_DOCKER_COMPOSE=/root/BTCPayServer/btcpayserver-docker/Generated/docker-compose.generated.yml
BTCPAY_BASE_DIRECTORY=/root/BTCPayServer
BTCPAY_ENV_FILE=/root/BTCPayServer/.env
BTCPAYGEN_OLD_PREGEN=false
BTCPAY_SSHKEYFILE=/datadir/id_rsa
BTCPAY_SSHTRUSTEDFINGERPRINTS:SHA256:...............;
----------------------

Improve Pay Button disabled message

When a user clickc on a pay button and the feature is disabled on the store, they are greeted with

perhaps we should have a more friendly page version

Azure deployment frozen at near-end BTC sync

After a few days, it is still stuck here (from a standard one-click Azure deployment):

https://i.imgur.com/rzypP0q.png

Will investigate.

Replace container links with networks

Containers links are a legacy docker feature and are discouraged from being used. The substitute are networks.
I've done a test on btcpay.nbitstack.com and am running btc on am modified compose with networks

Ideally, we have 2 networks: internal and web with only the front facing services in web.

docker-compose up causes "manifest for nicolasdorier/btcpayserver:1.0.1.83 not found"

root@btcpayvm:~/btcpayserver-docker# docker-compose -f "$(pwd)/Production/docker-compose.btc-clightning.yml" up -d
[...]
Pulling btcpayserver (nicolasdorier/btcpayserver:1.0.1.83)...
ERROR: manifest for nicolasdorier/btcpayserver:1.0.1.83 not found

This tag doesn't seem to exist, so I fixed it by changing btcpayserver in the yml and setting:
image: nicolasdorier/btcpayserver:1.0.1.84

Getting Infinite error loop and Error 503 when I try to access on browser

I have installed docker-compose, cloned this repository and then cd into the Production directory, once there I ran, docker-compose up, but it didn't work, I got stuck in a loop of errors. Sometimes it hangs for a few seconds in the output below, and then the error loop starts again..

If I try to access http://my_public_ip/ I get a 503 Service Temporarily Unavailable error.

I'm using Google Engine by the way.. I'm not sure if this docker is compatible with Azure only.

nginx-gen                            | 2018/01/05 19:46:50 Received event start for container cdca2f293225
btcpayserver_bitcoind                | 2018-01-05 19:46:50 Adding fixed seed nodes as DNS doesn't seem to be available.
letsencrypt-nginx-proxy-companion    | 2018/01/05 19:46:53 Debounce maxTimer fired
letsencrypt-nginx-proxy-companion    | 2018/01/05 19:46:53 Contents of /app/letsencrypt_service_data did not change. Skipping notification '/app/update_certs'
nginx-gen                            | 2018/01/05 19:46:55 Debounce minTimer fired
nginx-gen                            | 2018/01/05 19:46:55 Contents of /etc/nginx/conf.d/default.conf did not change. Skipping notification ''

Port 80 connects to WordPress at root of domain, but not to BTCPayServer at pay.domain

• Using fragments: opt-save-storage-xs;opt-add-woocommerce. On initial run, WP setup appeared, was successful, and WP seems to be useable (at mydomain.com).

• However, visiting the route pay.mydomain.com, as configured for BTCPayServer, won't load - it fails with ERR_CONNECTION_TIMED_OUT on Chrome (This site can’t be reached: pay.mydomain.com took too long to respond.). Same thing with https://.

• Both NBXplorer and BTCPayServer are successfully reporting 'New Block' events. Also, bitcoind seems to be fully syncd (progress 1.0, correct height).

• Running for BTC only on a DigitalOcean one-click instance, per this guide: https://medium.com/@molthoff/running-btcpay-on-digital-ocean-for-10-month-how-to-add-other-coins-7a497339fb2f. Disk usage is at 64%, Memory usage is at 54%.

• The nginx configuration seems to contain the right url: pay.mydomain.com

• I have run ./btcpayserver-restart.sh, and even ./changedomain.sh pay.mydomain.com

• Upon inspecting letsencrypt-nginx-proxy-companion:

2019/03/17 20:05:24 Received event start for container 2cba9a1be126
2019/03/17 20:05:26 Received event die for container 2cba9a1be126
2019/03/17 20:05:41 Debounce minTimer fired
2019/03/17 20:05:41 Contents of /app/letsencrypt_service_data did not change. Skipping notification '/app/signal_le_service'
2019/03/17 20:06:26 Received event start for container 2cba9a1be126
2019/03/17 20:06:28 Received event die for container 2cba9a1be126
2019/03/17 20:06:43 Debounce minTimer fired
2019/03/17 20:06:43 Contents of /app/letsencrypt_service_data did not change. Skipping notification '/app/signal_le_service'

Seems to be stuck in this loop, continuously restarting the LND image. There is nothing in logs/lnd.log

Also just saw this message from nginx:

x.x.x.x - - [17/Mar/2019:20:01:13 +0000] "\x03\x00\x00/*\xE0\x00\x00\x00\x00\x00Cookie: mstshash=Administr" 400 166 "-" "-"
2019/03/17 20:11:32 [warn] 8#8: no resolver defined to resolve ocsp.int-x3.letsencrypt.org while requesting certificate status, responder: ocsp.int-x3.letsencrypt.org, certificate: "/etc/nginx/certs/mydomain.com.crt"

Any ideas?

[Feature Request] Custom url for exchange rate provider

[suggestion] mount an already synched blockchain directory inside the docker

I installed BTCPay on a very custom setup and wrote this article about my experience so far.
Since I already run a Bitcoin full node on the same machine, I would like to use the already synched blockchain directly with BTCPay.
@NicolasDorier suggested that I use the docker cp command to copy the data from my existent node to the volume created inside the docker, but I think it could be even better if I can directly mount the existing .bitcoin directory inside the docker compose.
What do you think ?

Conflict with LND other port 9735

Summary

I want to start a btcpayserver docker to experiment on the testnet. I already run a bitcoind and LND instance on the mainnet on the same machine (a small home server on Ubuntu).

I followed instructions on the README page, and ran . ./btcpay-setup.sh -i, everything was ok, except an error that kept c-lightning from starting.

Here is the exact error message :
ERROR: for clightning_bitcoin Cannot start service clightning_bitcoin: driver failed programming external connectivity on endpoint btcpayserver_clightning_bitcoin (fdb8db643d2aae0fbc6bbd906c7fd97ed074a5ed2be74e887191293fbb5e4d56): Error starting userland proxy: listen tcp 0.0.0.0:9735: bind: address already in use

lsof -i -P -n | grep LISTEN indeed shows lnd 13495 bitcoin 8u IPv6 511515 0t0 TCP *:9735 (LISTEN)

Is there a way to change the port c-lightning is listening on setup ? Especially since my LND is running on main and this c-lighting will run on testnet.

Environment setup

Description:    Ubuntu 18.04 LTS
Release:        18.04
4.15.0-23-generic

btcpayserver-docker commit 511db652e8228f566b87620fe94a8d00f162d120

Thanks !

BTCPayServer Repos

How would you feel about btcpayserver-docker and btcpayserver-azure being merged into a singular repo: btcpayserver-deploy? Each platform would have its own directory, in addition to a toplevel docs/ directory.

That way, btcpayserver/btcpayserver can stay as-is (./build.sh-driven build), and also have internals-specific docs in a docs/ dir.

I like the current layout with WooCommerce / Drupal Commerce / Magento / WHMCS / Prestashop as 'plugin' repos; their default configuration(s) & yet another docs/ can also be in each of these repos. I think they should all have the suffix -plugin.

This all could also make the btcpayserver-docs repo obsolete... But perhaps it can be reorganized / repurposed.