alpine-mariadb VS docker-mariadb

I currently use the linuxserver nextcloud image with the mariadb image from yobasystems because it's more lightweight than others I've found. Happy to share my docker-compose.yml file if useful. I have been intending to migrate to the official nextcloud image but haven't found a good time to do it yet. I trust linuxserver images enough, they have a good reputation, but I like to be as close to upstream as possible. Mariadb is one example where the arm architecture isn't officially supported. I chose a third-party image rather than built my own because nextcloud was one of the first things I migrated over to docker before I learnt how to build images. Goes to show learning docker does take time :)

Try https://github.com/yobasystems/alpine-mariadb

Hi together, I want to give nextcloud a try with my raspberry pi 3. Since there is at least one more little service on the pi I've decided to go for a docker instance to separate them. I did all the steps in the guide (went for the fmp/mariadb instance), port forwarded the ports 80 and 443 in my router and inserted the name of my dyndns into the VIRTUAL_HOST and LETSENCRYPT_HOST. I also had to switch out the official mariadb to rpi-mariadb. How ever, when I open the pi locally (http://local.address) or insert http://my.dyndns (=port 80) I get a standard nginx welcome screen and "connection not successful" on https:// (=port 443). What am I missing? Do I need an account or something else for letsencrypt? In docker ps I can see that the nextcloud_redis_1 container restarts about every minute.