@Martin_Webster
Glad the network issue got resolved for you.
As for launching Chromium automatically, I use a slightly different method since none of my Raspberry Pis have a full desktop environment - they are very minimal builds. I am using Arch Linux Arm though, not Raspbian…
I just install Xorg and the matchbox window manager package (matchbox-window-manager package on Arch Linux Arm, not sure on Raspbian). I then have a systemctl service file that runs a script. This works for Xorg, but since the matchbox-window-manager is not compatible with Wayland, I will have to look for a new approach then.
systemd service file:
[Unit]
Description = Starts Xorg as defined in /home/USERNAME/bin/gui.sh
After = systemd-user-sessions.service network.target
Conflicts=getty@tty7.service[Service] User = USERNAME Group = USERNAME PAMName=login Type = simple TTYPath=/dev/tty7 ExecStart = /usr/bin/xinit /usr/bin/dbus-launch --exit-with-session /home/USERNAME/bin/gui.sh -- :0 -nolisten tcp vt7 Restart = always StandardInput = tty
[Install] WantedBy = multi-user.target
gui.sh script:
#!/bin/bash export DISPLAY=":0" xset dpms 60 60 60 & matchbox-window-manager -use_titlebar no -use_cursor no & /usr/bin/chromium --kiosk <URL TO EXTENSION>