Guide to create Lightning Address redirection on your domain

7 minute read

Understanding Lightning Addresses

Lightning Address is a reusable identifier that looks like an email address and can be used to send and receive payments over the Lightning Network. It is easy to remember unlike an LNURL. Some Lightning wallets and services provide this feature where they may either let you choose an identifier on their domain or will randomly generate one for you. For example: Wallet of Satoshi is a custodial Lightning wallet that auto generates one for you such as <randomidentifier>

Note: This is this is not an email address and cannot be used to send or receive emails, unless you also setup an email server and create an email address with that same identifier and domain.

To understand how Lightning Addresses are constructed have a look at the below image: Lightning Address illustrationSource: Lightning Address GitHub readme

Based on the above pictorial illustration let us try to breakdown a Lightning Address with an actual example. My Lightning Address is which decodes into the following URL If you visit that URL you will see a LNURL Pay request and response in JSON format. :

	"metadata":"[[\"text/plain\",\"Pay to Wallet of Satoshi user: scarredsofa23\"],[\"text/identifier\",\"\"]]",

Lightning wallets that can decode or support it can send or receive payments by converting the Lightning Address based on the above response of the LNURL Pay request and will facilitate the payment or receipt of the BOLT11 Invoice. It is likely that the Lightning Address service provider running the LNURLp endpoint will have it running on the following URL:[identifier]

Note: I have used Lightning Decoder to decode the Lightning Address.

How to setup Lightning Address redirection with your domain using GitHub pages to redirect to Wallet of Saotshi or GetAlby Lightning Address (Free and Easy)

This section of the guide is for those who own a domain or a subdomain and would like to make use of GitHub pages for setting up Lightning Address redirection.

  1. Point your domain or subdomain’s DNS to GitHub pages by setting up the below A records on your domain providers portal:

    Set the default or lowest possible TTL (Time To Live) value that your domain provider allows. This just tells the DNS resolver how long to cache a DNS query before updating.

    Depending on your domain provier you may have to enter @ or leave blank the host value to use the root domain in your NIP-05 identifier. If you want to use a subdomain enter the subdomain name in that field.

    Note: If GitHub updates the above IP addresses please refer to their page. Once you update your domain’s DNS it may take some time to propagate, anywhere from a few minutes to several hours.

  2. Register and Login to your GitHub account and visit here to create a new repository. Give your repository a name and make sure to select ‘Public’ repository if you want the GitHub Pages setup to be free. Using a ‘Private’ repository with GitHub pages is a paid feature and requires an upgrade.

    Note: If want to use an existing repository that already points to your custom domain or you want to use GitHubs free subdomain skip to step 3.

  3. Create a new file in your repository in the following directory path: <repository>/.well-known/lnurlp/<yourusername>

    Note: <yourusername> will be part of your Lightning Address <yourusername> Replace it with what you want.

    Redirect to Wallet Of Satoshi(WOS) Lightning address: Add the below content to your <yourusername> file. Here’s an example. To view your Wallet Of Satoshi content to paste into this file, visit this URL<your-WOS-user> and view the JSON raw data. Copy it and paste it into <yourusername> file:

    Note: Your WOS User is usually in your Lightning Address: <your-WOS-user>

    Sample JSON that needs to go into the file:

         "callback": "<your-callback-payreq>",
         "maxSendable": 100000000000,
         "minSendable": 1000,
         "metadata": "[[\"text/plain\",\"Pay to Wallet of Satoshi user: <your-WOS-user>\"],[\"text/identifier\",\"<your-WOS-user>\"]]",
         "commentAllowed": 32,
         "tag": "payRequest"

    Redirect to Getalby Lightning address: Add the below content to your <yourusername> file. To view your Getalby content to paste into this file, visit this URL<your-getalby-user> and view the JSON raw data. Copy it and paste it into <yourusername> file. For example: My getalby:

    Note: Your Getlalby User is in your Lightning Address:<your-getlaby-user>

    Sample JSON that needs to go into the file:

         "status": "OK",
         "tag": "payRequest",
         "commentAllowed": 255,
         "callback": "<your-getlaby-user>/callback",
         "metadata": "[[\"text/identifier\", \"<your-getlaby-user>\"], [\"text/plain\", \"Sats for <your-getlaby-user>\"]]",
         "minSendable": 1000,
         "maxSendable": 11000000000,
         "payerData": {
             "name": {
             "mandatory": false
             "email": {
             "mandatory": false
  4. Go to the ‘Settings’ page of your repository and navigate to ‘Pages’ under Code and automation section on the sub menu or modify the below URL to visit it directly:<your-github-username>/<repository>/settings/pages

    Note: Replace <your-github-username> with your GitHub username and <repository> with the repository name.

    Under Build and deployment select source as ‘Deploy from a branch’. Select branch as ‘main’ or ‘master’, ‘/root’ and click save.

    Under Custom domain enter your domain and click save. GitHub will perform a DNS check to verify that the A records setup on your domain in step 1 are accurate.

    Note: It this fails, wait for your domain’s DNS to complete propagation and retry. DNS propagation could take anywhere from a few minutes to hours.

    Check ‘Enforce HTTPS’. This will generate an SSL certificate for your Domain from GitHub for free and assign it.

    Note: At times, this may take a while to generate.

  5. Create a new file _config.yml or update it to add the below lines:

     - .well-known
  6. Try sending some Bitcoin or Sats to <yourusername> to test. If it works you are all done. If not, verify the above steps are completed.

How to setup Lightning Address redirection using your web server

If you own a and a web server and would like to use an identifier on your domain, but would like to receive payments or to allow others to send payments to you using <youridentifier> then all you need to do is to setup a simple redirection on your web server.

Note: To keep this short, I will assume that your domain’s or subdomain’s DNS is already pointing to your web server using either an A record, AAAA record or CNAME and can access your web server.

Setup on NGINX

Open /etc/nginx/sites-available/<> with a text editor like nano or vim from your console that you use to SSH into your server. Replace <> with your This should also automatically update the domain file located in /etc/nginx/sites-enabled/ because of the symbolic link.

  1. Edit the below file using a text editor:

    $ nano /etc/nginx/sites-enabled/<>

    Sample configuration:

    server {
        location /.well-known/lnurlp {
            rewrite ^/.well-known/lnurlp/<youridentifier>$<youractualwalletidentifier> redirect;
            add_header 'Access-Control-Allow-Origin' '*';

    Example setup with my Lightning Address:

    server {
        location /.well-known/lnurlp {
            rewrite ^/.well-known/lnurlp/ezofox$ redirect;
            add_header 'Access-Control-Allow-Origin' '*';

    As per the above example I can now share as my Lightning Address and this will forward or redirect payments to my original Lightning Address wallet.

    Details of the configuration:

    • rewrite: Used to tell NGINX to match the URL pattern eg: /.well-known/lnurlp/[identifier] to another URL.

    • ^/.well-known/lnurlp/<youridentifier>: Redirect from URL.

    • $: End of string.

    •<youractualwalletidentifier>: Redirect to URL. Replace with any other Lightning Address service providers URL.

    • add_header 'Access-Control-Allow-Origin' '*';: Adds CORS Access-Control-Allow-Origin permission which is required by some clients like to allow Lightning tips.

  2. Reload or restart NGINX service:

     $ service nginx reload 


     >$ service nginx restart

Setup on Apache

Redirection on Apache is achieved using the Redirect Directive. Depending on OS or your configuration you may have to edit with your text editor nano, vim or others one of these files /etc/apache2/sites-available/000-default.conf or /etc/apache2/sites-available/ (In Ubuntu) or /etc/httpd/conf.d/vhost.conf (In CentOS) and add a redirection from /.well-known/lnurlp/<youridentifier> to<youractualwalletidentifier>


A simple implementation would be to edit the .htaccess in your domain’s root directory and add the redirect directive as shown below:

Redirect /.well-known/lnurlp/<youridentifier><youractualwalletidentifier>
<If "%{REQUEST_URI} =~ m#^/.well-known/lnurlp/#">
Header always set Access-Control-Allow-Origin "*"

Details of the configuration:

  • Redirect: Redirection for Apache
  • /.well-known/lnurlp/<youridentifier>: The redirect from path. All you need is to setup the `.well-known’ folder.
  •<youractualwalletidentifier>: Replace with relevant Lightning Address provider’s redirect to URL.
  • <If "%{REQUEST_URI} =~ m#^/.well-known/lnurlp/#"></If>: Use of RegEx folder path to conditionally allow CORS Access-Control-Allow-Origin only for lnurlp path for security purposes.
  • Header always set Access-Control-Allow-Origin "*": Adds CORS Access-Control-Allow-Origin permission which is required by some clients like to allow Lightning tips.

For any other web servers, you may need to read the respective documentation of those web server implementations to understand how to perform a similar permanent redirection.

If you found this guide useful feel free to leave a Lightning tip at:

Lightning Address:, OR LNURL: Tipjar