-
Notifications
You must be signed in to change notification settings - Fork 366
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Issue with externalip and externalhosts configuration in LND #927
Comments
@rockstardev I'm not sure why we are using the The docker entrypoint has two lines where it sets
For the latter I haven't found any hints regarding why even use the For the former it would always be a hostname rather than an IP address. Imho it would be good to clarify that in the variable name and set What are your thoughts? |
First of all: you dont need to set an onion adress for lnd as an external IP Most importantly you need to set:
for lnd to get an onion address. externalip= should be only used when you have a fixed IP adress. No port needed to be set, it takes the port from the port given at the for dynamic IP adresses use: externalhosts="dyndnsaddress.com" should be used so lnd resolveds this adress periodically to set and advertise this adress as its own. You need a ddns client that updates the IP adress to your dyndnsprovider. Externalhosts actually can also be used to resolve a domain for a fixed IP not only for dydns You should let users set indepentently and optionally set an externalip for example to make use of wireguard vpn infront of lnd like for example tunnelsats |
a future possible setup-way could be: setup externalhosts=$BTCPAY_HOST remove externalip=xyz.onion |
adresses this issue: btcpayserver#927
There is currently no way to set externalip to an IP address through btcpay vars.
Btcpay will use the value of
BTCPAY_HOST
forexternalip=
which is the primary DOMAIN name for the site.If you set the var
BTCPAY_ANNOUNCEABLE_HOST
to an IP address it will be overridden by btcpay-setup.sh and reset to theBTCPAY_HOST
domain.This can cause issues when migrating to new IP or if serving the btcpay webservice behind a DNS proxy like cloudflare which will resolve the domain to cloudflares IP address instead of the LND nodes public IP address.
The assignment of a domain to
externalip
also seems to not be best practice when there is a configuration variable calledexternalhosts
that is intended for DNS resolution.Shouldn't BTCPAY allow for the
externalip
in LND conf to be set as an IP address through ENV vars for servers that have a static IP, and have the option to add BTCPAY_HOST / BTCPAY_ADDITIONAL_HOSTS asexternalhosts
entries for those that have a dynamic IP?The text was updated successfully, but these errors were encountered: