11 hours ago, ZombieHedgehog said:

 

Neither version 21.0.3 or 22.0 fixed the issue, getting a ERR_CONNECTION_CLOSED webpage error.

 

Do the logfiles say anything? And are you able to open console of nextcloud docker? In my case the console wouldn't even open.

4 hours ago, JdeJong said:

Do the logfiles say anything? And are you able to open console of nextcloud docker? In my case the console wouldn't even open.

 

Logs appear to be normal, it seems like nextcloud is running but is disconnected from the network

 

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] 90-custom-folders: executing...
[cont-init.d] 90-custom-folders: 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.
[cont-init.d] 70-aliases: exited 0.
[cont-init.d] 90-custom-folders: executing...
[cont-init.d] 90-custom-folders: 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.

On 7/19/2021 at 2:37 PM, skois said:

For anyone wondering.. Collabora stil haven't fixed this, there was some commits that MIGHT be related to this bug, but there is NOT any new images build yet so I can test.
Stick for 6.4.9.3 for now

I am not sure if I am reading it correctly, but I think this means they fixed it and it should be incorporated with the next update (6.4.10.6?)

https://github.com/CollaboraOnline/online/pull/2931

I am not sure if I am reading it correctly, but I think this means they fixed it and it should be incorporated with the next update (6.4.10.6?)
https://github.com/CollaboraOnline/online/pull/2931

If this was indeed the problem, yes 10.6 should have this included

Sent from my Mi 10 Pro using Tapatalk

Dear all,

I am having issue of maintenance in log of nextcloud docker. this happen when I restarted the server. 

this is blocking the GUI and I cannot access next cloud login page. the screen shot is attached. 

any help is much appreciated!

Kind regards,

 

there is prolly a reason why its in maintenance mode, you can try edit the config.php

 

located at \\yourserver\appdata\nextcloud\www\nextcloud\config

 

  'maintenance' => false,
 

but may rethink what you done so it is currently in maintenance ...

I have issues getting my upload speed to my NC server maxxed when accessing both through webbrowser as through the desktop app. When I test on LAN everything is 80-90 MB/s no issues.

 

However when I then turn on SWAG and use the WAN access the desktop app runs at round 70-90 MB/s. I do see it pause a lot, probably because of the chunking. When I use the webbrowser I get 80-90 MB/s download, but upload is only 20 MB/s. So it seems something is wrong with my nginx configs, but I have no idea what it could be. Already looked at some optimizations, but none seem to fix it. Doesn't help that I don't understand the relationship between SWAG and NC's own NGINX files (nginx.conf and default).

 

Anyone has any clue what it could be?

On 7/20/2021 at 8:37 AM, VozDeOuro said:

can't change my domain name to my new one
if i put the new domain name on the config i got this error
any one knows something ?

 

I fixed my error. It was actually due to the domain name from SWAG (previously letsencript). Logs were throwing the error: "nginx: [emerg] "proxy_redirect" directive is duplicate in /config/nginx/proxy-confs/youtube-dl.subfolder.conf:22", which was solved by deleting that file. I guess SWAG was not even starting because of that error so custom domain names do not work. 

 

Hopefully this helps someone.

Hello,

 

i am Struggling to get a new version of Nextcloud installed with MariaDB on Unraid. i have done this in the past without issue. i am setting up a new unraid server and am getting an issue while trying to get through the initial Nextcloud setup with setting admin user/MariaDB settings it keeps timing out. if i try to restart the nextcloud container it will startup in the initial setup page again but errors when i try to proceed saying the user account already exists. 

 

Unraid Version 6.9.2

Nextcloud Docker Tag being used - linuxserver/nextcloud

MariaDB  Docker Tag being used - linuxserver/mariadb

 

Thanks,

if its a complete fresh setup, may try removing the existing nextcloud database from mariadb or create a new database or create a new user in the existing one (you can delete the old one and rename the new existing one then).

 

i would recommend step 1 or 2, who knows what you have in your existing one ...

On 7/22/2021 at 7:54 PM, ejf513 said:

I am not sure if I am reading it correctly, but I think this means they fixed it and it should be incorporated with the next update (6.4.10.6?)

https://github.com/CollaboraOnline/online/pull/2931

6.4.10.6 is released! It's working for me!

Confirmed! 

6.4.10.6 is released! It's working for me!

So it’s safe to remove “collabora/code:6.4.9.3” and go back to “collabora/code”?

Thanks a ton mate!

So it’s safe to remove “collabora/code:6.4.9.3” and go back to “collabora/code”?

Thanks a ton mate!

Yes

Sent from my Mi 10 Pro using Tapatalk

Yes

Sent from my Mi 10 Pro using Tapatalk

Doesn’t appear to be working here unless I’ve broken something else. Just restarted Nextcloud and Collabora so will try again in a sec. just sits on connecting.

Doesn’t appear to be working here unless I’ve broken something else. Just restarted Nextcloud and Collabora so will try again in a sec. just sits on connecting.

Use :6.4.10.6
Just in case it used a cached image.


Sent from my Mi 10 Pro using Tapatalk

Use :6.4.10.6
Just in case it used a cached image.


Sent from my Mi 10 Pro using Tapatalk

Will try in AM. On my way to bed at current. Maybe I broke something else; albeit I haven’t been muckin in things LOL

Thank you, Skois

Use :6.4.10.6
Just in case it used a cached image.


Sent from my Mi 10 Pro using Tapatalk

Downgrade 6.4.9.3 and instantly works… log last night makes me wonder if it isn’t something with certificate verification box? Never had issue 6.4.9.3 before though or had to toggle that [emoji51]

I can’t get 6.4.10.6 to work though

Downgrade 6.4.9.3 and instantly works… log last night makes me wonder if it isn’t something with certificate verification box? Never had issue 6.4.9.3 before though or had to toggle that [emoji51]

I can’t get 6.4.10.6 to work though

Hmm try with incognito, maybe something in cache?
For me works very good, it's even faster

Sent from my Mi 10 Pro using Tapatalk

Hmm try with incognito, maybe something in cache?
For me works very good, it's even faster

Sent from my Mi 10 Pro using Tapatalk

Played with it more; still no dice [emoji22]. I’m sure it’s fail on my part just don’t know what

6 minutes ago, blaine07 said:

Played with it more; still no dice . I’m sure it’s fail on my part just don’t know what

I don't know what else might be  Maybe it's worth posting a bug report on Collabora's github.

Hi everyone,

i need your help

I'm on NextCloud 21.0.3

and, of course, i've these messeges:

 

 

this is my DEFAULT file:

 

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.

    add_header X-Content-Type-Options nosniff;
    add_header X-XSS-Protection "1; mode=block";
    add_header X-Robots-Tag none;
    add_header X-Download-Options noopen;
    add_header X-Frame-Options "SAMEORIGIN";
    add_header X-Permitted-Cross-Domain-Policies none;
    add_header Referrer-Policy no-referrer;
    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;
    location = /robots.txt {
        allow all;
        log_not_found off;
        access_log off;
    }
    location = /.well-known/carddav {
      return 301 $scheme://$host:444/remote.php/dav;
    }
    location = /.well-known/caldav {
      return 301 $scheme://$host:444/remote.php/dav;
    }
    location = /.well-known/webfinger {
      return 301 $scheme://$host:444/public.php?service=webfinger;
    }
    location = /.well-known/host-meta {
      return 301 $scheme://$host:444/public.php?service=host-meta;
    }
    location = /.well-known/host-meta.json {
      return 301 $scheme://$host:444/public.php?service=host-meta-json;
    }
    client_max_body_size 10G;
    fastcgi_buffers 64 4K;
    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;
    location / {
        rewrite ^ /index.php;
    }
    location ~ ^\/(?:build|tests|config|lib|3rdparty|templates|data)\/ {
        deny all;
    }
    location ~ ^\/(?:\.|autotest|occ|issue|indie|db_|console) {
        deny all;
    }
    location ~ ^\/(?:index|remote|public|cron|core\/ajax\/update|status|ocs\/v[12]|updater\/.+|oc[ms]-provider\/.+|.+\/richdocumentscode\/proxy)\.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;
        fastcgi_param front_controller_active true;
        fastcgi_pass php-handler;
        fastcgi_intercept_errors on;
        fastcgi_request_buffering off;
    }
    location ~ ^\/(?:updater|oc[ms]-provider)(?:$|\/) {
        try_files $uri/ =404;
        index index.php;
    }
    location ~ \.(?:css|js|woff2?|svg|gif|map)$ {
        try_files $uri /index.php$request_uri;
        add_header Cache-Control "public, max-age=15778463";
        # 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.
        add_header X-Content-Type-Options nosniff;
        add_header X-XSS-Protection "1; mode=block";
        add_header X-Robots-Tag none;
        add_header X-Download-Options noopen;
        add_header X-Frame-Options "SAMEORIGIN";
        add_header X-Permitted-Cross-Domain-Policies none;
        add_header Referrer-Policy no-referrer;
        access_log off;
    }
    location ~ \.(?:png|html|ttf|ico|jpg|jpeg|bcmap|mp4|webm)$ {
        try_files $uri /index.php$request_uri;
        access_log off;
    }
}

 

What i must do/modify to make this messages disappear?

 

i have already tried to add this but it doesn't work:

 

location ^~ /.well-known {

       location = /.well-known/carddav { return 301 /remote.php/dav/; }

       location = /.well-known/caldav { return 301 /remote.php/dav/; }

       location = /.well-known/webfinger { return 301 /index.php$uri; }

       location ^~ /.well-known { return 301 /index.php$uri; }

 

       try_files $uri $uri/ =404;

       }

 

Thanks in advance to anyone who wants to help me!

 

Zippi

 

For anyone that has the problem with the nextcloudlog file that spinns up the drives:

 

i could not get it to work with the PHP

Hi guys,

 

i performed an updated from v21.0.3 to v22.1.0 RC1 and when i wanted to finish the update with the web based updater, i got this message and i can't access NC anymore. Does anybody have an idea?

 

 

44 minutes ago, parazit said:

Hi guys,

 

i performed an updated from v21.0.3 to v22.1.0 RC1 and when i wanted to finish the update with the web based updater, i got this message and i can't access NC anymore. Does anybody have an idea?

 

 

Most of the time this error comes because of a broken or not started database.
Start there