[Support] Linuxserver.io - Nextcloud


Recommended Posts

Hello everyone. especially @skois and @saarg as it seems like you answer this question the most. and i have read multiple times where you reference the fix to this issue but i am still having the "well-known/" issues (pasted below). I have tried all fixes on this forum and on the github issues such as deleting default file, clearing browser cache (even tried the way mentioned on git issue by right clicking the refresh and doing the dump and hard reload that way.), Ive changed the docker tags, updated nextcloud to latest version 21.0.1. I'm not using any proxy nextcloud is only available on my local network or through VPN. unraid version 6.9.2 (if this matters in this situation)
 
I can provide any logs, outputs, or info needed.
 
i really am sorry if i passed over the answer to this question but last night i read through the last 92 pages post by post and have not found a solution to my issue.
 
The last option i haven't tried is complete delete the docker and try again but from everything i read that's not the solution and ill still have same issue.
 
Your web server is not properly set up to resolve "/.well-known/webfinger". Further information can be found in the documentation.
Your web server is not properly set up to resolve "/.well-known/nodeinfo". Further information can be found in the documentation.
Your web server is not properly set up to resolve "/.well-known/caldav". Further information can be found in the documentation.
Your web server is not properly set up to resolve "/.well-known/carddav". Further information can be found in the documentation.
 
Wait, I have the impression, that well known error fix needs the server accessible through reverse proxy. But I'm not really sure.

Sent from my Mi 10 Pro using Tapatalk

Link to comment
4 hours ago, Aspect said:

Hello everyone. especially @skois and @saarg as it seems like you answer this question the most. and i have read multiple times where you reference the fix to this issue but i am still having the "well-known/" issues (pasted below). I have tried all fixes on this forum and on the github issues such as deleting default file, clearing browser cache (even tried the way mentioned on git issue by right clicking the refresh and doing the dump and hard reload that way.), Ive changed the docker tags, updated nextcloud to latest version 21.0.1. I'm not using any proxy nextcloud is only available on my local network or through VPN. unraid version 6.9.2 (if this matters in this situation)

 

I can provide any logs, outputs, or info needed.

 

i really am sorry if i passed over the answer to this question but last night i read through the last 92 pages post by post and have not found a solution to my issue.

 

The last option i haven't tried is complete delete the docker and try again but from everything i read that's not the solution and ill still have same issue.

 

Your web server is not properly set up to resolve "/.well-known/webfinger". Further information can be found in the documentation.

Your web server is not properly set up to resolve "/.well-known/nodeinfo". Further information can be found in the documentation.

Your web server is not properly set up to resolve "/.well-known/caldav". Further information can be found in the documentation.

Your web server is not properly set up to resolve "/.well-known/carddav". Further information can be found in the documentation.

 

Post your default file.

Link to comment
3 hours ago, skois said:

Wait, I have the impression, that well known error fix needs the server accessible through reverse proxy. But I'm not really sure.

Sent from my Mi 10 Pro using Tapatalk
 

The fix is in the default file of the nextcloud container.

Link to comment

upstream php-handler {
    server 127.0.0.1:9000;
}
server {
    listen 80;
    listen [::]:80;
    server_name _;
    return 301 https://$host$request_uri;
}
server {
    listen 443 ssl http2;
    listen [::]:443 ssl http2;
    server_name _;
    ssl_certificate /config/keys/cert.crt;
    ssl_certificate_key /config/keys/cert.key;

    # Add headers to serve security related headers
    # Before enabling Strict-Transport-Security headers please read into this
    # topic first.
    add_header Strict-Transport-Security "max-age=15768000; includeSubDomains; preload;" always;
    #
    # WARNING: Only add the preload option once you read about
    # the consequences in https://hstspreload.org/. This option
    # will add the domain to a hardcoded list that is shipped
    # in all major browsers and getting removed from this list
    # could take several months.

    # set max upload size
    client_max_body_size 512M;
    fastcgi_buffers 64 4K;

    # Enable gzip but do not remove ETag headers
    gzip on;
    gzip_vary on;
    gzip_comp_level 4;
    gzip_min_length 256;
    gzip_proxied expired no-cache no-store private no_last_modified no_etag auth;
    gzip_types application/atom+xml application/javascript application/json application/ld+json application/manifest+json application/rss+xml application/vnd.geo+json application/vnd.ms-fontobject application/x-font-ttf application/x-web-app-manifest+json application/xhtml+xml application/xml font/opentype image/bmp image/svg+xml image/x-icon text/cache-manifest text/css text/plain text/vcard text/vnd.rim.location.xloc text/vtt text/x-component text/x-cross-domain-policy;

    # HTTP response headers borrowed from Nextcloud `.htaccess`
    add_header Referrer-Policy                      "no-referrer"   always;
    add_header X-Content-Type-Options               "nosniff"       always;
    add_header X-Download-Options                   "noopen"        always;
    add_header X-Frame-Options                      "SAMEORIGIN"    always;
    add_header X-Permitted-Cross-Domain-Policies    "none"          always;
    add_header X-Robots-Tag                         "none"          always;
    add_header X-XSS-Protection                     "1; mode=block" always;

    # Remove X-Powered-By, which is an information leak
    fastcgi_hide_header X-Powered-By;

    root /config/www/nextcloud/;

    # display real ip in nginx logs when connected through reverse proxy via docker network
    set_real_ip_from 172.0.0.0/8;
    real_ip_header X-Forwarded-For;

    # Specify how to handle directories -- specifying `/index.php$request_uri`
    # here as the fallback means that Nginx always exhibits the desired behaviour
    # when a client requests a path that corresponds to a directory that exists
    # on the server. In particular, if that directory contains an index.php file,
    # that file is correctly served; if it doesn't, then the request is passed to
    # the front-end controller. This consistent behaviour means that we don't need
    # to specify custom rules for certain paths (e.g. images and other assets,
    # `/updater`, `/ocm-provider`, `/ocs-provider`), and thus
    # `try_files $uri $uri/ /index.php$request_uri`
    # always provides the desired behaviour.
    index index.php index.html /index.php$request_uri;

    # Rule borrowed from `.htaccess` to handle Microsoft DAV clients
    location = / {
        if ( $http_user_agent ~ ^DavClnt ) {
            return 302 /remote.php/webdav/$is_args$args;
        }
    }
    # Make a regex exception for `/.well-known` so that clients can still
    # access it despite the existence of the regex rule
    # `location ~ /(\.|autotest|...)` which would otherwise handle requests
    # for `/.well-known`.
    location ^~ /.well-known {
        # The following 6 rules are borrowed from `.htaccess`

        location = /.well-known/carddav     { return 301 /remote.php/dav/; }
        location = /.well-known/caldav      { return 301 /remote.php/dav/; }
        # Anything else is dynamically handled by Nextcloud
        location ^~ /.well-known            { return 301 /index.php$uri; }

        try_files $uri $uri/ =404;
    }

    # Rules borrowed from `.htaccess` to hide certain paths from clients
    location ~ ^/(?:build|tests|config|lib|3rdparty|templates|data)(?:$|/)  { return 404; }
    location ~ ^/(?:\.|autotest|occ|issue|indie|db_|console)              { return 404; }

    # Ensure this block, which passes PHP files to the PHP process, is above the blocks
    # which handle static assets (as seen below). If this block is not declared first,
    # then Nginx will encounter an infinite rewriting loop when it prepends `/index.php`
    # to the URI, resulting in a HTTP 500 error response.
    location ~ \.php(?:$|/) {
        fastcgi_split_path_info ^(.+?\.php)(/.*)$;
        set $path_info $fastcgi_path_info;

        try_files $fastcgi_script_name =404;

        include /etc/nginx/fastcgi_params;
        fastcgi_param SCRIPT_FILENAME $document_root$fastcgi_script_name;
        fastcgi_param PATH_INFO $path_info;
        fastcgi_param HTTPS on;

        fastcgi_param modHeadersAvailable true;         # Avoid sending the security headers twice
        fastcgi_param front_controller_active true;     # Enable pretty urls
        fastcgi_pass php-handler;

        fastcgi_intercept_errors on;
        fastcgi_request_buffering off;
    }

    location ~ \.(?:css|js|svg|gif)$ {
        try_files $uri /index.php$request_uri;
        expires 6M;         # Cache-Control policy borrowed from `.htaccess`
        access_log off;     # Optional: Don't log access to assets
    }

    location ~ \.woff2?$ {
        try_files $uri /index.php$request_uri;
        expires 7d;         # Cache-Control policy borrowed from `.htaccess`
        access_log off;     # Optional: Don't log access to assets
    }

    location / {
        try_files $uri $uri/ /index.php$request_uri;
    }

}

Link to comment
13 hours ago, Aspect said:

upstream php-handler {
    server 127.0.0.1:9000;
}
server {
    listen 80;
    listen [::]:80;
    server_name _;
    return 301 https://$host$request_uri;
}
server {
    listen 443 ssl http2;
    listen [::]:443 ssl http2;
    server_name _;
    ssl_certificate /config/keys/cert.crt;
    ssl_certificate_key /config/keys/cert.key;

    # Add headers to serve security related headers
    # Before enabling Strict-Transport-Security headers please read into this
    # topic first.
    add_header Strict-Transport-Security "max-age=15768000; includeSubDomains; preload;" always;
    #
    # WARNING: Only add the preload option once you read about
    # the consequences in https://hstspreload.org/. This option
    # will add the domain to a hardcoded list that is shipped
    # in all major browsers and getting removed from this list
    # could take several months.

    # set max upload size
    client_max_body_size 512M;
    fastcgi_buffers 64 4K;

    # Enable gzip but do not remove ETag headers
    gzip on;
    gzip_vary on;
    gzip_comp_level 4;
    gzip_min_length 256;
    gzip_proxied expired no-cache no-store private no_last_modified no_etag auth;
    gzip_types application/atom+xml application/javascript application/json application/ld+json application/manifest+json application/rss+xml application/vnd.geo+json application/vnd.ms-fontobject application/x-font-ttf application/x-web-app-manifest+json application/xhtml+xml application/xml font/opentype image/bmp image/svg+xml image/x-icon text/cache-manifest text/css text/plain text/vcard text/vnd.rim.location.xloc text/vtt text/x-component text/x-cross-domain-policy;

    # HTTP response headers borrowed from Nextcloud `.htaccess`
    add_header Referrer-Policy                      "no-referrer"   always;
    add_header X-Content-Type-Options               "nosniff"       always;
    add_header X-Download-Options                   "noopen"        always;
    add_header X-Frame-Options                      "SAMEORIGIN"    always;
    add_header X-Permitted-Cross-Domain-Policies    "none"          always;
    add_header X-Robots-Tag                         "none"          always;
    add_header X-XSS-Protection                     "1; mode=block" always;

    # Remove X-Powered-By, which is an information leak
    fastcgi_hide_header X-Powered-By;

    root /config/www/nextcloud/;

    # display real ip in nginx logs when connected through reverse proxy via docker network
    set_real_ip_from 172.0.0.0/8;
    real_ip_header X-Forwarded-For;

    # Specify how to handle directories -- specifying `/index.php$request_uri`
    # here as the fallback means that Nginx always exhibits the desired behaviour
    # when a client requests a path that corresponds to a directory that exists
    # on the server. In particular, if that directory contains an index.php file,
    # that file is correctly served; if it doesn't, then the request is passed to
    # the front-end controller. This consistent behaviour means that we don't need
    # to specify custom rules for certain paths (e.g. images and other assets,
    # `/updater`, `/ocm-provider`, `/ocs-provider`), and thus
    # `try_files $uri $uri/ /index.php$request_uri`
    # always provides the desired behaviour.
    index index.php index.html /index.php$request_uri;

    # Rule borrowed from `.htaccess` to handle Microsoft DAV clients
    location = / {
        if ( $http_user_agent ~ ^DavClnt ) {
            return 302 /remote.php/webdav/$is_args$args;
        }
    }
    # Make a regex exception for `/.well-known` so that clients can still
    # access it despite the existence of the regex rule
    # `location ~ /(\.|autotest|...)` which would otherwise handle requests
    # for `/.well-known`.
    location ^~ /.well-known {
        # The following 6 rules are borrowed from `.htaccess`

        location = /.well-known/carddav     { return 301 /remote.php/dav/; }
        location = /.well-known/caldav      { return 301 /remote.php/dav/; }
        # Anything else is dynamically handled by Nextcloud
        location ^~ /.well-known            { return 301 /index.php$uri; }

        try_files $uri $uri/ =404;
    }

    # Rules borrowed from `.htaccess` to hide certain paths from clients
    location ~ ^/(?:build|tests|config|lib|3rdparty|templates|data)(?:$|/)  { return 404; }
    location ~ ^/(?:\.|autotest|occ|issue|indie|db_|console)              { return 404; }

    # Ensure this block, which passes PHP files to the PHP process, is above the blocks
    # which handle static assets (as seen below). If this block is not declared first,
    # then Nginx will encounter an infinite rewriting loop when it prepends `/index.php`
    # to the URI, resulting in a HTTP 500 error response.
    location ~ \.php(?:$|/) {
        fastcgi_split_path_info ^(.+?\.php)(/.*)$;
        set $path_info $fastcgi_path_info;

        try_files $fastcgi_script_name =404;

        include /etc/nginx/fastcgi_params;
        fastcgi_param SCRIPT_FILENAME $document_root$fastcgi_script_name;
        fastcgi_param PATH_INFO $path_info;
        fastcgi_param HTTPS on;

        fastcgi_param modHeadersAvailable true;         # Avoid sending the security headers twice
        fastcgi_param front_controller_active true;     # Enable pretty urls
        fastcgi_pass php-handler;

        fastcgi_intercept_errors on;
        fastcgi_request_buffering off;
    }

    location ~ \.(?:css|js|svg|gif)$ {
        try_files $uri /index.php$request_uri;
        expires 6M;         # Cache-Control policy borrowed from `.htaccess`
        access_log off;     # Optional: Don't log access to assets
    }

    location ~ \.woff2?$ {
        try_files $uri /index.php$request_uri;
        expires 7d;         # Cache-Control policy borrowed from `.htaccess`
        access_log off;     # Optional: Don't log access to assets
    }

    location / {
        try_files $uri $uri/ /index.php$request_uri;
    }

}

Next time you post a config file or log, please use the code formatting. It's not easy to look at this on a mobile device when the formatting is screwed up.

 

The file looks like it's the latest version, so try using incognito mode or private mode in your browser.

Link to comment
7 hours ago, DockX said:

I have tried  incognito and other devices. But the message stays.

 

I just installed a fresh nextcloud container here and there are no messages about missing well-known stuff.

Post your docker run command, how you connect to nextcloud and exactly what you have been doing to try to fix it. And use the code tag.

 

 

Screenshot from 2021-04-22 18-18-35.png

Edited by saarg
Link to comment

sorry for not using code tag.

 

so far my steps are as follows:

 

  • tried to edit the original default file before consulting the forum or anything else really
  • read forum deleted default file
  • edited NEW default file to remove strict header warning (successfully)
  • ive tried to make my own default file by copying whats on nextclouds documentation
  • ive cleared my browser cache
  • ive deleted my browser
  • ive used every browser in regular mode
  • ive used every browser in incognito mode
  • ive accessed nextcloud from different devices in my LAN
  • ive accessed nextcloud from different devices over VPN

I have received the same errors with every solution Ive tried above

 

[s6-init] making user provided files available at /var/run/s6/etc...exited 0.
[s6-init] ensuring user provided files have correct perms...exited 0.
[fix-attrs.d] applying ownership & permissions fixes...
[fix-attrs.d] done.
[cont-init.d] executing container initialization scripts...
[cont-init.d] 01-envfile: executing...
[cont-init.d] 01-envfile: exited 0.
[cont-init.d] 10-adduser: executing...
usermod: no changes

-------------------------------------
_ ()
| | ___ _ __
| | / __| | | / \
| | \__ \ | | | () |
|_| |___/ |_| \__/


Brought to you by linuxserver.io
-------------------------------------

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

User uid: 99
User gid: 100
-------------------------------------

[cont-init.d] 10-adduser: exited 0.
[cont-init.d] 20-config: executing...
[cont-init.d] 20-config: exited 0.
[cont-init.d] 30-keygen: executing...
using keys found in /config/keys
[cont-init.d] 30-keygen: exited 0.
[cont-init.d] 40-config: executing...
[cont-init.d] 40-config: exited 0.
[cont-init.d] 50-install: executing...
[cont-init.d] 50-install: exited 0.
[cont-init.d] 60-memcache: executing...
[cont-init.d] 60-memcache: exited 0.
[cont-init.d] 70-aliases: executing...
[cont-init.d] 70-aliases: exited 0.
[cont-init.d] 99-custom-files: executing...
[custom-init] no custom files found exiting...
[cont-init.d] 99-custom-files: exited 0.
[cont-init.d] done.
[services.d] starting services
[services.d] done.

 

Edited by Aspect
Link to comment

hi guys I'm trying to update from 20.0.9 to 21.0.1 but I am having issues updating. I get a error message at step 3. something along the lines of gateway timeout. I also tried to update nextcloud using command line. but that resulted in a error when trying to run occ upgrade. exception: Database error when running migration latest for app core. I ended up restoring to a backup from yesterday. sorry I am new to this. ty

Link to comment
16 hours ago, saarg said:

 

I just installed a fresh nextcloud container here and there are no messages about missing well-known stuff.

Post your docker run command, how you connect to nextcloud and exactly what you have been doing to try to fix it. And use the code tag.

 

Hi,

thanks for testing it @saarg. I guess it has something to do with SWAG then. Here is my compose file:

version: "3.3"
services:
  swag:
    container_name: SWAG
    image: linuxserver/swag
    cap_add:
      - NET_ADMIN
    ports:
      - 80:80
      - 443:443
    volumes:
      - /data/SWAG:/config
      - /data/Nextcloud_config/log/nextcloud:/config/log/nextcloud
    restart: unless-stopped
    environment:
      - PUID=1000
      - PGID=100
      - EMAIL=*
      - URL=*
      - SUBDOMAINS=*
      - ONLY_SUBDOMAINS=true
      - DHLEVEL=4096
      - TZ=Europe/Berlin
  nextcloud:
    image: linuxserver/nextcloud
    container_name: nextcloud
    hostname: Nextcloud
    environment:
      - PUID=1000
      - PGID=100
      - TZ=Europe/Berlin
    ports:
      - 8011:443
    volumes:
      - /data/Nextcloud_config:/config
      - /data/Nextcloud_data:/data
    depends_on:
      - mariadb
      - redis
    restart: unless-stopped
  mariadb:
    image: linuxserver/mariadb
    container_name: mariadb
    environment:
      - PUID=1000
      - PGID=100
      - MYSQL_ROOT_PASSWORD=*
      - TZ=Europe/Berlin
    volumes:
      - /data/MariaDB:/config

 

Maybe subfolder.conf needs a change:

 

## Version 2020/12/09
# 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' => ['swag'],
#  'overwritewebroot' => '/nextcloud',
#  'overwrite.cli.url' => 'https://your-domain.com/nextcloud',
#
# 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 => 'your-domain.com',
#  ),

# Redirects for DAV clients
location = /.well-known/carddav {
    return 301 $scheme://$host/nextcloud/remote.php/dav;
}

location = /.well-known/caldav {
    return 301 $scheme://$host/nextcloud/remote.php/dav;
}

location /nextcloud {
    return 301 $scheme://$host/nextcloud/;
}

location ^~ /nextcloud/ {
    include /config/nginx/proxy.conf;
    resolver 127.0.0.11 valid=30s;
    set $upstream_app nextcloud;
    set $upstream_port 443;
    set $upstream_proto https;
    proxy_pass $upstream_proto://$upstream_app:$upstream_port;

    rewrite /nextcloud(.*) $1 break;
    proxy_max_temp_file_size 2048m;
    proxy_set_header Range $http_range;
    proxy_set_header If-Range $http_if_range;
    proxy_redirect off;
    proxy_ssl_session_reuse off;
}

 

Link to comment
On 4/20/2021 at 10:06 PM, Carlos said:

Hi there,

 

As as said before, my smartphone won't connect to the Nextcloud server using the domain via WiFi neither using the browser nor the app (using 4G works fine). For a moment Pi-Hole crossed my mind as a possible cause but disabling it nothing changes.

 

Cheers

 

On 4/21/2021 at 8:24 AM, saarg said:

 

Then it's something in your network not resolving the domain.

Well, I finally found the issue. My ISP updated the fiber router and that caused my problem connecting to the server using WiFi. Surprisingly using the 5GHz WiFi worked fine. Anyway, rolled back the firmware, blocked remote updates and now it's working fine again.

 

Thanks

Link to comment
5 hours ago, DockX said:

Hi,

thanks for testing it @saarg. I guess it has something to do with SWAG then. Here is my compose file:


version: "3.3"
services:
  swag:
    container_name: SWAG
    image: linuxserver/swag
    cap_add:
      - NET_ADMIN
    ports:
      - 80:80
      - 443:443
    volumes:
      - /data/SWAG:/config
      - /data/Nextcloud_config/log/nextcloud:/config/log/nextcloud
    restart: unless-stopped
    environment:
      - PUID=1000
      - PGID=100
      - EMAIL=*
      - URL=*
      - SUBDOMAINS=*
      - ONLY_SUBDOMAINS=true
      - DHLEVEL=4096
      - TZ=Europe/Berlin
  nextcloud:
    image: linuxserver/nextcloud
    container_name: nextcloud
    hostname: Nextcloud
    environment:
      - PUID=1000
      - PGID=100
      - TZ=Europe/Berlin
    ports:
      - 8011:443
    volumes:
      - /data/Nextcloud_config:/config
      - /data/Nextcloud_data:/data
    depends_on:
      - mariadb
      - redis
    restart: unless-stopped
  mariadb:
    image: linuxserver/mariadb
    container_name: mariadb
    environment:
      - PUID=1000
      - PGID=100
      - MYSQL_ROOT_PASSWORD=*
      - TZ=Europe/Berlin
    volumes:
      - /data/MariaDB:/config

 

Maybe subfolder.conf needs a change:

 


## Version 2020/12/09
# 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' => ['swag'],
#  'overwritewebroot' => '/nextcloud',
#  'overwrite.cli.url' => 'https://your-domain.com/nextcloud',
#
# 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 => 'your-domain.com',
#  ),

# Redirects for DAV clients
location = /.well-known/carddav {
    return 301 $scheme://$host/nextcloud/remote.php/dav;
}

location = /.well-known/caldav {
    return 301 $scheme://$host/nextcloud/remote.php/dav;
}

location /nextcloud {
    return 301 $scheme://$host/nextcloud/;
}

location ^~ /nextcloud/ {
    include /config/nginx/proxy.conf;
    resolver 127.0.0.11 valid=30s;
    set $upstream_app nextcloud;
    set $upstream_port 443;
    set $upstream_proto https;
    proxy_pass $upstream_proto://$upstream_app:$upstream_port;

    rewrite /nextcloud(.*) $1 break;
    proxy_max_temp_file_size 2048m;
    proxy_set_header Range $http_range;
    proxy_set_header If-Range $http_if_range;
    proxy_redirect off;
    proxy_ssl_session_reuse off;
}

 

I'm confused now. Are you having two accounts here and posting as aspect also or did you just piggytail on his problem answering my post to him.

Seeing you are not using unraid, please go to linuxserver.io/support and either join our discord or discourse forum to get support. This is for unraid users only.

Link to comment
On 4/21/2021 at 1:01 AM, skois said:

As i said it's on the /data folder not config.

 

So i have gone through every folder that has to do with Nextcloud... and never found what you are tell me i should see. is there a chance that my "/data" folder could be called something else?

Link to comment
28 minutes ago, kerpster said:

So i have gone through every folder that has to do with Nextcloud... and never found what you are tell me i should see. is there a chance that my "/data" folder could be called something else?

Please ignore me... i dont have a /data folder..... but i did manage to figure out that this stupid .step file is a hidden file and for some reason my checkbox was unchecked to see them. thank you for the help.

Link to comment
25 minutes ago, kerpster said:

Please ignore me... i dont have a /data folder..... but i did manage to figure out that this stupid .step file is a hidden file and for some reason my checkbox was unchecked to see them. thank you for the help.

So i deleted the step file and now it just says update in progress. i ran "updater.phar" in the terminal and just get "Step 6 is currently in process. Please call this command later." Did i delete the wrong one... and i 100% dont have a /data folder

Link to comment
16 hours ago, akash3230 said:

hi guys I'm trying to update from 20.0.9 to 21.0.1 but I am having issues updating. I get a error message at step 3. something along the lines of gateway timeout. I also tried to update nextcloud using command line. but that resulted in a error when trying to run occ upgrade. exception: Database error when running migration latest for app core. I ended up restoring to a backup from yesterday. sorry I am new to this. ty

Bump

Link to comment
Bump
Without detailed steps you did and logs, you only gonna get something along the lines "try running the update again"

Adding as much info as possible in the first post, would make anyone who try to help, have a bigger picture of what might have gone wrong.

Tbh when I see posts "x" don't work, gives an generic error. I just scroll.

Sent from my Mi 10 Pro using Tapatalk


Link to comment
13 hours ago, Aspect said:

@saarg i don't want to speak for someone else but @DockX and i are two separate people.

 

i am using unraid and i broke down some of the steps ive used as well as my run for you in this post (didnt want to double post) sorry for the confusion.

 

I don't see the docker run command there and it's not really enough detailed info about what you have done.

But could you try to set up a new nextcloud container and be sure to use anothe folder for both appdata and data. You can use sqlite for database. I just want to see if you get the same errors then, as I'm not getting it.

Link to comment
14 hours ago, saarg said:

I don't see the docker run command there and it's not really enough detailed info about what you have done.

But could you try to set up a new nextcloud container and be sure to use anothe folder for both appdata and data. You can use sqlite for database. I just want to see if you get the same errors then, as I'm not getting it.

@saarg Unfortunately fresh install is having same issue (screen shots of new install)

 

ill do my best this time to provide the information you need to assist.

 

30908583_Screenshotfrom2021-04-2420-39-48.thumb.png.2a748efe47a32e269719741f49a968f8.png753960693_Screenshotfrom2021-04-2420-40-12.thumb.png.5d37a23dfc2ef621a1fcdd245be938fa.png

Link to comment
On 4/23/2021 at 6:58 PM, skois said:

Without detailed steps you did and logs, you only gonna get something along the lines "try running the update again"

Adding as much info as possible in the first post, would make anyone who try to help, have a bigger picture of what might have gone wrong.

Tbh when I see posts "x" don't work, gives an generic error. I just scroll.

Sent from my Mi 10 Pro using Tapatalk

 

thank you for your reply. I'm sorry I am new to all of this. what kind of information should I include in the post?

Link to comment
On 4/23/2021 at 11:17 PM, kerpster said:

So i deleted the step file and now it just says update in progress. i ran "updater.phar" in the terminal and just get "Step 6 is currently in process. Please call this command later." Did i delete the wrong one... and i 100% dont have a /data folder

Yes, you do have a /data folder, otherwise you would not have any user files stored. You just have to find where you mapped it.
 

image.thumb.png.dd65f81d88921b8945367e4c51dbc610.png

 

So, in the /data/updater-xhsdfh643 (whatever random you have) 
there is 2 folders and 0, 1 or 2 hidden files. Open downloads and delete if anything is inside.
Also if you have a .step file delete it,  you don't have to delete the .step-previous-update)

 

image.png.27394873d64218281a0050c72dd802d6.png

 

Now restart docker (right click on it and restart)

Open console (right click on it and console)

 

updater.phar

 

Link to comment

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.