# Just Screenly-Logo and no Web-GUI

**URL:** <https://forums.screenly.io/t/just-screenly-logo-and-no-web-gui/1488>\
**Category:** Anthias\
**Created:** [July 19, 2024, 1:16am UTC](https://forums.screenly.io/t/just-screenly-logo-and-no-web-gui/1488 "2024-07-19T01:16:44Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![matsmats](https://avatars.discourse-cdn.com/v4/letter/m/d26b3c/32.png) [@matsmats](https://forums.screenly.io/u/matsmats)\
**Post date:** [July 19, 2024, 1:16am UTC](https://forums.screenly.io/t/just-screenly-logo-and-no-web-gui/1488/1 "2024-07-19T01:16:44Z")

</div>

Hey guys,

I set up Anthias on a Raspberry Pi 4 Model B Rev 1.5 around 1,5 month ago.

It plays 15 pictures in a loop and I´m pretty happy with it.

Unfortunately it stopped working from the sudden and only displays the Screenly-Logo.  
The Web-GUI pretents to load, but doesn´t appear.

SSH access is possible.

I already powercyled the Pi and tried several reboots without success.

May you please help me out how I can start troubleshooting? I’m at a bit of a loss right now. Unfortunately, the display is about 300km away.

I hope I can fix it remotely without driving over to replace the hardware.

Thank you in advance  
Mats

systemd-analyze blame:

> > $ systemd-analyze blame  
> > 2min 431ms wg-quick@wg0.service  
> > 27.576s cloudflared.service  
> > 24.011s docker.service  
> > 8.318s NetworkManager-wait-online.service  
> > 6.499s e2scrub\_reap.service  
> > 5.290s containerd.service  
> > 3.499s apt-daily.service  
> > 2.025s dev-mmcblk0p2.device  
> > 1.717s ModemManager.service  
> > 1.317s plymouth-start.service  
> > 1.289s systemd-binfmt.service  
> > 1.057s rpi-eeprom-update.service  
> > 1.017s networking.service  
> > 926ms ssh.service  
> > 892ms systemd-timesyncd.service  
> > 886ms NetworkManager.service  
> > 821ms systemd-journal-flush.service  
> > 673ms systemd-udev-trigger.service  
> > 601ms avahi-daemon.service  
> > 592ms bluetooth.service  
> > 575ms proc-sys-fs-binfmt\_misc.mount  
> > 570ms polkit.service  
> > 551ms plymouth-read-write.service  
> > 534ms dbus.service  
> > 520ms keyboard-setup.service  
> > 512ms console-setup.service  
> > 501ms systemd-logind.service  
> > 491ms systemd-tmpfiles-setup.service  
> > 488ms systemd-fsck@dev-disk-by\x2dpartuuid-4a07fd05\x2d01.service  
> > 464ms wpa\_supplicant.service  
> > 453ms run-rpc\_pipefs.mount  
> > 398ms systemd-journald.service  
> > 383ms raspi-config.service  
> > 355ms sshswitch.service  
> > 293ms rc-local.service  
> > 267ms user@1000.service  
> > 226ms systemd-rfkill.service  
> > 190ms logrotate.service  
> > 187ms dev-mqueue.mount  
> > 182ms systemd-remount-fs.service  
> > 182ms sys-kernel-debug.mount  
> > 176ms sys-kernel-tracing.mount  
> > 175ms systemd-random-seed.service  
> > 168ms fake-hwclock.service  
> > 168ms systemd-sysctl.service  
> > 166ms systemd-sysusers.service  
> > 156ms kmod-static-nodes.service  
> > 152ms modprobe@configfs.service  
> > 143ms alsa-restore.service  
> > 142ms modprobe@drm.service

---

<div class="post-metadata">

**Author:** ![nicomiguelino](https://avatars.discourse-cdn.com/v4/letter/n/e56c9b/32.png) [@nicomiguelino](https://forums.screenly.io/u/nicomiguelino)\
**Post date:** [July 19, 2024, 3:27pm UTC](https://forums.screenly.io/t/just-screenly-logo-and-no-web-gui/1488/2 "2024-07-19T15:27:17Z")

</div>

@matsmats, would you be able to provide the server and the viewer logs? Detailed steps on how to do them can be seen [here](https://github.com/Screenly/Anthias/tree/master/docs#how-to-get-logs-from-anthias). I would recommend you to run the following:

```bash
cd ~/screenly
docker compose logs -ft anthias-server # on one terminal session/tab/window
docker compose logs -ft anthias-viewer # on another terminal session/tab/window

```

If you have a spare hardware nearby and can’t wait, you can do the following:

- Backup your Anthias data (limited to assets, asset metadata, and settings).
  - As a limitation, you won’t be able to backup your system settings like network settings (if there are any).
  - SSH to your device and do a software upgrade by running the following:

```bash
cd screenly/
./bin/run_upgrade.sh

```

- Alternatively, you can also run the install script to update Anthias: `bash <(curl -sL https://install-anthias.srly.io)`

I hope this helps.

---

<div class="post-metadata">

**Author:** ![matsmats](https://avatars.discourse-cdn.com/v4/letter/m/d26b3c/32.png) [@matsmats](https://forums.screenly.io/u/matsmats)\
**Post date:** [July 20, 2024, 8:32am UTC](https://forums.screenly.io/t/just-screenly-logo-and-no-web-gui/1488/3 "2024-07-20T08:32:38Z")

</div>

Hey mate,  
thank you for your quick reply.  
I used your commands and didn´t find anything conspicous in the logs.  
But while digging deeper I noticed that my SSH-connection was very slow and patchy.  
What should I say - in summary it was just a throttled mobile data connection that was to slow to show the web GUI and in coinsidence the assets we´re just expired.

Anyways. Thank you for your help and have a nice weekend 🙂