Installation troubleshooting

Diagnose first-boot failures, Wi-Fi issues, a blank display, bad system clock, incomplete downloads and missing Admin access.

This page covers problems during initial installation. See Troubleshooting for an already installed player.

The Pi does not boot #

Check that the card was written with the 64-bit Raspberry Pi DietPi image, the power supply is adequate and display cables are seated. Headless systems can be running even with no visible picture: check the router.

Wi-Fi never connects #

Verify that the Wi-Fi template is saved as dietpi.txt, that dietpi-wifi.txt contains your SSID and password, and that the Wi-Fi country code is correct. On Windows check that the filename does not end in .txt.txt. Ethernet with the Ethernet template is a useful alternative.

The installer seems stuck #

Allow time for the DietPi first-run packages and several reboots. If you can log in by SSH with the system password from the template, inspect:

tail -n 80 /var/lib/mupibox-ng/install.log tail -n 80 /var/lib/dietpi/logs/dietpi-firstrun-setup.log systemctl --failed

The MuPiBox installer log survives a reboot. If missing, DietPi's own first-run may not have completed.

Certificate/download errors #

Raspberry Pis usually have no RTC and may start with an incorrect clock. Check Internet, DNS and date:

date -Is timedatectl status curl -I https://releases.mupibox.de/installer/install.sh

Do not disable TLS certificate or release signature checking.

Admin unavailable or display black #

Try http://<IP>:8090/admin/ from the same LAN; guest network isolation may block access. If Admin works while the display stays black, inspect Display & touch. For SSH diagnosis:

systemctl status mupibox-ng --no-pager journalctl -u mupibox-ng -b --no-pager -n 100 df -h /

DietPi 10.7+ is required for full Wi-Fi management. When reporting a problem via GitHub, provide Pi/display models, selected template, DietPi version and error messages without passwords or tokens.