Added Nextcloud to BigBearCasaOS

Hi
I followed the instructions for zima, i saved it and restarted but got a server error message same as before the edit. I downloaded dozzle and this is the main log and the control pane for the container

Can you see whats wrong? Its a tad confusing for me! I‘ll post the other is below.

I see the network has changed; it should be big_bear_nextcloud_network. Did you change it?

Ah! Is that what it is? Hmm, no i got a red error from zimaos but it wasnt up long enough to read properly… now i got it, it says its improperly labelled in docker compose.

Is this instruction supposed to work with the Bigbear Nextcloud SMB version as well? I installed the Nextcloud SMB version under Casaos, and then I get an “access through untrusted domain” error. So I showed up on this page here. Then, I try the bash command listed in “Instructions” above in my terminal, both with sudo as a regular user and then logging into root as well. It seems to be missing directories or files. I can only presume that this script was made and tested and made to work on a system that either had more files or permissions. Do I need to execute this from a different directory at my terminal?

root@casaos:/# bash -c “$(wget -qLO - https://raw.githubusercontent.com/bigbeartechworld/big-bear-scripts/master/casaos-add-lan-ip-to-nextcloud-config/run.sh)”
cp: cannot stat ‘/DATA/AppData/big-bear-nextcloud/html/config/config.php’: No such file or directory
bash: line 10: /DATA/AppData/big-bear-nextcloud/html/config/config.php: No such file or directory
Error: open /var/lib/casaos/apps/big-bear-nextcloud/docker-compose.yml: no such file or directory
Usage:
casaos-cli app-management apply [flags]

Flags:
-d, --dry-run dry run
-f, --file string path to a compose file
-h, --help help for apply

Global Flags:
-u, --root-url string root url of CasaOS API

@andyhoy Hello, yes, the SMB version was migrated to the big-bear nextcloud, so they’re both using the same image. Please follow this tutorial:

Hi.
I’m not familiar with dockers and all that linux stuff.
My setup is rpi5 with CasaOS on SDcard with 52Pi quad nvme shield. I want to run only OS from SD card and all data keep on ssd’s.
I changed all hosts adresses from appdata folder to /mnt/storage/docker/… and now when trying to enter nextcloud interface i have error:
“Configuration was not read or initialized correctly, not overwriting /var/www/html/config/config.php”

Can smbd help me?

I found solution for that - just changed privileges to mentioned folders

Hola buenas, quien me podria ayudar con estos errores?

Hi @dragonfire1119, thanks for your job. When I try to change/var/www/html mapping from /DATA/AppData/big-bear-nextcloud/html to /mnt/Data/nextcloud_html on the nextcloud container

Error while trying to initialise the database: An exception occurred while executing a query: SQLSTATE[42501]: Insufficient privilege: 7 ERROR: permission denied for table oc_migrations 

image

Any idea to solve this issue?

Hello @MathGon, I would follow my other tutorial here:

Instead of changing the host path you can also mount a new drive to /DATA/AppData.

Hi guys, hope you can help me, is this my first post
Nice to meet you all
I have my casa os on debian 12, casa os version 0.4.15 with next cloud last version and cloudflared tunnel up and running
My issue is i have adgauardhome working with tunnel without any issue but i got the error on nextcloud about trusted domain : Please contact your administrator. If you are an administrator, edit the “trusted_domains” setting in config/config.php like the example in config.sample.php.

My config file have the following information
‘trusted_domains’ =>
array (
0 => ‘localhost’,
1 => ‘my casaos internal IP’,
2 => ‘the domain of the tunnel the complete URL like nextcloud.mydomain.com
),

and don’t wotk i try to stop and start the nextcloud container same issue, what i’m doing wrong??
Can you please helpme?
Br

So I’m having issues connecting to Nextcloud via Windows 10 because when I connect it to the proxy host, it says that "The Polling URL does not start with HTTPS despite the login URL started with HTTPS.