[BUG] Security and setup check fails in 28.0.1

[ntompson]

Is there an existing issue for this?

• [X] I have searched the existing issues

Current Behavior

When navigating to the Administration Overview page(/settings/admin/overview), the automated checks fail:

The java console reports 3 errors, which I have not seen before:

Expected Behavior

In previous versions, the automated checks complete and either give me an all OK message, or point to issues that need to be resolved. I've never seen this failure before

Steps To Reproduce

As above, in a browser, navigate to /settings/admin/overview and see error message after waiting for some time for automated checks to complete.

Environment

- OS: Debian bullseye (11.8) (Linux xxxxx 5.10.0-26-amd64 #1 SMP Debian 5.10.197-1 (2023-09-29) x86_64 GNU/Linux)
- How docker service was installed: distro package manager (apt)

CPU architecture

x86-64

Docker creation

YAML docker compose file:

---
version: "3"
services:
  nextcloud:
    image: linuxserver/nextcloud:28.0.1
    container_name: nextcloud
    environment:
      - PUID=912
      - PGID=912
      - TZ=Australia/Hobart
    volumes:
      - /home/nick/docker/nextcloud/config:/config
      - /mnt/Calypso/nc-data:/data
    depends_on:
      - redis
    restart: unless-stopped
    networks:
      - swag_proxy-net
      - redis-net

  redis:
    image: redis:7.2.3
    volumes:
      - /home/nick/docker/redis:/data
    restart: unless-stopped
    container_name: redis
    networks:
      - redis-net

networks:
  swag_proxy-net:
    external: true
  redis-net:
    driver: bridge

Container logs

docker logs nextcloud
[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:    912
User GID:    912
───────────────────────────────────────

using keys found in /config/keys
Initializing nextcloud 28.0.1.1 (this can take a while) ...
Setting permissions
Initializing finished
[custom-init] No custom files found, skipping...
[ls.io-init] done.

[ntompson]

I should add: I have updated the default.conf file to the latest version as directed. I am also running through the SWAG reverse proxy using all latest config.

[ntompson]

An update. The 504 issue has disappeared (and consequently the security and setup check completes correctly. However, the two 404s remain. I don't know whether they matter...?

[DoubleAps1]

I should add: I have updated the default.conf file to the latest version as directed. I am also running through the SWAG reverse proxy using all latest config.

Thanks for this. I was able to fix the external scan and now it identifies the correct version I'm running. Unfortunately, the internal scan still fails with the error that you specified in the 1st post.

Just to provide path for anyone else. The file is located in the path below. I just ended up renaming the current default.conf and renaming default.conf.sample to default.conf.

/config/nginx/site-confs

[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.

[homerr]

Closing out as this was likely a result of bugs in NC 28 prior to 28.0.3 - no need to worry about the 404's they relate to the certificate generation (if needed).

[ntompson]

Why was this closed? It is still an issue in 28.0.4:

The setup checks take forever to run (they used to come back quickly). There's clearly something wrong here. My config is as recommended by you guys -- not sure what else I can do?

[github-actions[bot]]

This issue is locked due to inactivity