Skip to content
Ride The Lightning - A full function web browser app for LND and C-Lightning
TypeScript HTML JavaScript CSS Other
Branch: master
Clone or download
ShahanaFarooqui Error handling fix
Error handling fix
Latest commit ea86c12 Nov 6, 2019
Type Name Latest commit message Commit time
Failed to load latest commit information.
.circleci docker_layer caching false Oct 16, 2019
.github/ISSUE_TEMPLATE Update issue templates Oct 9, 2018
angular Error handling fix Nov 6, 2019
controllers InitWallet with Passphrase fixes Nov 6, 2019
docker Docker regtest setup (#108) Apr 14, 2019
docs Update Oct 29, 2019
e2e Merging Angular pre-build code Mar 19, 2019
product management Merging Angular pre-build code Mar 19, 2019
routes InitWallet with Passphrase fixes Nov 6, 2019
screenshots Updated RTL LND Architecture Sep 16, 2019
src Error handling fix Nov 6, 2019
.DS_Store Initial commit Sep 15, 2018
.editorconfig Lazy Load Completed Sep 1, 2019
.gitattributes Initial commit Sep 15, 2018
.gitignore Issue 181 refresh page Sep 19, 2019
Dockerfile Have better docker caching (#63) Feb 25, 2019
Dockerfile.arm32v7 Have better docker caching (#63) Feb 25, 2019
Dockerfile.arm64v8 updated docker arm64 Aug 16, 2019
LICENSE Create LICENSE Sep 28, 2018 readme updated Oct 16, 2019
_config.yml Set theme jekyll-theme-hacker Jan 11, 2019
angular.json Angular 8 Update Jul 27, 2019
app.js OnChain & Payments Sep 8, 2019
common.js InitWallet with Passphrase fixes Nov 6, 2019
connect.js Landing page input on getInfo Nov 6, 2019
package-lock.json Fix #199 Clicking on restore channel crashing RTL Oct 27, 2019
package.json Fix #199 Clicking on restore channel crashing RTL Oct 27, 2019
prebuild.js Merging Angular pre-build code Mar 19, 2019
protractor.conf.js Merging Angular pre-build code Mar 19, 2019
rtl.js incomplete 2 Apr 6, 2019
sample-RTL-Multi-Node-Conf.json Issue #160 default node setup Jun 19, 2019
sample-RTL.conf Channel backup & #157 custom expiry time for invoice Jun 17, 2019
tsconfig.json Peers Sep 7, 2019
tslint.json Merging Angular pre-build code Mar 19, 2019

Ride The Lightning (RTL)

Known Vulnerabilities license

Stable Release: v0.5.3 (Docker build pending)

Intro -- Application Features -- Road Map -- LND API Coverage -- Application Configurations -- C-lightning


RTL is a full function, device agnostic, web user interface to help manage lightning node operations. RTL is available on LND and C-Lightning implementations.

This page covers instructions for LND. For C-lightning, refer to this page.

Lightning Network Daemon(LND) is an implementation of Lightning Network BOLT protocol by Lightning Labs.

Pre-requisite for running RTL is a functioning and synced LND node. You can setup your own node, by following the below guides:

  • Windows/Mac users can follow Pierre Rochard's Node Launcher
  • Linux or Raspberry Pi users can follow Stadicus's guide

For detailed screenshots and UI operation guide you can visit our medium post

RTL is available on the below platforms/services:

Docker Image:



  • Functioning and synced LND lightning node.
  • Node.js, which can be downloaded here
    • On Ubuntu, g++ is required to install the node-sass dependency. This is available in the build-essential package.
      • The Most recent versions of node.js might give errors while installing node-sass. Use node.js LTS version 8 or 10 as a solution.
  • Recommended Browsers: Chrome, Firefox, MS Edge


First time setup

  • Fetch sources from RTL git repository, by executing the below on the command prompt:

$ git clone

  • Change directory to RTL folder:

$ cd RTL

  • Fetch the dependencies and build the application by running:

$ npm install

Or: Update existing build

$ cd RTL
$ git reset --hard HEAD
$ git clean -f -d
$ git pull
$ npm install

Prep for Execution

RTL requires its own config file RTL.conf, to start the server and provide user authentication on the app.

Advanced users can refer to this page, for config settings required to manage multiple LND nodes

  • Rename sample-RTL.conf file to RTL.conf.
  • Locate the complete path of the readable macroon file (admin.macroon) on your node and the lnd.conf file.
  • Modify the RTL.conf file per the example file below

Example RTL.conf:




For details on all the configuration options refer to this page.

User Authentication on RTL

RTL requires the user to be authenticated by the application first, before allowing access to LND functions. There are two options to configure authentication on RTL, depending on the nodeAuthtype value provided in RTL.conf.

  • Option 1: nodeAuthType=DEFAULT; Password provided in lnd.conf for the rpc setting for bitcoind will be used for authentication.
  • Option 2: nodeAuthType=CUSTOM; Specific password must be provided in RTL.conf (in plain text) for authentication. Password should be set with rtlPass=<user defined> in the [Authentication] section of RTL.conf

Start the Server

Run the following command:

$ node rtl

If the server started successfully, you should get the below output on the console:

$ Server is up and running, please open the UI at http://localhost:3000

Optional: Running RTL as a service (Rpi or Linux platform users)

In case you are running a headless Rpi or a Linux node, you can configure RTL as a service.

  • Create RTL systemd unit and with the following content. Save and exit.
# Raspibolt RTL: systemd unit for RTL
# /etc/systemd/system/RTL.service

Description=RTL daemon

ExecStart=/usr/bin/node <Full path of the RTL folder>/rtl

  • enable and start RTL
$ sudo systemctl enable RTL
$ sudo systemctl start RTL
  • montior the RTL log file in realtime(exit with Ctrl-C)

$ sudo journalctl -f -u RTL

Accessing the Application

You can access the application in multiple setups (Please make note of the 4th exception):

  1. Same device as the server: Open your browser at the following address: http://localhost:3000 to access the RTL application.

  2. Remotely from another device on the same local network (home network) as the node(RTL server+LND running on the same device):

  • Ensure that the if a firewall running on your node, it allows access on port 3000 (or the custom port configured for RTL).
  • Determine the IP address of your node to access the application. E.g. if the IP address of your node is then open your browser at the following address: to access RTL.
  1. Config tweaks for running RTL server and LND on separate devices on the same network can be found here.

  2. Any Other setup: Please be advised, if you are accessing your node remotely via RTL, its critical to encrypt the communication via use of https. You can use solutions like nginx and letsencrypt or TOR to setup secure access for RTL.

  • Sample SSL setup guide can be found here
  • (For advanced users) A sample SSL guide to serve remote access over an encrypted Tor connection can be found here


In case you are running into issues with the application or if you have feedback, feel free to open issues on our github repo. You can also reach out to us via twitter DM on @Suheb__ or @RTL_App. Thanks for your interest.

You can’t perform that action at this time.