Hi again, @vix! 
And if I see something that doesn’t work, I think it’s a good idea sharing it.
Absolutely, thanks for testing our nightlies!
Do you need some more details from my side?
We don’t set up encryption for Portainer as far as I know, so maybe the portainer_data volume has some stray certificate from previous runs.
Could you run the following commands to remove the volume and then restart the board? Make sure you’re running the latest docker-compose.yml that comes with build 307.
torizon@verdin-imx8mp-06817296:~$ docker ps -a
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
06418498f426 torizon/chromium:3 "/usr/bin/start-brow…" 3 minutes ago Exited (0) About a minute ago torizon-kiosk-1
ebd2f6dacafa torizon/weston-vivante:3 "/usr/bin/entry.sh" 3 minutes ago Exited (143) About a minute ago torizon-weston-1
251297897b8b portainer/portainer-ce:2.17.1 "/portainer --templa…" 3 minutes ago Exited (2) About a minute ago torizon-portainer-1
torizon@verdin-imx8mp-06817296:~$ docker rm -f 251297897b8b
251297897b8b
torizon@verdin-imx8mp-06817296:~$ docker volume rm -f torizon_portainer_data
torizon_portainer_data
Thanks!