[bug]: LND-CLN err=update_fee XXXXXX unaffordable about lnd HOT 13 CLOSED

Asked for some node details here: ElementsProject/lightning#7254 (comment)

from lnd.

Asked for some node details here: ElementsProject/lightning#7254 (comment)

I answered you there: ElementsProject/lightning#7254 (comment)

BTW I think we may have found another related bug in LND: when feeurl cannot be retrived, it seems it defaults to 253sat/kw, which is ridiculous. This might be the problem, plus unable to renegotiate with CLN once the new low fee is stablished.

I will open another issue.

from lnd.

This appears to be a duplicate of #7756
Has been fixed with #7805

Will be available with 0.18

from lnd.

This appears to be a duplicate of #7756 Has been fixed with #7805

Will be available with 0.18

Anything I can do today to avoid expensive FC?

from lnd.

cc @ziggie1984 in case he has any ideas

from lnd.

The only way for this to recover is to wait until fees go down, or ask your CLN node to run a setting which discards the fee check.

CLN Setting:

--ignore-fee-limits=BOOL

from lnd.

The only way for this to recover is to wait until fees go down, or ask your CLN node to run a setting which discards the fee check.

CLN Setting:

--ignore-fee-limits=BOOL

I'm been told in the Telegram group that modifying this setting doesn't help. Is that right?

from lnd.

The only way for this to recover is to wait until fees go down, or ask your CLN node to run a setting which discards the fee check.

CLN Setting:

--ignore-fee-limits=BOOL

My CLN peer says he tried running with that setting. Fees at 100 are not that high. I use feeurl to feed more realistic estimates, not bitcoin core. Maybe CLN gets too high estimates (my bitcoin core thinks the fees are 1150 still), because they don't have such a setting.

from lnd.

CLN related bug: ElementsProject/lightning#7254

from lnd.

From CLN Docs:

ignore-fee-limits=BOOL

Allow nodes which establish channels to us to set any fee they want. This may result in a channel which cannot be closed, should fees increase, but make channels far more reliable since we never close it due to unreasonable fees. Note that this can be set on a per-channel basis with lightning-setchannel(7).

see: https://github.com/ElementsProject/lightning/blob/master/doc/lightningd-config.5.md

from lnd.

From CLN Docs:

ignore-fee-limits=BOOL

Allow nodes which establish channels to us to set any fee they want. This may result in a channel which cannot be closed, should fees increase, but make channels far more reliable since we never close it due to unreasonable fees. Note that this can be set on a per-channel basis with lightning-setchannel(7).

see: https://github.com/ElementsProject/lightning/blob/master/doc/lightningd-config.5.md

Made no difference, same error ((

from lnd.

Can you report detailed logs of both nodes while this setting is active.

from lnd.

Can you report detailed logs of both nodes while this setting is active.

My CLN peer did not send me his logs. My LND logs did not show anything different. The HTLC just expired and the channel FCd (((

from lnd.