Hey Alomon,
i also want to install nextcloud as easy as its possible I have tried it over the linuxserver.io repo but this will not work for me ... I hope may be you can help me. At the end i want mainly use KODI to watch tv and in the background i would like to run nextcloud. I have an raspbery 3b+ - and if that is not enough i will get a raspberry pi4 with 8gb.
Can you maybe give me some informations and what is the easiest or best way to install nextcloud on KODI (LibreELEC)????
Display MoreHi,
Now I think I've got it installed, I used CLI to be able to monitor everything:
Codedocker create \ --name=nextcloud \ --net=lsio \ -e PUID=65534 \ -e PGID=100 \ -e TZ=Europe/London \ -v /storage/.kodi/userdata/addon_data/docker.linuxserver.nextcloud/config:/config \ -v /storage/.kodi/userdata/docker.linuxserver.nextcloud/data:/data \ --restart unless-stopped \ linuxserver/nextcloud
Code Display Moredocker create \ --name=mariadb \ --net=lsio \ -e PUID=65534 \ -e PGID=100 \ -e MYSQL_ROOT_PASSWORD= _SQL_PASS_\ -e TZ=Europe/London \ -e MYSQL_DATABASE=nc \ -e MYSQL_USER= _SQL_USER_ \ -e MYSQL_PASSWORD=_SQL_USER_PASS_ \ -p 3306:3306 \ -v /storage/.kodi/userdata/addon_data/docker.linuxserver.mariadb/config:/config \ --restart unless-stopped \ linuxserver/mariadb
Code Display Moredocker create \ --name=letsencrypt \ --cap-add=NET_ADMIN \ --net=lsio \ -e PUID=65534 \ -e PGID=100 \ -e TZ=Europe/London \ -e URL=_MY_DOMAIN_.duckdns.org \ -e SUBDOMAINS=nextcloud \ -e VALIDATION=duckdns \ -e DUCKDNSTOKEN=_MY_TOKEN_ \ -e EMAIL=_MY_MAIL_ \ -e DHLEVEL=2048 \ -e STAGING=false \ -p 443:443 \ -v /storage/.kodi/userdata/addon_data/docker.linuxserver.letsencrypt/config:/config \ --restart unless-stopped \ linuxserver/letsencrypt
Then:
I used a custom dhparams to speed things up as explained here. I also had to edit nextcloud.subdomain.conf file with proxy_max_temp_file_size 1024m; as explained there. Then docker restart letsencrypt.
I can now access to my Nextcloud instance via https://nextcloud._MY_DOMAIN_.duckdns.org. Howerver, my browsers still trigger a safety alert regarding the certificate because the certificate is for _MY_DOMAIN_.duckdns.org and not for nextcloud._MY_DOMAIN_.duckdns.org.
I tried as well to install letsencrypt with wildcard as SUBDOMAINS but got the same error because the certificate was for *._MY_DOMAIN_.duckdns.org.
This seems to provide other applications to access Nextcloud (in my case, Home Assistant).
Is there a solution fot that?
Thanks again