Rtl web interface unreachable afetr overnight restart

I’m running StartOs on a B-link Mini pc. After an apparent overnight restart, RTL stopped opening. RTL homepage will not open at all just a thinking blank page login never appears. StartOS says RTL is running and healthy. LND is working, fully synced, and its dashboard opens.I’ve tried RTL’s local IP address, dot-local address, and Tor address. None works. I rebuilt RTL, but that did not fix it. The RTL logs say the server is running. I have funded lightning channels and don’t want to risk losing them. Can someone help me safely figure out why RTL won’t open? I also have a warning in LND that my continuous Google Drive backup failed which also was working before the overnight reset. The error says that it couldn’t find the root directory ID. Not sure if it is related just thought i would throw it in here as well. Thank you.

Your channels and funds aren’t at risk from any of this. They live in LND, and RTL is only a dashboard that talks to LND, so nothing you do to RTL (restarting it, rebuilding it, even uninstalling and reinstalling it) touches them. The one thing to avoid is uninstalling LND.

A page that stays blank and loading on every address, Tor included, usually means the RTL page itself loads but then waits forever for an answer from the RTL server behind it.

  1. Which versions of StartOS, RTL and LND you’re on. Each is shown on the service’s page and under System.

  2. Open RTL in a private or incognito window and leave it loading for a minute. Then open RTL’s Logs in StartOS and copy everything from the last couple of minutes, not just the “server running” line. That shows what RTL tried when your browser asked for the page.

  3. In LND, does Health show every check green?

We reproduced the same situation in a new private window (solid purple screen with decimal point going back and forth in tab) Even though RTL showing running. StartOs 0.4.0.1, LND 0.21.3-Beta, RTL 0.15.12.0. LND is running ,unlocked, and synced, and we have downloaded RTL Logs to attach.

8+00:00  Started container-runtime.service - StartOS Container Runtime.
2026-09-30T21:20:49+00:00  Listening on /media/startos/rpc/service.sock
2026-09-30T21:20:52+00:00  Initializing...
2026-09-30T21:20:52+00:00  Initialization complete.
2026-09-30T21:25:02+00:00  Starting Ride The Lightning...
2026-09-30T21:25:02+00:00  adding callback 1
2026-09-30T21:25:02+00:00  Launching primary...
2026-09-30T21:25:05+00:00  .const() triggered
2026-09-30T21:25:05+00:00  Restarting service...
2026-09-30T21:25:05+00:00  Starting Ride The Lightning...
2026-09-30T21:25:05+00:00  adding callback 2
2026-09-30T21:25:05+00:00  Launching primary...
2026-09-30T21:25:06+00:00  [9/30/2026,
 9:25:06 PM] INFO: RTL => Server is up and running, please open the 
UI at http://0.0.0.0:80 or your proxy configured url.
2026-09-30T21:27:59+00:00  Starting Ride The Lightning...
2026-09-30T21:27:59+00:00  adding callback 3
2026-09-30T21:27:59+00:00  Launching primary...
2026-09-30T21:28:00+00:00  [9/30/2026,
 9:28:00 PM] INFO: RTL => Server is up and running, please open the 
UI at http://0.0.0.0:80 or your proxy configured url.
2026-09-30T22:01:42+00:00  [9/30/2026, 10:01:42 PM] ERROR: Authenticate => Invalid Password! Failed IP 127.0.0.1: {"error":"Invalid password."}
2026-09-30T22:01:46+00:00  [9/30/2026, 10:01:46 PM] ERROR: Authenticate => Invalid Password! Failed IP 127.0.0.1: {"error":"Invalid password."}
2026-10-01T13:14:22+00:00  [10/1/2026, 1:14:22 PM] ERROR: Authenticate => Invalid Password! Failed IP 127.0.0.1: {"error":"Invalid password."}
2026-10-02T19:58:53+00:00  [10/2/2026, 7:58:53 PM] ERROR: Authenticate => Invalid Password! Failed IP 127.0.0.1: {"error":"Invalid password."}
2026-10-02T19:58:54+00:00  [10/2/2026, 7:58:54 PM] ERROR: Authenticate => Invalid Password! Failed IP 127.0.0.1: {"error":"Invalid password."}
2026-10-02T19:59:51+00:00  [10/2/2026, 7:59:51 PM] ERROR: Authenticate => Invalid Password! Failed IP 127.0.0.1: {"error":"Invalid password."}
2026-10-02T20:00:18+00:00  [10/2/2026, 8:00:18 PM] ERROR: Authenticate => Invalid Password! Failed IP 127.0.0.1: {"error":"Invalid password."}
2026-10-03T17:38:08+00:00  [10/3/2026, 5:38:08 PM] ERROR: App => Invalid CSRF token. Form tempered..
2026-10-04T04:47:34+00:00  [10/4/2026, 4:47:34 AM] ERROR: Authenticate => Invalid Password! Failed IP 10.0.3.1: {"error":"Invalid password."}
2026-10-04T04:48:20+00:00  [10/4/2026, 4:48:20 AM] ERROR: Authenticate => Invalid Password! Failed IP 10.0.3.1: {"error":"Invalid password."}
2026-10-04T04:48:25+00:00  [10/4/2026, 4:48:25 AM] ERROR: Authenticate => Invalid Password! Failed IP 10.0.3.1: {"error":"Invalid password."}
2026-10-04T20:12:43+00:00  [10/4/2026, 8:12:43 PM] ERROR: App => Invalid CSRF token. Form tempered..
2026-10-04T20:12:54+00:00  [10/4/2026, 8:12:54 PM] ERROR: Authenticate => Invalid Password! Failed IP 127.0.0.1: {"error":"Invalid password."}
2026-10-06T02:13:26+00:00  [10/6/2026, 2:13:26 AM] ERROR: Authenticate => Invalid Password! Failed IP 10.0.3.1: {"error":"Invalid password."}
2026-10-06T02:13:40+00:00  [10/6/2026, 2:13:40 AM] ERROR: Authenticate => Invalid Password! Failed IP 10.0.3.1: {"error":"Invalid password."}
2026-10-06T13:04:59+00:00  [10/6/2026, 1:04:59 PM] ERROR: Authenticate => Invalid Password! Failed IP 127.0.0.1: {"error":"Invalid password."}
2026-10-06T13:05:07+00:00  [10/6/2026, 1:05:07 PM] ERROR: Authenticate => Invalid Password! Failed IP 127.0.0.1: {"error":"Invalid password."}
2026-10-06T13:05:16+00:00  [10/6/2026, 1:05:16 PM] ERROR: Authenticate => Invalid Password! Failed IP 127.0.0.1: {"error":"Invalid password."}
2026-10-06T19:02:13+00:00  [10/6/2026, 7:02:13 PM] ERROR: Authenticate => Invalid Password! Failed IP 127.0.0.1: {"error":"Invalid password."}
2026-10-06T19:02:33+00:00  [10/6/2026, 7:02:33 PM] ERROR: Authenticate => Invalid Password! Failed IP 127.0.0.1: {"error":"Invalid password."}
2026-10-06T19:02:41+00:00  [10/6/2026, 7:02:41 PM] ERROR: Authenticate => Invalid Password! Failed IP 127.0.0.1: {"error":"Invalid password."}
2026-10-08T13:24:18+00:00  [10/8/2026, 1:24:18 PM] ERROR: Authenticate => Invalid Password! Failed IP 127.0.0.1: {"error":"Invalid password."}
2026-10-08T13:24:34+00:00  [10/8/2026, 1:24:34 PM] ERROR: Authenticate => Invalid Password! Failed IP 127.0.0.1: {"error":"Invalid password."}
2026-10-13T13:41:30+00:00  .const() triggered
2026-10-13T13:41:30+00:00  Restarting service...
2026-10-13T13:41:30+00:00  Starting Ride The Lightning...
2026-10-13T13:41:31+00:00  adding callback 4
2026-10-13T13:41:31+00:00  Launching primary...
2026-10-13T13:41:33+00:00  .const() triggered
2026-10-13T13:41:33+00:00  Restarting service...
2026-10-13T13:41:33+00:00  Starting Ride The Lightning...
2026-10-13T13:41:33+00:00  adding callback 5
2026-10-13T13:41:33+00:00  Launching primary...
2026-10-13T13:41:34+00:00  [10/13/2026,
 1:41:34 PM] INFO: RTL => Server is up and running, please open the 
UI at http://0.0.0.0:80 or your proxy configured url.
2026-10-13T13:48:00+00:00  .const() triggered
2026-10-13T13:48:00+00:00  Restarting service...
2026-10-13T13:48:00+00:00  Starting Ride The Lightning...
2026-10-13T13:48:00+00:00  adding callback 6
2026-10-13T13:48:00+00:00  Launching primary...
2026-10-13T13:48:01+00:00  .const() triggered
2026-10-13T13:48:01+00:00  Restarting service...
2026-10-13T13:48:01+00:00  Starting Ride The Lightning...
2026-10-13T13:48:01+00:00  adding callback 7
2026-10-13T13:48:01+00:00  Launching primary...
2026-10-13T13:48:01+00:00  [10/13/2026,
 1:48:01 PM] INFO: RTL => Server is up and running, please open the 
UI at http://0.0.0.0:80 or your proxy configured url.
2026-10-13T13:49:34+00:00  Starting Ride The Lightning...
2026-10-13T13:49:34+00:00  adding callback 8
2026-10-13T13:49:34+00:00  Launching primary...
2026-10-13T13:49:35+00:00  [10/13/2026,
 1:49:35 PM] INFO: RTL => Server is up and running, please open the 
UI at http://0.0.0.0:80 or your proxy configured url.
2026-10-13T13:49:54+00:00  Starting Ride The Lightning...
2026-10-13T13:49:54+00:00  adding callback 9
2026-10-13T13:49:54+00:00  Launching primary...
2026-10-13T13:49:55+00:00  [10/13/2026,
 1:49:55 PM] INFO: RTL => Server is up and running, please open the 
UI at http://0.0.0.0:80 or your proxy configured url.
2026-10-14T21:10:52+00:00  container-runtime.service: Deactivated successfully.
2026-10-14T21:10:52+00:00  container-runtime.service: Consumed 5min 35.588s CPU time, 255.3M memory peak, 120.1M memory swap peak.
2026-10-14T21:10:56+00:00  Started container-runtime.service - StartOS Container Runtime.
2026-10-14T21:10:57+00:00  Listening on /media/startos/rpc/service.sock
2026-10-14T21:10:59+00:00  Initializing...
2026-10-14T21:11:00+00:00  Initialization complete.
2026-10-14T21:11:00+00:00  Starting Ride The Lightning...
2026-10-14T21:11:00+00:00  adding callback 1
2026-10-14T21:11:00+00:00  Launching primary...
2026-10-14T21:11:03+00:00  [10/14/2026,
 9:11:03 PM] INFO: RTL => Server is up and running, please open the 
UI at http://0.0.0.0:80 or your proxy configured url

I do still need to get the latest update as well i have not done the latest RTL update yet. Seemed to coincide with the update as well. (Maybe)

The purple screen with the dot moving in the tab is your browser still waiting for RTL to send the page. Nothing has arrived at all, on any of the addresses you tried. The RTL logs show it starting normally after the restart on the 14th and no errors since. RTL only logs errors, so the logs can’t show what’s holding it up. StartOS shows RTL as healthy because its check only tests whether RTL’s port accepts a connection, which can happen even when RTL isn’t answering.

Both RTL and LND have newer versions out than the ones you’re running (RTL 0.15.13:1, LND 0.21.4). Updating either one is safe for your channels, and the update restarts the service. Install both and try RTL again.

If it still doesn’t load, we need to see whether RTL answers from inside your server. Connect to your server over SSH and run this command. It asks RTL for its page from inside RTL’s own container and gives up after 10 seconds. Paste what it prints here.

sudo start-cli package attach ride-the-lightning -n rtl-sub -- wget -S -O /dev/null -T 10 http://127.0.0.1/rtl/

The Google Drive backup error is a separate problem, and it’s most likely on Google’s side. When you made the app in Google Cloud Console for LND’s backups, it started out in Testing. While an app is in Testing, Google cancels its access to your Drive 7 days after you approve it, so a week after setup every upload starts failing. To check, open your project in Google Cloud Console and go to Google Auth Platform → Audience. If the publishing status says Testing, that’s the cause. To fix it:

  1. On that same Audience page, click Publish app and confirm. You don’t need Google to review it for your own use.
  2. In StartOS, open LND, run Configure Continuous Backups again and do the Google Drive sign-in once more to get a new Authorization Code. Your Client ID and Secret are already saved. Google will show a warning that the app isn’t verified. Click Advanced, then Go to followed by your app’s name.

After that, the access no longer expires after a week.