Basic installation

You can choose between four package managers, poetry and nix

By default, LNbits will use SQLite as its database. You can also use PostgreSQL which is recommended for applications with a high load (see guide below).

Mininum poetry version has is ^1.2, but it is recommended to use latest poetry. (including OSX) Make sure you have Python 3.9 or 3.10 installed.

install python on ubuntu

# for making sure python 3.9 is installed, skip if installed. To check your installed version: python3 --version
sudo apt update
sudo apt install software-properties-common
sudo add-apt-repository ppa:deadsnakes/ppa
sudo apt install python3.9 python3.9-distutils

install poetry

curl -sSL | python3 -
# Once the above poetry install is completed, use the installation path printed to terminal and replace in the following command
export PATH="/home/user/.local/bin:$PATH"
git clone
cd lnbits
git checkout main

# Next command, you can exchange with python3.10 or newer versions.
# Identify your version with python3 --version and specify in the next line
# command is only needed when your default python is not ^3.9 or ^3.10
poetry env use python3.9
poetry install --only main

mkdir data
cp .env.example .env
# set funding source amongst other options
nano .env

Running the server

poetry run lnbits
# To change port/host pass 'poetry run lnbits --port 9000 --host'
# adding --debug in the start-up command above to help your troubleshooting and generate a more verbose output
# Note that you have to add the line DEBUG=true in your .env file, too.

Updating the server

cd lnbits
# Stop LNbits with `ctrl + x`
git pull
# Keep your poetry install up to date, this can be done with `poetry self update`
poetry install --only main
# Start LNbits with `poetry run lnbits`

Option 2: Nix

# Install nix. If you have installed via another manager, remove and use this install (from
sh <(curl -L --daemon

# Enable nix-command and flakes experimental features for nix:
echo 'experimental-features = nix-command flakes' >> /etc/nix/nix.conf

# Add cachix for cached binaries
nix-env -iA cachix -f
cachix use lnbits

# Clone and build LNbits
git clone
cd lnbits
nix build

mkdir data

Running the server

nix run

Ideally you would set the environment via the .env file, but you can also set the env variables or pass command line arguments:

# .env variables are currently passed when running, but LNbits can be managed with the admin UI.
LNBITS_ADMIN_UI=true ./result/bin/lnbits --port 9000

# Once you have created a user, you can set as the super_user
SUPER_USER=be54db7f245346c8833eaa430e1e0405 LNBITS_ADMIN_UI=true ./result/bin/lnbits --port 9000

Option 3: Docker

use latest version from docker hub

docker pull lnbits/lnbits
wget -O .env
mkdir data
docker run --detach --publish 5000:5000 --name lnbits --volume ${PWD}/.env:/app/.env --volume ${PWD}/data/:/app/data lnbits/lnbits

build the image yourself

git clone
cd lnbits
docker build -t lnbits/lnbits .
cp .env.example .env
mkdir data
docker run --detach --publish 5000:5000 --name lnbits --volume ${PWD}/.env:/app/.env --volume ${PWD}/data/:/app/data lnbits/lnbits

Option 4: is a docker container hosting platform that has a generous free tier. You can host LNbits for free on for personal use.

First, sign up for an account at (no credit card required).

Then, install the CLI onto your device here.

After install is complete, the command will output a command you should copy/paste/run to get fly into your $PATH. Something like:

flyctl was installed successfully to /home/ubuntu/.fly/bin/flyctl
Manually add the directory to your $HOME/.bash_profile (or similar)
  export FLYCTL_INSTALL="/home/ubuntu/.fly"

You can either run those commands, then source ~/.bash_profile or, if you don’t, you’ll have to call Fly from ~/.fly/bin/flyctl.

Once installed, run the following commands.

git clone
cd lnbits
fly auth login
[complete login process]
fly launch

You’ll be prompted to enter an app name, region, postgres (choose no), deploy now (choose no).

You’ll now find a file in the directory called fly.toml. Open that file and modify/add the following settings.

Note: Be sure to replace ${PUT_YOUR_LNBITS_ENV_VARS_HERE} with all relevant environment variables in .env or .env.example. Environment variable strings should be quoted here, so if in .env you have LNBITS_ENDPOINT= in fly.toml you should have LNBITS_ENDPOINT="".

Note: Don’t enter secret environment variables here. offers secrets (via the fly secrets command) that are exposed as environment variables in your runtime. So, for example, if using the LND_REST funding source, you can run fly secrets set LND_REST_MACAROON=<hex_macaroon_data>.

kill_timeout = 30




  internal_port = 5000

Next, create a volume to store the sqlite database for LNbits. Be sure to choose the same region for the volume that you chose earlier.

fly volumes create lnbits_data --size 1

You’re ready to deploy! Run fly deploy and follow the steps to finish deployment. You’ll select a region (up to you, choose the same as you did for the storage volume previously created), postgres (choose no), deploy (choose yes).

You can use fly logs to view the application logs, or fly ssh console to get a ssh shell in the running container.


Problems installing? These commands have helped us install LNbits.

sudo apt install pkg-config libffi-dev libpq-dev

# build essentials for debian/ubuntu
sudo apt install python3.9-dev gcc build-essential

# if the secp256k1 build fails:
# if you used poetry
poetry add setuptools wheel

Optional: PostgreSQL database

If you want to use LNbits at scale, we recommend using PostgreSQL as the backend database. Install Postgres and setup a database for LNbits:

# on debian/ubuntu 'sudo apt-get -y install postgresql'
# or follow instructions at

# Postgres doesn't have a default password, so we'll create one.
sudo -i -u postgres
# on psql
ALTER USER postgres PASSWORD 'myPassword'; # choose whatever password you want
# on postgres user
createdb lnbits

You need to edit the .env file.

# add the database connection string to .env 'nano .env' LNBITS_DATABASE_URL=
# postgres://<user>:<myPassword>@<host>:<port>/<lnbits> - alter line bellow with your user, password and db name
# save and exit

Using LNbits

Now you can visit your LNbits at http://localhost:5000/.

Now modify the .env file with any settings you prefer and add a proper funding source by modifying the value of LNBITS_BACKEND_WALLET_CLASS and providing the extra information and credentials related to the chosen funding source.

Then you can restart it and it will be using the new settings.

You might also need to install additional packages or perform additional setup steps, depending on the chosen backend. See the short guide on each different funding source.

Take a look at Polar for an excellent way of spinning up a Lightning Network dev environment.

Additional guides

SQLite to PostgreSQL migration

If you already have LNbits installed and running, on an SQLite database, we highly recommend you migrate to postgres if you are planning to run LNbits on scale.

There’s a script included that can do the migration easy. You should have Postgres already installed and there should be a password for the user (see Postgres install guide above). Additionally, your LNbits instance should run once on postgres to implement the database schema before the migration works:

# STOP LNbits

# add the database connection string to .env 'nano .env' LNBITS_DATABASE_URL=
# postgres://<user>:<password>@<host>/<database> - alter line bellow with your user, password and db name
# save and exit

# START LNbits
# STOP LNbits
poetry run python tools/
# or
make migration

Hopefully, everything works and get migrated… Launch LNbits again and check if everything is working properly.

LNbits as a systemd service

Systemd is great for taking care of your LNbits instance. It will start it on boot and restart it in case it crashes. If you want to run LNbits as a systemd service on your Debian/Ubuntu/Raspbian server, create a file at /etc/systemd/system/lnbits.service with the following content:

# Systemd unit for lnbits
# /etc/systemd/system/lnbits.service

# you can uncomment these lines if you know what you're doing
# it will make sure that lnbits starts after lnd (replace with your own backend service)

# replace with the absolute path of your lnbits installation
# same here. run `which poetry` if you can't find the poetry binary
ExecStart=/home/lnbits/.local/bin/poetry run lnbits
# replace with the user that you're running lnbits on


Save the file and run the following commands:

sudo systemctl enable lnbits.service
sudo systemctl start lnbits.service

Reverse proxy with automatic HTTPS using Caddy

Use Caddy to make your LNbits install accessible over clearnet with a domain and https cert.

Point your domain at the IP of the server you’re running LNbits on, by making an A record.

Install Caddy on the server

sudo caddy stop

Create a Caddyfile

sudo nano Caddyfile

Assuming your LNbits is running on port 5000 add: {
  handle /api/v1/payments/sse* {
    reverse_proxy {
      header_up X-Forwarded-Host
      transport http {
         keepalive off
         compression off
  reverse_proxy {
    header_up X-Forwarded-Host

Save and exit CTRL + x

sudo caddy start

Running behind an Apache2 reverse proxy over HTTPS

Install Apache2 and enable Apache2 mods:

apt-get install apache2 certbot
a2enmod headers ssl proxy proxy-http

Create a SSL certificate with LetsEncrypt:

certbot certonly --webroot --agree-tos --non-interactive --webroot-path /var/www/html -d

Create an Apache2 vhost at: /etc/apache2/sites-enabled/lnbits.conf:

cat <<EOF > /etc/apache2/sites-enabled/lnbits.conf
<VirtualHost *:443>
  SSLEngine On
  SSLProxyEngine On
  SSLCertificateFile /etc/letsencrypt/live/
  SSLCertificateKeyFile /etc/letsencrypt/live/
  Include /etc/letsencrypt/options-ssl-apache.conf
  LogLevel info
  ErrorLog /var/log/apache2/lnbits.log
  CustomLog /var/log/apache2/lnbits-access.log combined
  RequestHeader set "X-Forwarded-Proto" expr=%{REQUEST_SCHEME}
  RequestHeader set "X-Forwarded-SSL" expr=%{HTTPS}
  ProxyPreserveHost On
  ProxyPass / http://localhost:5000/
  ProxyPassReverse / http://localhost:5000/
  <Proxy *>
      Order deny,allow
      Allow from all

Restart Apache2:

service restart apache2

Running behind an Nginx reverse proxy over HTTPS

Install nginx:

apt-get install nginx certbot

Create a SSL certificate with LetsEncrypt:

certbot certonly --nginx --agree-tos -d

Create an nginx vhost at /etc/nginx/sites-enabled/

cat <<EOF > /etc/nginx/sites-enabled/
server {

    location / {

    proxy_set_header Host $host;
    proxy_set_header X-Forwarded-Host $host;
    proxy_set_header X-Forwarded-Proto $scheme;

    listen [::]:443 ssl;
    listen 443 ssl;
    ssl_certificate /etc/letsencrypt/live/;
    ssl_certificate_key /etc/letsencrypt/live/;
    include /etc/letsencrypt/options-ssl-nginx.conf;
    ssl_dhparam /etc/letsencrypt/ssl-dhparams.pem;

Restart nginx:

service restart nginx

Using https without reverse proxy

The most common way of using LNbits via https is to use a reverse proxy such as Caddy, nginx, or ngriok. However, you can also run LNbits via https without additional software. This is useful for development purposes or if you want to use LNbits in your local network.

We have to create a self-signed certificate using mkcert. Note that this certificate is not “trusted” by most browsers but that’s fine (since you know that you have created it) and encryption is always better than clear text.

Install mkcert

You can find the install instructions for mkcert here.

Install mkcert on Ubuntu:

sudo apt install libnss3-tools
curl -JLO ""
chmod +x mkcert-v*-linux-amd64
sudo cp mkcert-v*-linux-amd64 /usr/local/bin/mkcert

Create certificate

To create a certificate, first cd into your LNbits folder and execute the following command on Linux:

openssl req -new -newkey rsa:4096 -x509 -sha256 -days 3650 -nodes -out cert.pem -keyout key.pem

This will create two new files (key.pem and cert.pem ).

Alternatively, you can use mkcert (more info):

# add your local IP (192.x.x.x) as well if you want to use it in your local network
mkcert localhost ::1

You can then pass the certificate files to uvicorn when you start LNbits:

poetry run uvicorn lnbits.__main__:app --host --port 5000 --ssl-keyfile ./key.pem --ssl-certfile ./cert.pem

LNbits running on Umbrel behind Tor

If you want to run LNbits on your Umbrel but want it to be reached through clearnet, Uxellodunum made an extensive guide on how to do it.

Docker installation

To install using docker you first need to build the docker image as:

git clone
cd lnbits
docker build -t lnbits-legend .

You can launch the docker in a different directory, but make sure to copy .env.example from lnbits there

cp <lnbits_repo>/.env.example .env

and change the configuration in .env as required.

Then create the data directory

mkdir data

Then the image can be run as:

docker run --detach --publish 5000:5000 --name lnbits-legend -e "LNBITS_BACKEND_WALLET_CLASS='FakeWallet'" --volume ${PWD}/.env:/app/.env --volume ${PWD}/data/:/app/data lnbits-legend

Finally you can access your lnbits on your machine at port 5000.