Gateway timeout- how to fix it?

Ostravskiiii · August 14, 2024, 6:17pm

Hi, I must have messed something up while learning with Start9OS.

Start9 server runs on Xpenology (Synology) virtual PC.

CPU AMD Athlon 5370, 16GB RAM, 2x SATA disk Btrfs(SHR RAID-backups Start9OS), nvme SSD 2TB,(for Start9OS).

Yesterday, in addition to my native services (bitcoin core + Lighting core + Ride to Lighting GUI, everything worked relatively well so far), I also installed LND and BTCpay server.

Both LND and BTCpay synced for over 10 hours without success.

I did a “System Rebuild” and waited until this morning.

Since then, I have not had access to the system.

I can get to the server’s IP addresses via localhost (ping from the local site is fine within 5ms), but when I enter the password, I get a “Gateway Timeout” error.

I can get into the system via SSH, but I can’t do much there either, just the basics, I don’t know exactly the specifications and commands… (I’m learning).

Below are the screenshots. Finally, I tried to restart Virtual PC, but to no avail.

I didn’t dare to restore Snapshots because of Lighting. (I have open channels and onchain) Please help, how to get out of this, how to restore backups via SSH?

I have backups here: “/volume1/Start9_os_backup”

I don’t have good knowledge of CLI but I’m learning.

Thanks to

#1
Last login: Wed Aug 14 12:54:45 2024 from 192.168.19.13
start9@warmer-snowman:~$ sudo systemctl status
Failed to read server status: Failed to activate service ‘org.freedesktop.systemd1’: timed out (service_start_timeout=2>
lines 1-1/1 (END)

#2
start9@warmer-snowman:~$ ps aux | grep lightningd
start9 40745 0.0 0.0 6856 2008 pts/1 S+ 14:44 0:00 grep lightningd
start9@warmer-snowman:~$ free -h
top
total used free shared buff/cache available
Mem: 11Gi 686Mi 2.6Gi 12Mi 8.7Gi 11Gi
Swap: 2.9Gi 147Mi 2.8Gi
top - 14:51:33 up 5 days, 15:49, 3 users, load average: 0.06, 0.03, 0.00
Tasks: 171 total, 1 running, 170 sleeping, 0 stopped, 0 zombie
%Cpu(s): 0.0 us, 0.2 sy, 0.0 ni, 99.8 id, 0.0 wa, 0.0 hi, 0.0 si, 0.0 st
MiB Mem : 11955.3 total, 2645.5 free, 689.1 used, 8946.5 buff/cache
MiB Swap: 2988.0 total, 2840.7 free, 147.3 used. 11266.2 avail Mem

PID USER      PR  NI    VIRT    RES    SHR S  %CPU  %MEM     TIME+ COMMAND

6391 avahi 20 0 7576 3900 3008 S 0.3 0.0 26:49.98 avahi-daemon
40757 start9 20 0 12036 4920 3016 R 0.3 0.0 0:02.35 top
40765 root 20 0 0 0 0 I 0.3 0.0 0:00.08 kworker/0:0-events_freezable_power_
1 root 20 0 168516 5716 4976 S 0.0 0.0 127:50.34 systemd
2 root 20 0 0 0 0 S 0.0 0.0 0:00.81 kthreadd
3 root 0 -20 0 0 0 I 0.0 0.0 0:00.00 rcu_gp
4 root 0 -20 0 0 0 I 0.0 0.0 0:00.00 rcu_par_gp
5 root 0 -20 0 0 0 I 0.0 0.0 0:00.00 slub_flushwq
6 root 0 -20 0 0 0 I 0.0 0.0 0:00.00 netns
10 root 0 -20 0 0 0 I 0.0 0.0 0:00.00 mm_percpu_wq
11 root 20 0 0 0 0 I 0.0 0.0 0:00.00 rcu_tasks_kthread
12 root 20 0 0 0 0 I 0.0 0.0 0:00.00 rcu_tasks_rude_kthread
13 root 20 0 0 0 0 I 0.0 0.0 0:00.00 rcu_tasks_trace_kthread
14 root 20 0 0 0 0 S 0.0 0.0 7:46.99 ksoftirqd/0
15 root 20 0 0 0 0 I 0.0 0.0 29:31.69 rcu_preempt
16 root rt 0 0 0 0 S 0.0 0.0 0:26.65 migration/0
18 root 20 0 0 0 0 S 0.0 0.0 0:00.00 cpuhp/0
19 root 20 0 0 0 0 S 0.0 0.0 0:00.00 cpuhp/1
20 root rt 0 0 0 0 S 0.0 0.0 0:26.80 migration/1
21 root 20 0 0 0 0 S 0.0 0.0 6:50.72 ksoftirqd/1
23 root 0 -20 0 0 0 I 0.0 0.0 0:00.00 kworker/1:0H-events_highpri
24 root 20 0 0 0 0 S 0.0 0.0 0:00.01 cpuhp/2
25 root rt 0 0 0 0 S 0.0 0.0 0:26.96 migration/2
start9@warmer-snowman:~$ df -h
Filesystem Size Used Avail Use% Mounted on
udev 5.9G 0 5.9G 0% /dev
tmpfs 1.2G 1012K 1.2G 1% /run
overlay 5.9G 89M 5.8G 2% /
/dev/sda3 15G 3.9G 11G 27% /media/embassy/next
tmpfs 5.9G 84K 5.9G 1% /dev/shm
tmpfs 5.0M 0 5.0M 0% /run/lock
/dev/sda2 1022M 160M 863M 16% /boot
tmpfs 1.2G 0 1.2G 0% /run/user/1001
/dev/mapper/EMBASSY_N7R6XBOVZASJQKDJKNMMCJA6WHO47HCANT3KQEC3EM5MLNF6QODQ_package-data 1.7T 771G 945G 45% /embassy-data/package-data
/dev/mapper/EMBASSY_N7R6XBOVZASJQKDJKNMMCJA6WHO47HCANT3KQEC3EM5MLNF6QODQ_main 8.0G 1.2G 6.4G 16% /var/log/journal
start9@warmer-snowman:~$ sudo journalctl -b -1
Data from the specified boot (-1) is not available: No such boot ID in journal
start9@warmer-snowman:~$ ps -p 1
PID TTY TIME CMD
1 ? 02:07:50 systemd
start9@warmer-snowman:~$ sudo reboot

Broadcast message from root@start on pts/2 (Wed 2024-08-14 14:53:12 UTC):

The system will reboot now!

Call to Reboot failed: Connection timed out

#3
start9@warmer-snowman:~$ sudo podman ps --all
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES

#4 ???

Thanks in advance for your help

Alvaro · August 14, 2024, 9:18pm

“Gateway Timeout Error” is a generic message from your browser that just means “unable to connect to the server”.

It’s almost always a browser caching issue and tends to happen when people leave their browsers tabs open for a long time, especially if the computer goes to sleep or hibernates.

The usual solution to this is to hard refresh the browser:

Linux/Windows: ctrl+shift+R
macOS : cmd+shift+R

If this does not help, you can also check out the “request error” common issue for other steps to take. Start9 | Common Issues

Ostravskiiii · August 15, 2024, 7:58am

Thank you, I’ve done all this before, it didn’t help. I tried to connect from different clients (PC1-PC3, android, Linux,Win,) of different browsers, I performed a hard refresh of the browser, it connected from an onion address and from a normal local IP address. I’m afraid there’s a bigger problem here. Unfortunately, I don’t know how to solve this problem without losing data on Lighting. Any other solution? Thanks to

StuPleb · August 15, 2024, 1:01pm

Some interface is running somewhere. Either your unique adjective-noun.local or start.local in diagnostic mode. And even if those are uncontactable, by IPa.ddr.ess

If nothing is running and so you can’t reboot then you may need to hard reboot.

Ostravskiiii · August 15, 2024, 6:10pm

Thank you, a hard restart was really enough.

I naively thought that it was enough to restart only virtual PC(host), I tried several times without success and looked for the error deep in the system.

Finally, on your advice, I rebooted the host and the problem was fixed immediately.

Thanks for the great tip, I probably wouldn’t have thought of this myself.
I have to admit that the Start9 support works really well, it responds quickly to every problem I’ve had so far and guides me perfectly to the goal.

And I still have a lot to learn, I will still have to examine, debug and check my host hardware and find weak points where possible problems may arise.

Thank you successfully solved, server Start9 os fully functional again.