Closed patsytau closed 2 weeks ago
I was able to install NextCloud on the new Truenas Scale 24.10, but I couldn't fix the alarms it detected. like "trusted_proxies" You can first go to SSH to delete the relevant configuration, or re-mount the app path
This was done with a known-unique app name - as far as I understand matters, that should mean no deletion of configurations from other attempts is necessary.
This was done with a known-unique app name - as far as I understand matters, that should mean no deletion of configurations from other attempts is necessary.
I failed to install at first, the container pool disk can overwrite the installation after the disk is remounted, delete the nextcoud container check delete ix and then reinstall
I've just tried a fresh nextcloud install. Used random name, random user and random passwords. (eg asdfasdfa) It deployed just fine.
Can you try a re-install and try to grab nextcloud logs as soon as possible? The current 'Configuring redis' log lines are probably only the logs after nextcloud failed once.
We will need the logs before those to find out what failed.
Thanks
Hi there, no change unfortunately - it deploys and is listed as 'running' as before, but even if I click the log button as soon as it appears, I get a blank console that says No logs yet
and it never updates, but if I refresh the page an re-open the logs I get the Configuring Redis as session handler
lines again.
Is there another way that I might be able to access the logs? If not, is there any additional information I can provide?
Same result with Nextcloud app version 1.4.3.
You can try opening another tab in truenas shell. Right after you hit install and the progress bar starts, you can start "spamming" this command, it will take few tries to start following the logs, until the nextcloud container is created.
sudo docker logs ix-nextcloud-nextcloud-1 -f
I spammed the command as quickly as I could but only received the following:
root@anastasia:/home/truenas_admin# docker logs ix-nextcloud-nextcloud-1 -f
Error response from daemon: No such container: ix-nextcloud-nextcloud-1
root@anastasia:/home/truenas_admin# docker logs ix-nextcloud-nextcloud-1 -f
Error response from daemon: No such container: ix-nextcloud-nextcloud-1
root@anastasia:/home/truenas_admin# docker logs ix-nextcloud-nextcloud-1 -f
root@anastasia:/home/truenas_admin# docker logs ix-nextcloud-nextcloud-1 -f
root@anastasia:/home/truenas_admin# docker logs ix-nextcloud-nextcloud-1 -f
root@anastasia:/home/truenas_admin# docker logs ix-nextcloud-nextcloud-1 -f
root@anastasia:/home/truenas_admin# docker logs ix-nextcloud-nextcloud-1 -f
root@anastasia:/home/truenas_admin# docker logs ix-nextcloud-nextcloud-1 -f
^[[A
^[[A
^[[A
Configuring Redis as session handler
root@anastasia:/home/truenas_admin# docker logs ix-nextcloud-nextcloud-1 -f
^[[A
Configuring Redis as session handler
Configuring Redis as session handler
root@anastasia:/home/truenas_admin# docker logs ix-nextcloud-nextcloud-1 -f
^[[A
^[[A
Configuring Redis as session handler
Configuring Redis as session handler
Configuring Redis as session handler
root@anastasia:/home/truenas_admin# docker logs ix-nextcloud-nextcloud-1 -f
^[[A
Configuring Redis as session handler
Configuring Redis as session handler
Configuring Redis as session handler
Configuring Redis as session handler
root@anastasia:/home/truenas_admin# docker logs ix-nextcloud-nextcloud-1 -f
Configuring Redis as session handler
Configuring Redis as session handler
Configuring Redis as session handler
Configuring Redis as session handler
Running docker ps
after this gives the following:
ONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
fb81c3f6ccde ix-nextcloud:30.0.1_23837e39bc18b8f10a4bf4d228f5a96b010bf9255353ca6326cb15cef9c7d158 "/entrypoint.sh apac…" 2 minutes ago Restarting (255) 27 seconds ago ix-nextcloud-nextcloud-1
4ec350e8cbb8 postgres:13.16 "docker-entrypoint.s…" 2 minutes ago Up 2 minutes (healthy) 5432/tcp ix-nextcloud-postgres-1
5433586c4f9f bitnami/redis:7.4.1 "/opt/bitnami/script…" 2 minutes ago Up 2 minutes (healthy) 6379/tcp ix-nextcloud-redis-1
It seems to keep restarting, which I guess is why Configuring Redis...
keeps appearing.
You are deleting (selecting to delete ix volumes as well) and recreating each time right?
This seems like nextcloud skips initialization part and goes straight to configuration. Which isn't what should happen in a fresh install
I am, yes. Could log output inadvertently be being redirected elsewhere?
Nope, at least not without manual changes.
Can you also check that there is nothing nextcloud related under /mnt/.ix-apps/app_configs
and /mnt/.ix-apps/app_mounts
?
After deleting the app (with ixVolumes) shows the following before installation:
root@anastasia:/mnt/.ix-apps# ls -la app_configs/
total 20
drwxr-xr-x 8 root root 8 Nov 4 15:20 .
drwxr-xr-x 6 root root 8 Oct 28 19:14 ..
drwxr-xr-x 3 root root 4 Nov 4 14:32 adguard-home
drwxr-xr-x 3 root root 4 Oct 28 22:19 caddy
drwxr-xr-x 3 root root 4 Nov 4 14:32 ddns-updater
drwxr-xr-x 3 root root 4 Oct 29 18:44 forgejo
drwxr-xr-x 3 root root 4 Nov 4 14:32 jellyfin
drwxr-xr-x 3 root root 4 Nov 4 14:33 wg-easy
root@anastasia:/mnt/.ix-apps# ls -la app_mounts/
total 19
drwxr-xr-x 6 root root 6 Nov 4 15:20 .
drwxr-xr-x 6 root root 8 Oct 28 19:14 ..
drwxr-xr-x 4 root root 4 Oct 28 16:52 adguard-home
drwxr-xr-x 3 root root 3 Oct 28 17:05 ddns-updater
drwxr-xr-x 3 root root 3 Oct 28 17:14 jellyfin
drwxr-xr-x 3 root root 3 Nov 2 14:28 wg-easy
root@anastasia:/mnt/.ix-apps# mount | grep next
mycloud/nextcloud on /mnt/mycloud/nextcloud type zfs (rw,relatime,xattr,nfs4acl,casesensitive)
mycloud/nextcloud/db on /mnt/mycloud/nextcloud/db type zfs (rw,relatime,xattr,nfs4acl,casesensitive)
mycloud/nextcloud/files on /mnt/mycloud/nextcloud/files type zfs (rw,relatime,xattr,nfs4acl,casesensitive)
These mounted nextcloud datasets are from my installation on TrueNAS Core.
After installation:
root@anastasia:/mnt/.ix-apps# ls -la app_configs/
total 21
drwxr-xr-x 9 root root 9 Nov 4 15:22 .
drwxr-xr-x 6 root root 8 Oct 28 19:14 ..
drwxr-xr-x 3 root root 4 Nov 4 14:32 adguard-home
drwxr-xr-x 3 root root 4 Oct 28 22:19 caddy
drwxr-xr-x 3 root root 4 Nov 4 14:32 ddns-updater
drwxr-xr-x 3 root root 4 Oct 29 18:44 forgejo
drwxr-xr-x 3 root root 4 Nov 4 14:32 jellyfin
drwxr-xr-x 3 root root 4 Nov 4 15:22 nextcloud
drwxr-xr-x 3 root root 4 Nov 4 14:33 wg-easy
root@anastasia:/mnt/.ix-apps# ls -la app_mounts/
total 20
drwxr-xr-x 7 root root 7 Nov 4 15:21 .
drwxr-xr-x 6 root root 8 Oct 28 19:14 ..
drwxr-xr-x 4 root root 4 Oct 28 16:52 adguard-home
drwxr-xr-x 3 root root 3 Oct 28 17:05 ddns-updater
drwxr-xr-x 3 root root 3 Oct 28 17:14 jellyfin
drwxr-xr-x 5 root root 5 Nov 4 15:22 nextcloud
drwxr-xr-x 3 root root 3 Nov 2 14:28 wg-easy
root@anastasia:/mnt/.ix-apps# mount | grep next
mycloud/nextcloud on /mnt/mycloud/nextcloud type zfs (rw,relatime,xattr,nfs4acl,casesensitive)
mycloud/nextcloud/db on /mnt/mycloud/nextcloud/db type zfs (rw,relatime,xattr,nfs4acl,casesensitive)
mycloud/nextcloud/files on /mnt/mycloud/nextcloud/files type zfs (rw,relatime,xattr,nfs4acl,casesensitive)
mycloud/ix-apps/app_mounts/nextcloud on /mnt/.ix-apps/app_mounts/nextcloud type zfs (rw,noatime,xattr,posixacl,casesensitive)
mycloud/ix-apps/app_mounts/nextcloud/data on /mnt/.ix-apps/app_mounts/nextcloud/data type zfs (rw,noatime,xattr,posixacl,casesensitive)
mycloud/ix-apps/app_mounts/nextcloud/html on /mnt/.ix-apps/app_mounts/nextcloud/html type zfs (rw,noatime,xattr,posixacl,casesensitive)
mycloud/ix-apps/app_mounts/nextcloud/postgres_data on /mnt/.ix-apps/app_mounts/nextcloud/postgres_data type zfs (rw,noatime,xattr,posixacl,casesensitive)
Okay so it's indeed a fresh install. Can you please share the output of the following command?
midclt call app.config nextcloud | jq
Run this while nextcloud is installed, replace nextcloud
with the name you gave to the app (if different)
NOTE: it will contain the passwords you entered.
Here you go. I set every username/password/appname to 'ilikecheese' :)
{
"ix_certificate_authorities": {},
"ix_certificates": {},
"ix_context": {
"app_metadata": {
"app_version": "30.0.1",
"capabilities": [
{
"description": "Nextcloud and Nginx are able to chown files.",
"name": "CHOWN"
},
{
"description": "Nextcloud and Nginx are able to bypass permission checks for it's sub-processes.",
"name": "FOWNER"
},
{
"description": "Nextcloud and Nginx are able to bypass permission checks.",
"name": "DAC_OVERRIDE"
},
{
"description": "Nextcloud and Nginx are able to set group ID for it's sub-processes.",
"name": "SETGID"
},
{
"description": "Nextcloud and Nginx are able to set user ID for it's sub-processes.",
"name": "SETUID"
},
{
"description": "Nextcloud and Nginx are able to bind to privileged ports.",
"name": "NET_BIND_SERVICE"
},
{
"description": "Nextcloud and Nginx are able to use raw sockets.",
"name": "NET_RAW"
}
],
"categories": [
"productivity"
],
"description": "A file sharing server that puts the control and security of your own data back into your hands.",
"home": "https://nextcloud.com/",
"host_mounts": [],
"icon": "https://media.sys.truenas.net/apps/nextcloud/icons/icon.svg",
"keywords": [
"nextcloud",
"storage",
"sync",
"http",
"web",
"php"
],
"last_update": "2024-11-04 13:18:25",
"lib_version": "2.0.7",
"lib_version_hash": "a483d30e0180b3e5f0cff93a55b867dbebe8e3b7561cacc376bfde91865f40d8",
"maintainers": [
{
"email": "dev@ixsystems.com",
"name": "truenas",
"url": "https://www.truenas.com/"
}
],
"name": "nextcloud",
"run_as_context": [
{
"description": "Nextcloud runs as root user.",
"gid": 0,
"group_name": "root",
"uid": 0,
"user_name": "root"
},
{
"description": "Postgres runs as non-root user.",
"gid": 999,
"group_name": "postgres",
"uid": 999,
"user_name": "postgres"
},
{
"description": "Redis runs as a non-root user and root group.",
"gid": 0,
"group_name": "root",
"uid": 1001,
"user_name": "redis"
},
{
"description": "Nginx runs as root user.",
"gid": 0,
"group_name": "root",
"uid": 0,
"user_name": "root"
}
],
"screenshots": [
"https://media.sys.truenas.net/apps/nextcloud/screenshots/screenshot1.png",
"https://media.sys.truenas.net/apps/nextcloud/screenshots/screenshot2.png",
"https://media.sys.truenas.net/apps/nextcloud/screenshots/screenshot3.png"
],
"sources": [
"https://github.com/nextcloud/docker",
"https://github.com/nextcloud/helm",
"https://github.com/truenas/charts/tree/master/charts/nextcloud"
],
"title": "Nextcloud",
"train": "stable",
"version": "1.4.3"
},
"app_name": "ilikecheese",
"is_install": true,
"is_rollback": false,
"is_update": false,
"is_upgrade": false,
"operation": "INSTALL",
"upgrade_metadata": {}
},
"ix_volumes": {
"data": "/mnt/.ix-apps/app_mounts/ilikecheese/data",
"html": "/mnt/.ix-apps/app_mounts/ilikecheese/html",
"postgres_data": "/mnt/.ix-apps/app_mounts/ilikecheese/postgres_data"
},
"network": {
"certificate_id": null,
"dns_opts": [],
"web_port": 30027
},
"nextcloud": {
"additional_envs": [],
"admin_password": "ilikecheese",
"admin_user": "ilikecheese",
"apt_packages": [],
"cron": {
"enabled": false
},
"data_dir_path": "/var/www/html/data",
"db_password": "ilikecheese",
"db_user": "nextcloud",
"host": "",
"max_execution_time": 30,
"op_cache_memory_consumption": 128,
"php_memory_limit": 512,
"php_upload_limit": 3,
"redis_password": "ilikecheese",
"tesseract_languages": []
},
"release_name": "ilikecheese",
"resources": {
"gpus": {
"nvidia_gpu_selection": {},
"use_all_gpus": false
},
"limits": {
"cpus": 2,
"memory": 4096
}
},
"storage": {
"additional_storage": [],
"data": {
"ix_volume_config": {
"acl_enable": false,
"dataset_name": "data"
},
"type": "ix_volume"
},
"html": {
"ix_volume_config": {
"acl_enable": false,
"dataset_name": "html"
},
"type": "ix_volume"
},
"is_data_in_the_same_volume": false,
"postgres_data": {
"ix_volume_config": {
"acl_enable": false,
"dataset_name": "postgres_data"
},
"type": "ix_volume"
}
}
}
Well I like cheese too and I used the same as well.
2024-11-04 15:47:21.982080+00:00Configuring Redis as session handler
2024-11-04 15:47:22.014595+00:00Initializing nextcloud 30.0.1.2 ...
2024-11-04 15:47:30.284237+00:00New nextcloud instance
2024-11-04 15:47:30.312560+00:00Installing with PostgreSQL database
2024-11-04 15:47:30.312675+00:00=> Searching for scripts (*.sh) to run, located in the folder: /docker-entrypoint-hooks.d/pre-installation
2024-11-04 15:47:30.314184+00:00Starting nextcloud installation
2024-11-04 15:47:40.152625+00:00Nextcloud was successfully installed
2024-11-04 15:47:40.163713+00:00Setting trusted domains…
2024-11-04 15:47:40.384188+00:00System config value trusted_domains => 1 set to string 127.0.0.1
2024-11-04 15:47:40.594830+00:00System config value trusted_domains => 2 set to string localhost
2024-11-04 15:47:40.802813+00:00System config value trusted_domains => 3 set to string nextcloud
2024-11-04 15:47:40.812172+00:00=> Searching for scripts (*.sh) to run, located in the folder: /docker-entrypoint-hooks.d/post-installation
2024-11-04 15:47:40.814324+00:00Initializing finished
2024-11-04 15:47:40.829984+00:00=> Searching for scripts (*.sh) to run, located in the folder: /docker-entrypoint-hooks.d/before-starting
2024-11-04 15:47:40.831564+00:00==> Running the script (cwd: /var/www/html): "/docker-entrypoint-hooks.d/before-starting/ix-update-hosts-script.sh"
2024-11-04 15:47:40.836772+00:00Updating database and redis host in config.php
2024-11-04 15:47:41.044385+00:00System config value redis => host set to string redis
2024-11-04 15:47:41.057365+00:00==> Finished the script: "/docker-entrypoint-hooks.d/before-starting/ix-update-hosts-script.sh"
2024-11-04 15:47:41.088451+00:00AH00558: apache2: Could not reliably determine the server's fully qualified domain name, using 172.16.1.4. Set the 'ServerName' directive globally to suppress this message
2024-11-04 15:47:41.100970+00:00AH00558: apache2: Could not reliably determine the server's fully qualified domain name, using 172.16.1.4. Set the 'ServerName' directive globally to suppress this message
2024-11-04 15:47:41.128868+00:00[Mon Nov 04 15:47:41.128804 2024] [mpm_prefork:notice] [pid 1:tid 1] AH00163: Apache/2.4.62 (Debian) PHP/8.2.25 configured -- resuming normal operations
2024-11-04 15:47:41.128908+00:00[Mon Nov 04 15:47:41.128837 2024] [core:notice] [pid 1:tid 1] AH00094: Command line: 'apache2 -D FOREGROUND'
2024-11-04 15:47:42.398576+00:00127.0.0.1 - - [04/Nov/2024:15:47:42 +0000] "GET /status.php HTTP/1.1" 200 1537 "-" "curl/7.88.1"
This is so weird. The script (from upstream) between these 2 lines, has hardly something to fail. Not sure why it doesn't move on on your case :/
2024-11-04 15:47:21.982080+00:00Configuring Redis as session handler
2024-11-04 15:47:22.014595+00:00Initializing nextcloud 30.0.1.2 ...
Can you try:
sudo docker image ls
sudo docker image rm <image_id>
After deleting the app (with ixVolumes) shows the following before installation:
root@anastasia:/mnt/.ix-apps# ls -la app_configs/ total 20 drwxr-xr-x 8 root root 8 Nov 4 15:20 . drwxr-xr-x 6 root root 8 Oct 28 19:14 .. drwxr-xr-x 3 root root 4 Nov 4 14:32 adguard-home drwxr-xr-x 3 root root 4 Oct 28 22:19 caddy drwxr-xr-x 3 root root 4 Nov 4 14:32 ddns-updater drwxr-xr-x 3 root root 4 Oct 29 18:44 forgejo drwxr-xr-x 3 root root 4 Nov 4 14:32 jellyfin drwxr-xr-x 3 root root 4 Nov 4 14:33 wg-easy root@anastasia:/mnt/.ix-apps# ls -la app_mounts/ total 19 drwxr-xr-x 6 root root 6 Nov 4 15:20 . drwxr-xr-x 6 root root 8 Oct 28 19:14 .. drwxr-xr-x 4 root root 4 Oct 28 16:52 adguard-home drwxr-xr-x 3 root root 3 Oct 28 17:05 ddns-updater drwxr-xr-x 3 root root 3 Oct 28 17:14 jellyfin drwxr-xr-x 3 root root 3 Nov 2 14:28 wg-easy root@anastasia:/mnt/.ix-apps# mount | grep next mycloud/nextcloud on /mnt/mycloud/nextcloud type zfs (rw,relatime,xattr,nfs4acl,casesensitive) mycloud/nextcloud/db on /mnt/mycloud/nextcloud/db type zfs (rw,relatime,xattr,nfs4acl,casesensitive) mycloud/nextcloud/files on /mnt/mycloud/nextcloud/files type zfs (rw,relatime,xattr,nfs4acl,casesensitive)
These mounted nextcloud datasets are from my installation on TrueNAS Core.
After installation:
root@anastasia:/mnt/.ix-apps# ls -la app_configs/ total 21 drwxr-xr-x 9 root root 9 Nov 4 15:22 . drwxr-xr-x 6 root root 8 Oct 28 19:14 .. drwxr-xr-x 3 root root 4 Nov 4 14:32 adguard-home drwxr-xr-x 3 root root 4 Oct 28 22:19 caddy drwxr-xr-x 3 root root 4 Nov 4 14:32 ddns-updater drwxr-xr-x 3 root root 4 Oct 29 18:44 forgejo drwxr-xr-x 3 root root 4 Nov 4 14:32 jellyfin drwxr-xr-x 3 root root 4 Nov 4 15:22 nextcloud drwxr-xr-x 3 root root 4 Nov 4 14:33 wg-easy root@anastasia:/mnt/.ix-apps# ls -la app_mounts/ total 20 drwxr-xr-x 7 root root 7 Nov 4 15:21 . drwxr-xr-x 6 root root 8 Oct 28 19:14 .. drwxr-xr-x 4 root root 4 Oct 28 16:52 adguard-home drwxr-xr-x 3 root root 3 Oct 28 17:05 ddns-updater drwxr-xr-x 3 root root 3 Oct 28 17:14 jellyfin drwxr-xr-x 5 root root 5 Nov 4 15:22 nextcloud drwxr-xr-x 3 root root 3 Nov 2 14:28 wg-easy root@anastasia:/mnt/.ix-apps# mount | grep next mycloud/nextcloud on /mnt/mycloud/nextcloud type zfs (rw,relatime,xattr,nfs4acl,casesensitive) mycloud/nextcloud/db on /mnt/mycloud/nextcloud/db type zfs (rw,relatime,xattr,nfs4acl,casesensitive) mycloud/nextcloud/files on /mnt/mycloud/nextcloud/files type zfs (rw,relatime,xattr,nfs4acl,casesensitive) mycloud/ix-apps/app_mounts/nextcloud on /mnt/.ix-apps/app_mounts/nextcloud type zfs (rw,noatime,xattr,posixacl,casesensitive) mycloud/ix-apps/app_mounts/nextcloud/data on /mnt/.ix-apps/app_mounts/nextcloud/data type zfs (rw,noatime,xattr,posixacl,casesensitive) mycloud/ix-apps/app_mounts/nextcloud/html on /mnt/.ix-apps/app_mounts/nextcloud/html type zfs (rw,noatime,xattr,posixacl,casesensitive) mycloud/ix-apps/app_mounts/nextcloud/postgres_data on /mnt/.ix-apps/app_mounts/nextcloud/postgres_data type zfs (rw,noatime,xattr,posixacl,casesensitive)
Switch back to the root directory in the ssh connection during the following operations
cmd:cd ~
First make sure there are no pg containers running Cmd:docker ps -a
There were a few things leftover from an attempt to install the Nextcloud AIO image, but having removed them I get the same logs as before.
@nblky I'm doing this completely with ixVolumes to minimise the risk of any customisation causing problems. When I was trying to use host paths I was also setting the permissions as you suggest.
@nblky unsetting/resetting the mount pool and removing/reinstalling has no impact on the outcome.
@nblky unsetting/resetting the mount pool and removing/reinstalling has no impact on the outcome.
reinstall and change the name like nextcloud-2
I have done so with each reinstallation of the app.
To be honest, I'm currently out of ideas.
Does it work if you use host paths?
Ensure that postgres has 999:999 <user:group>
. (Not ACLs, as it seems that postgres does not like that)
It seems likely that this is something unusual or that I may have had remnants of the AIO image installation still lurking that caused problems. I've got the AIO image up and running, so (at least from my perspective) I'm happy if you want to close this issue with "Something weird happening on her machine.". Thank you for your persistence with this :)
It's still so weird for me :') I'll close this for now, but I'll keep this in the back of my head, if I stumble on something similar and find a solution. I'll let you know!
Thanks!
Setting admin username all passwords to 'test' (just for simplicity), and leaving all other values at their defaults, the Nextcloud app (App Version 30.0.1, Version 1.4.2) does not successfully launch. In the list of apps, it is shown with green status and 'running'. The containers have the following statuses after a few seconds:
The nextcloud log contains only the following lines:
postgres log:
redis log: