Caddy won't start if you delete "admin" user

[yward]

Caddy will fail to start if you delete the admin user and use a different username, as it looks for for the following path:
2024-07-22T05:38:24.235196013Z Waiting for allowed-countries.txt file to be created
2024-07-22T05:38:24.235229751Z + '[' -f /nextcloud/admin/files/nextcloud-aio-caddy/allowed-countries.txt ']'
2024-07-22T05:38:24.235926414Z + echo 'Waiting for allowed-countries.txt file to be created'
2024-07-22T05:38:24.235944248Z + sleep 5

[speakradmin]

Same here. Wanted to try stalwart but it waits for a cert and that depends on caddy. Added caddy to my env variable and it won't start because I don't have an admin user in my Nextcloud setup any more.

@szaimen could the container be modified to have an option start up without the geoblocking feature as the "allowed-countries.txt" file is only needed for that

[speakradmin]

A workaround for those that stumble across this:

sudo mkdir /mnt/ncdata/admin
sudo mkdir /mnt/ncdata/admin/files
sudo mkdir /mnt/ncdata/admin/files/nextcloud-aio-caddy
sudo touch /mnt/ncdata/admin/files/nextcloud-aio-caddy/allowed-countries.txt
sudo chown www-data:www-data /mnt/ncdata/admin/files/nextcloud-aio-caddy/allowed-countries.txt

After that you can add whatever country code you need as per the docs here https://github.com/nextcloud/all-in-one/tree/main/community-containers/caddy

[tj775]

The geoblocking file should not be stored in the user-directory of the default admin user. It should be best practise to replace nextcloud default admin user. That happens in a non functional nextcloud-aio setup.