Cloudron makes it easy to run web apps like WordPress, Nextcloud, GitLab on your server. Find out more or install now.


Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • Bookmarks
  • Search
Skins
  • Light
  • Brite
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (No Skin)
  • No Skin
Collapse
Brand Logo

Cloudron Forum

Apps | Demo | Docs | Install
  1. Cloudron Forum
  2. Apps
  3. First Dawarich, now BTCPayServer!

First Dawarich, now BTCPayServer!

Scheduled Pinned Locked Moved Apps
5 Posts 2 Posters 123 Views 2 Watching
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • scookeS Offline
    scookeS Offline
    scooke
    wrote last edited by
    #1

    Thanks to @timconsidine and his https://ccai.appx.uk/ I've installed BTCPayServer. Quick questions...

    The Dashboard tells me the nodes are syncing... but there are NO nodes, correct, by default? I need to connect it to a Bitcoin node elsewhere, yes? I ask because I don't want to wake up tomorrow to find out my server has run out of space!

    Any other tips on how to connect that BTC node, as well as Lightning stuff?

    Thank you!

    A life lived in fear is a life half-lived

    1 Reply Last reply
    1
    • scookeS Offline
      scookeS Offline
      scooke
      wrote last edited by
      #2

      I think I messed up something specific. I entered the IP for the Bitcoin node I have running elsewhere. Do I need to make a user, too, on that instance to login to the PRC?

      And, I entered my.ip for the last item, explorer_bind, but I think that needed to stay as the local Docker IP, right> Well, I forget what that was. Could someone check and tell me what it should be please?

      Bitcoin RPC Configuration

      bitcoin:
      rpc_user: "user"
      rpc_password: "password"
      rpc_host: "my.ip"
      rpc_port: 8332
      node_endpoint: "my.ip:8333"

      Network Configuration

      network: "mainnet"

      Database Configuration (Cloudron managed)

      These are automatically set by Cloudron environment variables

      postgres:

      host: ${CLOUDRON_POSTGRESQL_HOST}

      port: ${CLOUDRON_POSTGRESQL_PORT}

      username: ${CLOUDRON_POSTGRESQL_USERNAME}

      password: ${CLOUDRON_POSTGRESQL_PASSWORD}

      database: ${CLOUDRON_POSTGRESQL_DATABASE}

      BTCPay Server Configuration

      btcpayserver:
      host: "${CLOUDRON_APP_DOMAIN}"
      protocol: "https"
      datadir: "/app/data/btcpayserver"

      NBXplorer Configuration

      nbxplorer:
      network: "mainnet"
      chaintype: "BTC"
      explorer_port: 32838
      explorer_bind: "WHAT WAS THIS:32838"

      A life lived in fear is a life half-lived

      1 Reply Last reply
      0
      • nostrdevN Offline
        nostrdevN Offline
        nostrdev
        wrote last edited by nostrdev
        #3

        If you install bitcoin core, the btcpay server will automatically use your local (cloudron) instance

        we didn't test the install against a remote server but your config looks good. Your IP is a regular IP right, not a domain?

          rpc_user: "bitcoin"
          rpc_password: "pass"
          rpc_host: "172.28.0.2"
          rpc_port: 8332
          node_endpoint: "172.28.0.2:8333"
        

        The nbexplorer thing is internal to btcpay server (this was the hardest part about setting up the container)

        Does your remote btc core instance have rpc enabled? something like this in your bitcoin.conf file:

        rpcauth=bitcoin:pass
        
        scookeS 1 Reply Last reply
        0
        • nostrdevN nostrdev

          If you install bitcoin core, the btcpay server will automatically use your local (cloudron) instance

          we didn't test the install against a remote server but your config looks good. Your IP is a regular IP right, not a domain?

            rpc_user: "bitcoin"
            rpc_password: "pass"
            rpc_host: "172.28.0.2"
            rpc_port: 8332
            node_endpoint: "172.28.0.2:8333"
          

          The nbexplorer thing is internal to btcpay server (this was the hardest part about setting up the container)

          Does your remote btc core instance have rpc enabled? something like this in your bitcoin.conf file:

          rpcauth=bitcoin:pass
          
          scookeS Offline
          scookeS Offline
          scooke
          wrote last edited by
          #4

          @nostrdev said in First Dawarich, now BTCPayServer!:

          bitcoin.conf file

          Yes, I'm using the IP of the server where the node is running. I made a rpc_user and password, but am not sure where to put it. They have an editable field, plus an editable app.env field... but no direction as to which file takes info like rpc_user, etc.

          Thank you @nostrdev . This is the last thing, I think, stopping things from working... there is no bitcoin.conf! And though I know I have to make it, their setup is so niche that there also isn't a bitcoin directory, nor a .bitcoin directory, within which the conf file normally resides. I'm trying to figure out where to put it, if it is even called bitcoin.conf. Their docker-compose.yml AND docker-compose.json each reference so many locations, none of which are simply called "bitcoin" as a directory. Very frustrating!

          Of course, I've posted help on the rt forums.... ONE person after days and days, who isn't even familiar with Bitcoin, tried to help. Pretty sad. I had more well-intentioned replies on a Reddit post within minutes. THIS is why I love Cloudron. It works, and if needed, help is not far.

          A life lived in fear is a life half-lived

          1 Reply Last reply
          0
          • nostrdevN Offline
            nostrdevN Offline
            nostrdev
            wrote last edited by nostrdev
            #5

            any reason you can't just run your Bitcoin node on your cloudron instance? it's prunable, which means it won't take loads of space.

            The rpc user/ pass definitely needs to be in the bitcoin.conf, it also needs to be salted/hashed, see: https://github.com/jlopp/bitcoin-core-rpc-auth-generator

            1 Reply Last reply
            1
            Reply
            • Reply as topic
            Log in to reply
            • Oldest to Newest
            • Newest to Oldest
            • Most Votes


            • Login

            • Don't have an account? Register

            • Login or register to search.
            • First post
              Last post
            0
            • Categories
            • Recent
            • Tags
            • Popular
            • Bookmarks
            • Search