all I did was to only define a port mapping for port 80 (not 443) in the add-on configuration and then pointed the proxy host of nginxproxymanager to the IP of my HA device and port I have configured in the add-on settings. Done. I ofc enabled and forced SSL in Nginx. That’s all I did.
edit: I also use the add-on from haberda, which jaaem just linked above
This is exactly what i’m trying. I’ve created a new duckdns subdomain which links in the nginx proxy manage to the nextcloud http port. But when I open the domain in the browser I get an unsecure connection warning.
//EDIT: Get certificate error. So when connecting to nextcoud the browser gets the certificate of home assistant.
sorry, no idea then - works for me.
thank you anyways. It must be a problem with the nextcloud installation. I even cant get http access in my local network only unsecure https network. maybe i try a fresh installation of the addon including a new database.
//EDIT: I found the issue. I used duckdns before and in the configiration file ha was forced to use ther certs of duckdns addon. After deleting the entries it works. But I mapped nextclouds https protocol and port. Now it works fine!
@DendelX did you ever figure out how to do this? I was able to get the Nextcloud addon working, but not able to mount an SMB reliably. I tried using the External Drives APP - but for whatever reason, it would only sync half the files.
Maybe something like this might work to allow the SMB to appear local in HASSIO?
https://community.home-assistant.io/t/mount-remote-smb-share-on-hassio/116734/122
I need to change the max. upload file size (client_max_body_size) , any idea how to change that?
Hi,
I implemented that in my own nextcloud addon here (set to 10gb), with several other options: GitHub - alexbelgium/hassio-addons: My homeassistant addons
Otherwise, here is the relevant code if you use linuxserver’s image (base for haberda and myself).
sed -i \
-e 's/upload_max_filesize=1024M/upload_max_filesize=10240M/g' \
-e 's/post_max_size=1024M/post_max_size=10240M/g' \
/etc/php7/php.ini
sed -i "s|client_max_body_size 512M;|client_max_body_size 10240M;|g" /defaults/default
If you are running those commands from inside a running container, the second change should be made in /config/nginx/site-confs/default. You then need to run nginx -s reload for it to take the new config in account
Hi all has anyone tried using the mariadb addon for one of the nextcloud addons and got it to work? if not what db are you using?
yes, use nextcloud from this repo: GitHub - haberda/hassio_addons: hopefully useful hassio addons
works fine with mariadb addon.
thanks, what config settings did you put into your mariadb addon?
This is my config
databases:
- nextcloud
- homeassistant
logins:
- username: nextcloud
password: xxxxxxx
- username: homeassistant
password: xxxxxxx
rights:
- username: nextcloud
database: nextcloud
- username: homeassistant
database: homeassistant
Thanks! thats what I had, but nextcloud wasn’t able to connect. Will keep digging. Cheers
Had this issue, too. It doesnt work with localhost or 127.0.0.1. I had to connect to the actual network ip.
Yep all working now. 
I get this Message: Composer autoloader not found, unable to continue. Check the folder “3rdparty”. Running “git submodule update --init” will initialize the git submodule that handles the subfolder “3rdparty”.
Is there a step that I’m missing?
Installed this on my supervised HA running on a Pi4 4GB and it runs out of memory.
Fatal Error Insufficient shared memory!
Any settings I can adjust? TIA.
I’m stuck with nextcloud is not installed
Nextcloud is not installed - only a limited number of commands are available
There are no commands defined in the "config:system" namespace.
cont-init: info: /etc/cont-init.d/99-trusted_domains.sh exited 1
s6-rc: info: service legacy-cont-init successfully started
s6-rc: info: service init-mods: starting
s6-rc: info: service init-mods successfully started
s6-rc: info: service init-mods-package-install: starting
s6-rc: info: service init-mods-package-install successfully started
s6-rc: info: service init-mods-end: starting
s6-rc: info: service init-mods-end successfully started
s6-rc: info: service init-services: starting
s6-rc: info: service init-services successfully started
s6-rc: info: service legacy-services: starting
services-up: info: copying legacy longrun cron (no readiness notification)
services-up: info: copying legacy longrun nginx (no readiness notification)
services-up: info: copying legacy longrun php-fpm (no readiness notification)
s6-rc: info: service legacy-services successfully started
s6-rc: info: service 99-ci-service-check: starting
[ls.io-init] done.
s6-rc: info: service 99-ci-service-check successfully started
Exception: Not installed in /data/config/www/nextcloud/lib/base.php:284
Stack trace:
#0 /data/config/www/nextcloud/lib/base.php(680): OC::checkInstalled()
#1 /data/config/www/nextcloud/lib/base.php(1144): OC::init()
#2 /data/config/www/nextcloud/cron.php(43): require_once('...')
#3 {main}
Exception: Not installed in /data/config/www/nextcloud/lib/base.php:284
Stack trace:
#0 /data/config/www/nextcloud/lib/base.php(680): OC::checkInstalled()
#1 /data/config/www/nextcloud/lib/base.php(1144): OC::init()
#2 /data/config/www/nextclo
Hi,
I have successfully installed the add-on https://github.com/haberda/hassio_addons and it works perfectly. Unfortunately, I have not yet managed with SSL. I use the same duckdns domain as Homeassistant with a different port. This also worked perfectly with the Bitwarden addon https://github.com/hassio-addons/addon-bitwarden. Unfortunately, an invalid certificate from linuxserver.io is always used. In Ikognito mode I can bypass the warning of my browser and then everything works without SSL. I think it is somehow because Nextcloud has installed an invalid certificate. How can I switch off this certificate?
Thanks a lot for your help!
I have found the solution!
Go to NGINX Proxy Manager and download the SSL certificate for your domain. Go to your Homeassistant SSL certificates via SambaNas. You will find a folder called Nextcloud. Now delete both files from the Nextcloud folder. Now copy the fullchain.perm from the download zip and paste it there. Name it cert.crt. Copy privkey.pem and name it cert.key. Restart Nextcloud. In my case, the certificate is no longer from Linuxserver but from Letsencrypt and that’s how it should be! I hope I have been able to help someone with this.