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:
