1 hour ago, mrvilla said:

After update to 6.4 my Nextcloud docker will not start up. Got an error saying server error:(

 

Any ideas?

 

 

 

 

You need to read the release notes before you do an upgrade 

Unraid now uses port 443 for https, and you have nextcloud using 443 I guess. Change one of them and it should work.

18 hours ago, saarg said:

 

You need to read the release notes before you do an upgrade 

Unraid now uses port 443 for https, and you have nextcloud using 443 I guess. Change one of them and it should work.

I read through the release notes and saw the https implementation. Just didnt notice the port it was using

 

Have changed the https port now and it is ok. Thanks for your help!

I have done as stated above with the port change but now i have to specify the port when i want to connect to the nextcloud. essentially where xxx.duckdns.org used to work to connect I now have to put in xxx.duckdns.org:12345 in order to connect to the nextcloud... I'm guessing this isnt actually a nextcloud issue and something I can fix with my duckdns?

How can I access this without HTTPS? I am only running it on my local netowork, and im trying to integrate Collabora and im getting cert errors.

49 minutes ago, relink said:

How can I access this without HTTPS? I am only running it on my local netowork, and im trying to integrate Collabora and im getting cert errors.

 

You'll need to edit the nginx config in /config.

On 27/12/2017 at 10:47 PM, kostecki said:

I've been using the container for a days now, and it seems to work perfectly. Thanks for hard work!

 

I really want to add Dropbox synchronization to Nextcloud, but after Dropbox deprecated OAuth1 in favor of OAuth2 it requires a different app: https://github.com/icewind1991/files_external_dropbox is it possible to add it to the container in some way?

 

Just shamelessly quoting myself in hope of an answer 

5 minutes ago, kostecki said:

 

Just shamelessly quoting myself in hope of an answer 

 

No, that looks like a plugin to Nextcloud, not something we add to the container, but something installed by the end user.

4 hours ago, CHBMB said:

 

No, that looks like a plugin to Nextcloud, not something we add to the container, but something installed by the end user.

That absolutely fair, and i understand but seeing as it requires me to download from source, build the plugin and enable it using the OCC i'm guessing it's as good as useless, unless i want to jump through all of these hoops everything the container is updated, right?

1 minute ago, kostecki said:

That absolutely fair, and i understand but seeing as it requires me to download from source, build the plugin and enable it using the OCC i'm guessing it's as good as useless, unless i want to jump through all of these hoops everything the container is updated, right?

 

Wrong, if you read the instructions you make the plugin in the apps directory, which is in /config/www/nextcloud/ so outside of the container and would be persistent.

 

You would need to install the dependencies to compile it the first time and install them again if you upgraded the container AND needed to recompile.

anyone update unraid to 6.4.0? I did and now my nextcloud docker container will not load at all. 

8 hours ago, M4ST3R-OWNER said:

anyone update unraid to 6.4.0? I did and now my nextcloud docker container will not load at all. 

I had issues with letsencrypt not starting.

This is because unraid now uses it.

 

For the short term, I disabled ssl in unraid and changed port 443 to 4433.

This allowed the letsencrypt docker to start again.

 

In the long term, I assume we will need to connect the nextcloud etc dockers to the builtin Unraid letsencrypt.

 

Haven't worked that bit out yet.  So system is working as per 6.35 for the time being.

 

2 hours ago, Jessie said:

I had issues with letsencrypt not starting.

This is because unraid now uses it.

 

For the short term, I disabled ssl in unraid and changed port 443 to 4433.

This allowed the letsencrypt docker to start again.

 

In the long term, I assume we will need to connect the nextcloud etc dockers to the builtin Unraid letsencrypt.

 

Haven't worked that bit out yet.  So system is working as per 6.35 for the time being.

 

 

No, in the long term you need to do what you've just done.  Unraid won't fetch SSL certs for your custom domain name like our container.

On 16/01/2018 at 6:53 PM, tazire said:

I have done as stated above with the port change but now i have to specify the port when i want to connect to the nextcloud. essentially where xxx.duckdns.org used to work to connect I now have to put in xxx.duckdns.org:12345 in order to connect to the nextcloud... I'm guessing this isnt actually a nextcloud issue and something I can fix with my duckdns?

 

No, duckdns uses port 80 or 443, depending on if you use http or https the port is automatically selected.  What you've done is changed the Nextcloud port so now you need to select it.  A better strategy would have been to change the Unraid SSL port from 443 to something else and leave Nextcloud on 443.  I'm assuming you're not using a reverse proxy?

10 hours ago, M4ST3R-OWNER said:

anyone update unraid to 6.4.0? I did and now my nextcloud docker container will not load at all. 

 

See the posts above and below yours.

22 hours ago, CHBMB said:

 

No, in the long term you need to do what you've just done.  Unraid won't fetch SSL certs for your custom domain name like our container.

Might have to do it the other way around then?

ie incorporate Unraid into the letsencrypt docker?

 

8 hours ago, Jessie said:

Might have to do it the other way around then?

ie incorporate Unraid into the letsencrypt docker?

 

 

I don't think that's going to work too well.  Best plan is to just use different ports.

Tried to install letsencrypt in order to get rid of the pesky warnings but the nextcloud did not want to start wen done.

Since I was afraid to mess to much with it I just removed letsencrypt and set the config file in nextcloud back to original form.

Everything is working again now.

 

But I would like to ask a few questions before I try again. I hate half guessing while doing something like this. 

At the moment I'm running Nextcloud on 443.

My config file looks like this:

 

<?php
$CONFIG = array (
  'memcache.local' => '\\OC\\Memcache\\APCu',
  'datadirectory' => '/data',
  'instanceid' => 'ocdom0nknjo5',
  'passwordsalt' => 'ssdsdsdsd',
  'secret' => 'sdsddssd',
  'trusted_domains' => 
  array (
    0 => '192.168.0.100',
    1 => 'mydomain',
  ),
  'overwrite.cli.url' => 'https://192.168.0.100',
  'dbtype' => 'mysql',
  'version' => '12.0.4.3',
  'dbname' => 'nextcloud',
  'dbhost' => '192.168.0.100:3306',
  'dbport' => '',
  'dbtableprefix' => 'oc_',
  'dbuser' => 'MrVilla',
  'dbpassword' => 'mypassword',
  'installed' => true,
);
 

 

I install letsencrypt on 442 

 

I make a nextcloud file in letsencrypt to this:

server {  
    listen 442 ssl;
    server_name mydomain;

    root /config/www;
    index index.html index.htm index.php;

    ###SSL Certificates
    ssl_certificate /config/keys/letsencrypt/fullchain.pem;
    ssl_certificate_key /config/keys/letsencrypt/privkey.pem;

    ###Diffie–Hellman key exchange ###
    ssl_dhparam /config/nginx/dhparams.pem;

    ###SSL Ciphers
    ssl_ciphers 'ECDHE-RSA-AES128-GCM-SHA256:ECDHE-ECDSA-AES128-GCM-SHA256:ECDHE-RSA-AES256-GCM-SHA384:ECDHE-ECDSA-AES256-GCM-SHA384:DHE-RSA-AES128-GCM-SHA256:DHE-DSS-AES128-GCM-SHA256:kEDH+AESGCM:ECDHE-RSA-AES128-SHA256:ECDHE-ECDSA-AES128-SHA256:ECDHE-RSA-AES128-SHA:ECDHE-ECDSA-AES128-SHA:ECDHE-RSA-AES256-SHA384:ECDHE-ECDSA-AES256-SHA384:ECDHE-RSA-AES256-SHA:ECDHE-ECDSA-AES256-SHA:DHE-RSA-AES128-SHA256:DHE-RSA-AES128-SHA:DHE-DSS-AES128-SHA256:DHE-RSA-AES256-SHA256:DHE-DSS-AES256-SHA:DHE-RSA-AES256-SHA:AES128-GCM-SHA256:AES256-GCM-SHA384:AES128-SHA256:AES256-SHA256:AES128-SHA:AES256-SHA:AES:CAMELLIA:DES-CBC3-SHA:!aNULL:!eNULL:!EXPORT:!DES:!RC4:!MD5:!PSK:!aECDH:!EDH-DSS-DES-CBC3-SHA:!EDH-RSA-DES-CBC3-SHA:!KRB5-DES-CBC3-SHA';

    ###Extra Settings###
    ssl_prefer_server_ciphers on;
    ssl_session_cache shared:SSL:10m;

        ### Add HTTP Strict Transport Security ###
    add_header Strict-Transport-Security "max-age=63072000; includeSubdomains";
    add_header Front-End-Https on;

    client_max_body_size 0;

    location / {
        proxy_pass https://192.168.0.100:442/; (I have here changed the IP to my server IP. 192.168.0.1 is my routers IP.
        proxy_max_temp_file_size 2048m;
        include /config/nginx/proxy.conf;
    }
}

 

I change nextcloud config to this:

<?php
$CONFIG = array (
  'memcache.local' => '\\OC\\Memcache\\APCu',
  'datadirectory' => '/data',
  'instanceid' => 'ocdom0nknjo5',
  'passwordsalt' => 'ssdsdsdsd',
  'secret' => 'sdsddssd',
  'trusted_domains' => 
  array (
    0 => '192.168.0.100:442', (still using mye servers IP)
    1 => 'mydomain',
  ),
  'overwrite.cli.url' => 'https://mydomain' ,

  'overwritehost' => 'mydomain' ,

  'overwriteprotocol' => 'https' ,
  'dbtype' => 'mysql',
  'version' => '12.0.4.3',
  'dbname' => 'nextcloud',
  'dbhost' => '192.168.0.100:3306',
  'dbport' => '',
  'dbtableprefix' => 'oc_',
  'dbuser' => 'MrVilla',
  'dbpassword' => 'mypassword',
  'installed' => true,
);

 

 

Am i getting something right here?

 

EDIT: Messed up on the ports. Corrected now. Unraid SSL is moved to 444

Edited January 22, 20188 yr by mrvilla

On 21/01/2018 at 12:54 PM, CHBMB said:

 

No, duckdns uses port 80 or 443, depending on if you use http or https the port is automatically selected.  What you've done is changed the Nextcloud port so now you need to select it.  A better strategy would have been to change the Unraid SSL port from 443 to something else and leave Nextcloud on 443.  I'm assuming you're not using a reverse proxy?

 

You're right im not. I was having issues getting it up and running correctly for me. I got it going with the intention of getting back to it. I just havent sat down to do it yet. I changed my unraid port for https but nextcloud still wont start... 

32 minutes ago, tazire said:

 

You're right im not. I was having issues getting it up and running correctly for me. I got it going with the intention of getting back to it. I just havent sat down to do it yet. I changed my unraid port for https but nextcloud still wont start... 

 

Unless you post your docker run command and some logs I'm shooting in the dark to be honest...

3 hours ago, CHBMB said:

 

Unless you post your docker run command and some logs I'm shooting in the dark to be honest...

 

No need right after this i went and double checked the https port for unraid and i dunno what i had done before but the assigned port never took and defaulted back to 443. i reassigned it and all is back to normal for now.

 

I will be trying to set up the reverse proxy again soon now that ive been reminded.

Has anyone gotten CardDav sync to work with MacOS? It's the one thing I've never been able to get to work. Sometimes MacOS will take the carddav address but nothing ever syncs. iOS is always fine.

I have deleted Folders outside of nextcloud, deleting them from Mapped network drive....

 

The files are gone, however nextcloud still sees the folders.

 

How do i rescan the nextcloud datatbase, im using mariaDB

On 20/1/2018 at 11:09 PM, CHBMB said:

 

Wrong, if you read the instructions you make the plugin in the apps directory, which is in /config/www/nextcloud/ so outside of the container and would be persistent.

 

You would need to install the dependencies to compile it the first time and install them again if you upgraded the container AND needed to recompile.

 

You're absolutely right - of course you are. I had to jump through a million hoops, but i have it installed and it works perfectly at bridging Dropbox and Nextcloud.

Thanks for proving me wrong!

20 hours ago, Greygoose said:

I have deleted Folders outside of nextcloud, deleting them from Mapped network drive....

 

The files are gone, however nextcloud still sees the folders.

 

How do i rescan the nextcloud datatbase, im using mariaDB

 

By using the occ terminal command.

You'll need to research what exactly to do, should be in the online Nextcloud server admin manual.

docker exec -it nextcloud bash
cd /config/www/nextcloud/
sudo -u abc php7 occ WHATEVER COMMAND IT IS YOU NEED TO RUN

***update - apparently my upgrade did not go well. I copied all of the 12.0.5 files over my existing (the new signer certs were missing completely) and now I'm back in business. 

 

I am suddenly getting a "too many redirects" error after login when visiting my instance. I recently upgraded to 12.05 and use LetsEncrypt as a reverse proxy. Any ideas as to what could cause this error?

 

I have the same issue when I disable overwrite.cli.url and overwrite host and access the domain locally without my external LetsEncrypt reverse proxy. 

 

 

Edited January 28, 20188 yr by Kash76