Deployment FAQ
This document covers the most common questions, errors, and issues you may encounter prior and during the installation of the software. For a detailed list of deployments method and instructions for each, please see Deployment page.
Here are common questions about installation, regardless of the deployment method.
BTCPay is a 100% free and open-source software. We do not charge you anything. However, to run it, you should host it. You can run it as a self-hosted solution on your own local server, or use a cloud hosting provider, which is what a majority of users do. Advanced users can run BTCPay on their own hardware Visit our Deployment Page to see various ways in which you can run BTCPay. If you do not wish to host your own server, you should use a free host. If you prefer to have control over your node and additional features, you can use a cloud solution, which goes from 5$ to 65$ /month depending on the provider you choose.
If you would like to run Bitcoin and Lightning Network nodes, the minimal requirements are :
2GB Ram
80 GB of storage with enabled pruning​
Docker
For beginners, we strongly recommend the web-deployment if you want a self-hosted solution or a third-party host​
If you're going to add more than one crypto coin, you need to expand the storage according to that coin(s) blockchain size.
Please see Deployment page for comparison of different installation methods and choose the one that suits your needs and skill level the most.
Yes, you can. Check our the Hardware Deployment page for detailed instructions.
Yes. BTCPay is not limited to the documented deployment methods. You can use whichever hosting solution you prefer, that fits the minimal requirements.
On a self-hosted BTCPay, the unlimited amount of users and stores can be attached. That's why there are users who opened their servers for others to use. Most of them are community-driven and free. See this list of third-party BTCPay hosts​
When you deploy your BTCPay Server, you should first register a user (during server synchronization). This user is automatically the server admin. If your BTCPay only shows Login in the header menu, and you are unable to register the first user after initial deployment, someone else has registered on your server as the admin. Although this is unlikely to occur (the user would need to know and watch your BTCPay domain name), they had access to your ssh private keys, thus you should redeploy a new server for security reasons.
Here you can find common questions and solutions to BTCPay web-deployments.
In your LunaNode dashboard, click on Virtual Machines > Your Virtual Machine > General Tab > External IP. Copy the external IP.
Go to your DNS provider and create an A record. Paste the external IP.
Go to Server Settings > Maintenance > Change Domain. Paste yourdomain.com without http or https prefix.
Additional documentation can be found on domain change page.
You need to open port 80 and 443. Once you did that, restart docker btcpay-restart.sh
Check this community guide.
You might see this error on the front page of your BTCPay Server since version 1.0.3.73.
This is caused by a breaking change made in BTCPay to be able to handle different domain on the same server.
It happens because your BTCPay Server is not exposed directly on internet, instead a reverse proxy (like nginx or IIS) receive the request and forward it to BTCPay Server.
Sadly, depending on the configuration of your reverse proxy, either the HTTP HOST header has been replaced, or the reverse proxy did not forwarded the protocol at the front with the http header X-Forwarded-Proto.
If you use NGinx, here is what you need to have at the top level in /etc/nginx/conf.d/default.conf:
map $http_x_forwarded_proto $proxy_x_forwarded_proto {default $http_x_forwarded_proto;'' $scheme;}proxy_set_header Host $http_host;proxy_set_header X-Forwarded-Proto $proxy_x_forwarded_proto;
If your reverse proxy is Apache 2, you need to set those two settings
<VirtualHost *:443>RequestHeader set X-Forwarded-Proto "https"ProxyPreserveHost on...</VirtualHost>