lightninglabs / lightning-terminal

Lightning Terminal: Your Home for Lightning Liquidity
MIT License
487 stars 82 forks source link

Terminal Web (https://terminal.lightning.engineering) showing old onion url #611

Closed mfbrj closed 11 months ago

mfbrj commented 11 months ago

Expected behavior Web Terminal should show the current onion url of the node as obtained from lncli getinfo.

Actual behavior Web terminal showing an old onion address, different from the address obtained from lncli getinfo.

To reproduce

  1. Configure lnd with tor v3 active. lnd will generate the file /root/.lnd/v3_onion_private_key
  2. Delete the file /root/.lnd/v3_onion_private_key.
  3. Restart lnd. This will generate a brand new /root/.lnd/v3_onion_private_key file, correspondent to a new .onion url.
  4. Go to https://terminal.lightning.engineering/<node pub key>/ and notice that page shows the old .onion url.

System information

Are you using Lightning Terminal as a standalone application or as part of Umbrel? Lightning Terminal standalone, deployead in a Kubernetes cluster; lnd remote.

What mode are you running Lightning Terminal in? Specifically of interest are the values of 'lnd-mode', 'faraday-mode', 'loop-mode' and 'pool-mode'. N/A

What version of Lightning Terminal are you using, where did you get it (website, self-compiled, etc)? Docker image lightninglabs/lightning-terminal:v0.10.4-alpha

What type of machine are you observing the error on (OS/CPU and disk type)? N/A

What is your operating system and its version? Host 6.1.0-0.deb11.6-amd64

Any extra information that might be useful in the debugging process. This is normally the contents of a litd.log file. Raw text or a link to a pastebin type site are preferred.

2023-07-31 14:34:22.803 [INF] LITD: LiT is running in mainnet, the taproot assets subserver do not support the `mainnet` network yet, disabling taproot assets subserver
2023-07-31 14:34:22.807 [INF] LITD: LiT version: 0.10.4-alpha commit=v0.10.4-alpha
2023-07-31 14:34:22.813 [INF] LITD: Listening for http_tls on: [::]:8443
2023-07-31 14:34:22.814 [INF] LITD: Listening for http on: [::]:8080
2023-07-31 14:34:22.837 [INF] SESS: Checking for schema update: latest_version=0, db_version=0
2023-07-31 14:34:22.837 [INF] LITD: Dialing lnd gRPC server at lnd-internal:10009
----------------------------------------------------------
 Lightning Terminal (LiT) by Lightning Labs               

 LND Operating mode      remote                               
 LND Node status         online                               
 LND Alias               <redacted>                               
 LND Version             0.16.4-beta commit=v0.16.4-beta                               
 LiT Version             0.10.4-alpha commit=v0.10.4-alpha                               
 Web interface           0.0.0.0:8443, 0.0.0.0:8080 (open https://localhost:8443 or http://localhost:8080 in your browser)                         
----------------------------------------------------------
2023-07-31 14:34:22.897 [INF] LITD: Connecting basic lnd client
2023-07-31 14:34:23.100 [INF] LITD: Connecting full lnd client
2023-07-31 14:34:23.100 [INF] LNDC: Creating lnd connection to lnd-internal:10009
2023-07-31 14:34:23.101 [INF] LNDC: Connected to lnd
2023-07-31 14:34:23.104 [INF] LNDC: Waiting for lnd to unlock
2023-07-31 14:34:23.108 [INF] LNDC: Wallet state of lnd is now: Lnd main server is ready for requests
2023-07-31 14:34:23.130 [INF] LNDC: lnd version: v0.16.4-beta, build tags 'autopilotrpc,signrpc,walletrpc,chainrpc,invoicesrpc,watchtowerrpc,neutrinorpc,monitoring,peersrpc,kvdb_postgres,kvdb_etcd,kvdb_sqlite'
2023-07-31 14:34:23.131 [INF] LNDC: Using network mainnet
2023-07-31 14:34:23.131 [INF] LNDC: Waiting for lnd to be fully synced to its chain backend, this might take a while
2023-07-31 14:34:23.149 [INF] LNDC: lnd is now fully synced to its chain backend
2023-07-31 14:34:23.283 [INF] LOOPD: Protocol version: MuSig2
2023-07-31 14:34:23.284 [INF] LOOPD: Swap server address: swap.lightning.today:11010
2023-07-31 14:34:23.285 [INF] LOOPD: Opening sqlite3 database at: /root/.loop/mainnet/loop_sqlite.db
2023-07-31 14:34:23.467 [INF] POOL: Version: 0.6.4-beta commit=v0.6.4-beta
2023-07-31 14:34:23.467 [INF] LOOPD: Waiting for updates
2023-07-31 14:34:23.467 [INF] LOOPD: Starting liquidity manager
2023-07-31 14:34:23.467 [INF] LOOPD: Starting swap client
2023-07-31 14:34:23.468 [INF] LOOP: Connected to lnd node '<redacted>' with pubkey <redacted> (version v0.16.4-beta, build tags 'autopilotrpc,signrpc,walletrpc,chainrpc,invoicesrpc,watchtowerrpc,neutrinorpc,monitoring,peersrpc,kvdb_postgres,kvdb_etcd,kvdb_sqlite')
2023-07-31 14:34:23.473 [INF] LOOP: Wait for first block ntfn
2023-07-31 14:34:23.486 [INF] LOOP: Starting event loop at height 801079
2023-07-31 14:34:23.609 [INF] POOL: Auction server address: pool.lightning.finance:12010
2023-07-31 14:34:23.617 [INF] CLDB: Checking for schema update: latest_version=1, db_version=1
2023-07-31 14:34:23.637 [INF] POOL: Using batch version 42 for connecting to auctioneer
2023-07-31 14:34:23.659 [INF] POOL: Using batch version 42 for connecting to auctioneer
2023-07-31 14:34:23.659 [INF] RPCS: Starting trader server
2023-07-31 14:34:23.687 [INF] RPCS: Connected to lnd node <redacted> with pubkey <redacted>
2023-07-31 14:34:23.710 [INF] ACCT: Watching spend of 6deee7a96c136843937720b03ae9d779ccd63867a635eb6927cbc3cb433fd12d:0 for account 038bc8aa57ade521bd6eb73d561b3911210e8facc97cd546361b023f56628953a1
2023-07-31 14:34:24.734 [INF] AUCT: Successfully connected to auction server
2023-07-31 14:34:25.200 [INF] FNDG: Starting funding manager
2023-07-31 14:34:25.201 [INF] FNDG: Funding manager is now active
2023-07-31 14:34:25.201 [INF] RPCS: Trader server is now active
2023-07-31 14:34:25.205 [INF] LITD: Starting LiT macaroon service
2023-07-31 14:34:25.306 [INF] AUTO: Starting Autopilot Client
2023-07-31 14:34:26.138 [INF] LITD: Starting LiT session server
mfbrj commented 11 months ago

The problem is related with cache in my browser.