RTL stuck at 'Unlock' screen about rtl HOT 9 CLOSED

You have a working config now, in case you want to run RTL.
Closing this issue now.
Feel free to open another, in case you run into any other issues or if you have any feedback from your experience on RTL. :-)
Thanks.

from rtl.

I've finally gotten both rpc and rest services working now together!

My solution (source):

• add tlsextraip=0.0.0.0 to the lnd.conf file
• delete the tls.cert file
• restart lnd.

from rtl.

@vindard
Please check if port # 8080 open on your rpi firewall.
And try with the below modified lnd.conf:

# RaspiBolt LND Mainnet: lnd configuration
# /home/bitcoin/.lnd/lnd.conf

[Application Options]
debuglevel=info
maxpendingchannels=5
alias=[redacted]
color=#68F442
minchansize=140000
restlisten=192.168.0.201:8080
#listen=localhost
#nat=false

#[Tor]
#tor.active=true
#tor.v3=true

[Bitcoin]
bitcoin.active=1

# enable either testnet or mainnet
#bitcoin.testnet=1
bitcoin.mainnet=1

bitcoin.node=bitcoind

[Bitcoind]
bitcoind.rpcuser=[redacted]
bitcoind.rpcpass=[redacted]
bitcoind.zmqpubrawblock=tcp://127.0.0.1:28332
bitcoind.zmqpubrawtx=tcp://127.0.0.1:28333

[autopilot]
autopilot.active=0
autopilot.maxchannels=5
autopilot.allocation=0.6

from rtl.

Ah, the problem was rpclisten=0.0.0.0:10009! Now that that one line is gone from lnd.conf file, RTL starts up perfectly.

Note: I also commented back out everything under the [Bitcoind] as I had it originally and it still worked great.

Hmm, that's less than ideal though since I would like to have the gRPC interface available for other apps I use. Any ideas around how we can have both restlisten and rpclisten enabled in the config file?

It could be made as a separate open issue that someone works towards maybe...

from rtl.

@vindard
Both these setting should not conflict. If you need rpclisten, try with the below:
rpclisten=127.0.0.1:10009

We are able to run RTL in both local and remote settings with both the entries in the lnd.conf file.

from rtl.

It looks like it's some sort of bug with lnd itself (#1567).

I've tried messing around with various combinations of restlisten and rpclisten being alternatively/simultaneously enabled, with localhost/0.0.0.0/127.0.0.1/localhost/192.168.0.201 (RPi IP) being toggled as well.

I haven't been able to find a workable combination as yet that allows both gRPC and REST to function at the same time but I think I'll just wait for lnd to work that out at some point in the future.

For future reference, my setup is a Raspberry Pi 3 running Raspbian Stretch Lite for the OS.

Thanks for the help @saubyk! ✌

from rtl.

Funnily it's now almost 2 years later and I'm setting up RTL on a new node and I think I've run into some version of this problem again (was searching my problem and found this issue) 🙈

• I can successfully curl the v1/getinfo endpoint using the admin.macaroon I have available for RTL so I don't think it's a REST api access issue, and
• the lnd wallet is already unlocked anyway

I'll mess around and see what I can figure out again 🤔

from rtl.

@vindard Feel free to share your RTL-config.json to double check your configuration after masking critical information.

from rtl.

Ah I figured it out after I noticed this funny little log message

INFO: RTLConf => Selected Node Updated To: "Node 1"
Common Set Options Error:{"errno":-20,"syscall":"open","code":"ENOTDIR","path":"/home/rtl/.lnd/admin.macaroon/admin.macaroon"}
Common Update Selected Node Options Error:{"errno":-20,"syscall":"open","code":"ENOTDIR","path":"/home/rtl/.lnd/admin.macaroon/admin.macaroon"}

It turns out I had set the macaroonPath path value to point directly to the file instead of its parent dir.

As a sidenote though, is there a reason why the macaroonPath value wants the parent dir path but the configPath value wants the path to the file?

from rtl.