[BUG] since ls372, nextcloud no longer works

[stefore]

Is there an existing issue for this?

• I have searched the existing issues

Current Behavior

Hello,
ls371 works great, but with ls372 and ls373, nextcloud no longer work.
I've got an 502 bad gateway error.

nextcloud/config/php/error.log :
[11-Mar-2025 13:42:35] NOTICE: Terminating ...
[11-Mar-2025 13:42:35] NOTICE: exiting, bye-bye!

nextcloud/config/nging/error.log :
2025/03/11 13:43:07 [error] 330#330: *1 connect() failed (111: Connection refused) while connecting to upstream, client: XX.XX.XX.XX, server: _, request: "GET /ocs/v2.php/apps/user_status/api/v1/user_status?format=json HTTP/1.1", upstream: "fastcgi://127.0.0.1:9000", host: "nextcloud.XXXX.fr"
2025/03/11 13:43:07 [error] 331#331: *2 connect() failed (111: Connection refused) while connecting to upstream, client: XX.XX.XX.XX, server: _, request: "GET /ocs/v2.php/apps/notifications/api/v2/notifications?format=json HTTP/1.1", upstream: "fastcgi://127.0.0.1:9000", host: "nextcloud.XXXX.fr"
2025/03/11 13:43:07 [error] 332#332: *5 connect() failed (111: Connection refused) while connecting to upstream, client: XX.XX.XX.XX, server: _, request: "PROPFIND /remote.php/dav/files/XXXX/ HTTP/1.1", upstream: "fastcgi://127.0.0.1:9000", host: "nextcloud.XXXX.fr"
2025/03/11 13:43:37 [error] 330#330: *7 connect() failed (111: Connection refused) while connecting to upstream, client:XX.XX.XX.XX, server: _, request: "PROPFIND /remote.php/dav/files/XXXX/ HTTP/1.1", upstream: "fastcgi://127.0.0.1:9000", host: "nextcloud.XXXX.fr"
2025/03/11 13:43:48 [error] 330#330: *9 connect() failed (111: Connection refused) while connecting to upstream, client: XX.XX.XX.XX, server: _, request: "PROPFIND /remote.php/dav/files/XXXX/ HTTP/1.1", upstream: "fastcgi://127.0.0.1:9000", host: "nextcloud.XXXX.fr"

Expected Behavior

Nextcloud should start.

Steps To Reproduce

run a docker with release ls372 or ls373

Environment

- OS:debian 12.9
- How docker service was installed:
SWAG + nextcloud + mariadb

- Docker version 28.0.1, build 068a01e

CPU architecture

x86-64

Docker creation

swag:
    image: lscr.io/linuxserver/swag
    container_name: swag
    cap_add:
      - NET_ADMIN
    env_file: /home/XXXX/dockers/0env_files/swag.env
    volumes:
      - /home/XXXX/dockers/swag:/config
    ports:
      - 443:443
      - 80:80
    restart: 'no'

  mariadb:
    image: lscr.io/linuxserver/mariadb
    container_name: mariadb
    env_file: /home/XXXX/dockers/0env_files/mariadb.env
    volumes:
      - /home/XXXX/dockers/mariadb:/config
    restart: 'no'


  nextcloud:
    #image: lscr.io/linuxserver/nextcloud:31.0.0-ls371
    image: lscr.io/linuxserver/nextcloud
    container_name: nextcloud
    env_file: /home/XXXX/dockers/0env_files/nextcloud.env
    volumes:
      - /home/XXXX/dockers/nextcloud/config:/config
      - /home/XXXX/dockers/nextcloud/data:/data
    restart: 'no'
    depends_on:
      - mariadb

Container logs

[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:    1000
User GID:    1000
───────────────────────────────────────
Linuxserver.io version: 31.0.0-ls373
Build-date: 2025-03-11T11:52:03+00:00
───────────────────────────────────────
    
using keys found in /config/keys
**** The following site-confs have extensions other than .conf ****
**** This may be due to user customization. ****
**** You should review the files and rename them to use the .conf extension or remove them. ****
**** nginx.conf will only include site-confs with the .conf extension. ****
/config/nginx/site-confs/default.conf.back
Initializing nextcloud  (this can take a while) ...
Setting permissions
New nextcloud instance
Please run the web-based installer on first connect!
Initializing finished
After completing the web-based installer, restart the Nextcloud container to apply default memory caching and transactional file locking configurations.
Alternatively, you can apply your own configurations by editing /config/www/nextcloud/config/config.php following the documentation:
https://docs.nextcloud.com/server/latest/admin_manual/configuration_server/caching_configuration.html
https://docs.nextcloud.com/server/latest/admin_manual/configuration_files/files_locking_transactional.html
[custom-init] No custom files found, skipping...
[ls.io-init] done.

[stefore]

hi,

I've noticed that with the latest version, it always detects a new installation of nextcloud.

nextcloud | Setting permissions
nextcloud | New nextcloud instance
nextcloud | Please run the web-based installer on first connect!
nextcloud | Initializing finished
nextcloud | After completing the web-based installer, restart the Nextcloud container to apply default memory caching and transactional file locking configurations.
nextcloud | Alternatively, you can apply your own configurations by editing /config/www/nextcloud/config/config.php following the documentation:
nextcloud | https://docs.nextcloud.com/server/latest/admin_manual/configuration_server/caching_configuration.html
nextcloud | https://docs.nextcloud.com/server/latest/admin_manual/configuration_files/files_locking_transactional.html
nextcloud | [custom-init] No custom files found, skipping...
nextcloud | [ls.io-init] done.

whereas with release ls371 (which works correctly) it doesn't.
nextcloud | Setting permissions
nextcloud | Initializing finished
nextcloud | [custom-init] No custom files found, skipping...
nextcloud | [ls.io-init] done.

[j0nnymoe]

Have you checked your mariadb instance is working correctly?

[stefore]

I have several containers (freshrss, among others) that work well with the same mariadb container.

I did a test by creating a 2nd blank instance of nextcloud (nextcloud2) and creating the reverse proxy “nextcloud2” in swag (which redirects to the nextcloud2 container). I'm still getting the 502 bad gateway error when I should normally be on the nextcloud installation confirmation screen ....

docker-compose.yaml :

nextcloud:
   image: lscr.io/linuxserver/nextcloud:31.0.0-ls371
    container_name: nextcloud
    env_file: /home/XXXX/dockers/0env_files/nextcloud.env
    volumes:
      - /home/XXXX/dockers/nextcloud/config:/config
      - /home/XXXX/dockers/nextcloud/data:/data
    restart: 'no'
    depends_on:
      - mariadb

  nextcloud2:
    image: lscr.io/linuxserver/nextcloud
    container_name: nextcloud2
    env_file: /home/XXXX/dockers/0env_files/nextcloud.env
    volumes:
      - /home/XXXX/dockers/nextcloud2/config:/config
      - /home/XXXX/dockers/nextcloud2/data:/data
    restart: 'no'
    depends_on:
      - mariadb

content of the file "nextcloud.env" :

PUID=1000
PGID=1000
TZ=Europe/Paris

content of the file "nextcloud2.subdomains.conf":

## Version 2024/07/16
# make sure that your nextcloud container is named nextcloud
# make sure that your dns has a cname set for nextcloud
# assuming this container is called "swag", edit your nextcloud container's config
# located at /config/www/nextcloud/config/config.php and add the following lines before the ");":
#  'trusted_proxies' => [gethostbyname('swag')],
#  'overwrite.cli.url' => 'https://nextcloud.example.com/',
#  'overwritehost' => 'nextcloud.example.com',
#  'overwriteprotocol' => 'https',
#
# Also don't forget to add your domain name to the trusted domains array. It should look somewhat like this:
#  array (
#    0 => '192.168.0.1:444', # This line may look different on your setup, don't modify it.
#    1 => 'nextcloud.example.com',
#  ),

server {
    listen 443 ssl;
    listen [::]:443 ssl;

    server_name nextcloud2.*;

    include /config/nginx/ssl.conf;

    client_max_body_size 0;

    location / {
        include /config/nginx/proxy.conf;
        include /config/nginx/resolver.conf;
        set $upstream_app nextcloud2;
        set $upstream_port 443;
        set $upstream_proto https;
        proxy_pass $upstream_proto://$upstream_app:$upstream_port;

        # Hide proxy response headers from Nextcloud that conflict with ssl.conf
        # Uncomment the Optional additional headers in SWAG's ssl.conf to pass Nextcloud's security scan
        proxy_hide_header Referrer-Policy;
        proxy_hide_header X-Content-Type-Options;
        proxy_hide_header X-Frame-Options;
        proxy_hide_header X-XSS-Protection;

        # Disable proxy buffering
        proxy_buffering off;
    }
}

[j0nnymoe]

Are you able to access the container directly when exposing the ports? Also might be worth showing what's in your .env for nextcloud. I should just read better.

[stefore]

I have mapped the following ports on my new test instance: nextcloud2

ports:
   -8443:443

I'm local and want to access my machine via its address: https://local_ip:8443
I still get error 402 bad gateway. So I can't proceed with the installation / configuration of this new instance.

If I access the logs of this new instance, I get :

config/log/nginx/error.log

2025/03/13 16:31:17 [error] 332#332: *5 connect() failed (111: Connection refused) while connecting to upstream, client: 192.168.0.51, server: _, request: "GET / HTTP/2.0", upstream: "fastcgi://127.0.0.1:9000", host: "192.168.0.102:8443"
2025/03/13 16:31:17 [error] 332#332: *5 connect() failed (111: Connection refused) while connecting to upstream, client: 192.168.0.51, server: _, request: "GET /favicon.ico HTTP/2.0", upstream: "fastcgi://127.0.0.1:9000", host: "192.168.0.102:8443

config/log/nginx/access.log

192.168.0.51 - - [13/Mar/2025:16:31:17 +0100] "GET / HTTP/2.0" 502 552 "-" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/134.0.0.0 Safari/537.36"
192.168.0.51 - - [13/Mar/2025:16:31:17 +0100] "GET /favicon.ico HTTP/2.0" 502 552 "-" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/134.0.0.0 Safari/537.36

config/log/php/error.log is empty

[stefore]

Hello,
I don't understand why, but it worked in the end. The only change was the debian update from 12.9 to 12.10 ....