Streamline Nextcloud Installation on CasaOS with BigBearCasaOS

[Bertie_Tozer]

Yeah I am going to have to find a better way to set up a home server
this is not going to work on the pi5 for me
now I have to work out how to uninstall casaos
pi5 is annoying
ok uninstall was very easy
thank you for all your help

[josefek]

Appreciate this! Can you explain how to utilize a CIFS mount for the user data dir? I mapped the container /var/www/html/data path to the mount in NextCloud settings in CasaOS to no avail.

[dragonfire1119]

I’ll try to explain it:

1. Manually mount the CIFS share:

sudo mount -t cifs -o username=your_user,password=your_pass //server_ip/share_name /mnt/nextcloud_data

2. Add it to /etc/fstab for persistence:

//server_ip/share_name /mnt/nextcloud_data cifs username=your_user,password=your_pass,uid=33,gid=33,iocharset=utf8 0 0

Tip: You can store your credentials in a separate file (e.g., /root/.cifs_credentials) for better security. Format:

username=your_user
password=your_pass

Then modify /etc/fstab:

//server_ip/share_name /mnt/nextcloud_data cifs credentials=/root/.cifs_credentials,uid=33,gid=33,iocharset=utf8 0 0

3. Update Docker Compose or Docker run to map the CIFS share:

volumes:
  - /mnt/nextcloud_data:/var/www/html/data

4. Set permissions so Nextcloud can access it:

sudo chmod -R 755 /mnt/nextcloud_data

Fixing Nextcloud Permissions in a Docker Container

Nextcloud is a powerful open-source platform for file synchronization and sharing, but it can run into issues if the file permissions are not set correctly. One common issue is the “Can’t write into config directory!” error, which typically indicates a permissions problem. This blog post will guide you through the steps to fix Nextcloud permissions within a Docker container. Steps to Fix Nextcloud Permissions Step 1: Identify the Running Container First, you need to identify the container runni…

5. Restart the container and verify in Nextcloud.

Always backup any data that’s important.

[totallynewtothis]

Love this video, finally I’m almost up and running with a domain, Cloudflared tunnels and nextcloud. But I can’t seem to get https (although there is with Cloudflare) nextcloud can’t see it so won’t respond when I try services that need the (s) like password manager that required https.

can anyone help me force https or just trust the domain its pointing to?

p.s. I have Cloudflare set to strict in the ssl settings

Thanks

[Clem_oOo]

Hi !

I succeed to overpass the “trusted domains” issue.
You can add the “TRUSTED_DOMAINS” key and the “local host” value in the container setting (as in the following picture)

My actual configuration is a Rpi 5 8Gb, with Raspberry OS (Debian 12) and CasaOS 0.4.15.

[cybersistema]

I was running into a “too many open files” error.

I fixed it by adding this to the container on install:

If other ppl are seeing this, you may want to add a ulimits setting to the default configuration. If not, it took me a while to figure this out, so hopefully this saves somebody else time.