Cospend, contacts and full text search + nextcloud 30 : unstable server

[coanda45]

Is there an existing issue for this?

• I have searched the existing issues

Current Behavior

Hi,

I just update NC to Nextcoud 30 with the actual latest release (30.0) (Linuxserver one under Synology NAS using docker).

Before I used cospend 1.6 under NC 29.
With NC 30, I update to Cospend 2.0. The update succeeds but I can’ activate it. “The apps makes the server unstable”.
Same problem with contacts and full text search.

Php version is 8.3.12

Do you know what is happening?

Thanks,

Regards,

Fabien
P.S. other similar post: https://help.nextcloud.com/t/cospend-contacts-and-full-text-search-nextcloud-30-unstable-server/206039/1 and julien-nc/cospend-nc#308

Expected Behavior

No response

Steps To Reproduce

From Nextcloud 29.0.3 to Nextcloud 30.0 linuxserver.
Using deploy container function of portainer.

Environment

- OS:Synology NAS DSM 7.2

CPU architecture

x86-64

Docker creation

---
services:
  nextcloud:
    image: lscr.io/linuxserver/nextcloud:latest
    container_name: nextcloud-new
    environment:
      - PUID=1026
      - PGID=100
      - TZ=Europe/Paris
    volumes:
      - ./config:/config
      - ./data:/data
    ports:
      - yyyy:443
    restart: unless-stopped
  mariadb:
    image: lscr.io/linuxserver/mariadb:latest
    container_name: nextcloud-new-mariadb
    environment:
      - PUID=1026
      - PGID=100
      - TZ=Europe/Paris
      - MYSQL_ROOT_PASSWORD=xxxxxxxxxxxxxxxxxxxx
      - MYSQL_DATABASE=nextcloud #optional
      - MYSQL_USER=xxxxxxxxxxxxx #optional
      - MYSQL_PASSWORD=xxxxxxxxxxxxxxxxxxx #optional
#      - REMOTE_SQL=http://URL1/your.sql,https://URL2/your.sql #optional
    volumes:
      - ./db-config:/config
    ports:
      - yyyy:3306
    restart: unless-stopped

Container logs

sudo docker logs nextcloud-new
[migrations] started
[migrations] 01-nginx-site-confs-default: skipped
[migrations] 02-default-location: skipped
[migrations] done
───────────────────────────────────────

      ██╗     ███████╗██╗ ██████╗
      ██║     ██╔════╝██║██╔═══██╗
      ██║     ███████╗██║██║   ██║
      ██║     ╚════██║██║██║   ██║
      ███████╗███████║██║╚██████╔╝
      ╚══════╝╚══════╝╚═╝ ╚═════╝

   Brought to you by linuxserver.io
───────────────────────────────────────

To support LSIO projects visit:
https://www.linuxserver.io/donate/

───────────────────────────────────────
GID/UID
───────────────────────────────────────

User UID:    1026
User GID:    100
───────────────────────────────────────
Linuxserver.io version: 30.0.0-ls345
Build-date: 2024-10-08T11:50:56+00:00
───────────────────────────────────────
    
using keys found in /config/keys
Initializing nextcloud 30.0.0.14 (this can take a while) ...
Setting permissions
Initializing finished
**** The following active confs have different version dates than the samples that are shipped. ****
**** This may be due to user customization or an update to the samples. ****
**** You should compare the following files to the samples in the same folder and update them. ****
**** Use the link at the top of the file to view the changelog. ****
┌────────────┬────────────┬────────────────────────────────────────────────────────────────────────┐
│  old date  │  new date  │ path                                                                   │
├────────────┼────────────┼────────────────────────────────────────────────────────────────────────┤
│ 2024-06-24 │ 2024-07-16 │ /config/nginx/site-confs/default.conf                                  │
└────────────┴────────────┴────────────────────────────────────────────────────────────────────────┘
[custom-init] No custom files found, skipping...
[ls.io-init] done.

[github-actions]

Thanks for opening your first issue here! Be sure to follow the relevant issue templates, or risk having this issue marked as invalid.

[j0nnymoe]

This is usually caused by an incorrectly configured config.php within nextcloud. Need to make sure your default.conf is up to date as well.

[LinuxServer-CI]

This issue has been automatically marked as stale because it has not had recent activity. This might be due to missing feedback from OP. It will be closed if no further activity occurs. Thank you for your contributions.