Bjonness406

Finally got it working, copied kamhighway's configs in the excact same order then it worked.. Posting my config below /mnt/cache/appdata/Nginx-letsencrypt/nginx/site-confs/default server { listen 80; listen 443 ssl default_server; if ($scheme = http) { return 301 https://xxx.ddns.net$request_uri; } root /config/www; index index.html index.htm index.php; server_name xxx.ddns.net; ssl_certificate /config/keys/fullchain.pem; ssl_certificate_key /config/keys/privkey.pem; ssl_dhparam /config/nginx/dhparams.pem; 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'; ssl_prefer_server_ciphers on; client_max_body_size 0; location / { try_files $uri $uri/ /index.html /index.php?$args =404; } location /nextcloud { include /config/nginx/proxy.conf; proxy_pass https://192.168.1.2:444/nextcloud; } location /request { include /config/nginx/proxy.conf; proxy_pass http://192.168.1.2:3579/request; } } /mnt/cache/appdata/nextcloud/www/nextcloud/config/config.php <?php $CONFIG = array ( 'memcache.local' => '\\OC\\Memcache\\APCu', 'datadirectory' => '/data', 'instanceid' => xxxxxxxxxx', 'passwordsalt' => 'xxxxxxxxxxxxxxxxxxxxxxxxxxxx', 'secret' => 'xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx', 'trusted_domains' => array ( 0 => '192.168.1.2:444', ), 'trusted_proxies' => array ( 0 => '192.168.1.2', ), 'overwritewebroot' => '/nextcloud', 'overwritehost' => 'xxx.ddns.net', 'overwrite.cli.url' => 'https://192.168.1.2:444/nextcloud', 'dbtype' => 'mysql', 'version' => '9.1.0.16', 'dbname' => 'NextCloud', 'dbhost' => '192.168.1.2:3306', 'dbtableprefix' => 'oc_', 'dbuser' => 'oc_xxxxxxxxxx', 'dbpassword' => 'xxxxxxxxxxxxxxxxxxxxxxxxxx', 'logtimezone' => 'UTC', 'installed' => true, 'maintenance' => false, 'loglevel' => 2, 'mail_smtpmode' => 'php', ); "/mnt/cache/appdata/Nginx-letsencrypt/nginx/proxy.conf" and "/mnt/cache/appdata/nextcloud/nginx/site-confs/default" is the same as in OP

You need to be able to pass through a usb device.

+1

And now unifi finally support auto backup

Do you know if the android app detects the installation if you use a "normal" address, like mydomain.net instead of a dyndns address? I use my bought domain name. It like mydomain.de. When I use the the normal Nextcloud container on the 443 Port, the Adress works correctly. So it is not that fault i guess.. Or do think it is? Then I don't think the dynsdns domain is the problem, I thought you had something like "xxx.dyndns.org". I am having some troubles with reverse proxy on the android app too, without reverse proxy it works perfectly fine. I have posted in the nextcloud forum, hope someone could help me there. https://help.nextcloud.com/t/reverse-proxy-with-android-client-does-not-work/3346 If someone is using nextcloud behind reverse proxy (prefer Nginx), does the android client work? If so, can you share your config? Well, I think you might see me up there in previous posts. I eventually did get this one to work with my nginx/letsencrypt reverse proxy as well. So its do-able. Apparently its good to note that Nextcloud recommends that you setup your domain to be "nextcloud.example.com" as opposed to "example.com/nextcloud" Once I found that out, I learned how to add a new server_name to nginx. So my nginx site-confs default file has this appended to the end: server { listen 443 ssl; server_name cloud.example.com; ssl_certificate /config/keys/fullchain.pem; ssl_certificate_key /config/keys/privkey.pem; ssl_dhparam /config/nginx/dhparams.pem; ssl_ciphers 'xxxxxxxxxxxxxxxxxxxxxxxx'; ssl_prefer_server_ciphers on; client_max_body_size 0; location / { proxy_pass https://192.168.1.5:8443; } } And the nextcloud config looks like: $CONFIG = array ( 'memcache.local' => '\\OC\\Memcache\\APCu', 'datadirectory' => '/data', 'instanceid' => 'ocbkgz4h8t5f', 'passwordsalt' => 'xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx', 'secret' => 'xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx', 'trusted_domains' => array ( 0 => '192.168.1.5:8443', 1 => 'example.com:8443', 2 => 'example.com:443', 3 => '192.168.1.5:443', ), 'trusted_proxies' => array ( 0 => '192.168.1.5', 1 => 'example.com', ), 'overwrite.cli.url' => 'https://example.com/nextcloud', 'dbtype' => 'mysql', 'version' => '9.0.53.0', 'dbname' => 'NextCloud', 'dbhost' => '1921.168.1.5:3306', 'dbtableprefix' => 'oc_', 'dbuser' => 'nextcloud', 'dbpassword' => 'xxxxxxxxxxxx', 'logtimezone' => 'UTC', 'installed' => true, 'maintenance' => false, 'appstore.experimental.enabled' => true, ); After all of this, I'm able to get access on the Nextcloud android app with my server set to "https://cloud.example.com" Thanks for sharing the config, but I want to have "mydomain.com/nextcloud" since I am not able to get "cloud.domain.com" (I am using a free address from No-IP). Hmm.. Do you use domain.com/nextcloud or nextcloud.domain.com?

You can expand very easy, just pop in a new drive and the array is expanded (unraid will "clean" the drive before it is accesible, takes some hours, but that happends in the background). I suggest you use 6.2, since then you can have dual parity. Then you can loose 2 disks without any data loss.

What are the differnce between community developer and certified community developer?

I tried it without any success. Here is my default network config: My router is setup to always assign the same ip address to my unRAID server Thanks again for the help! Set Obtain dns server address automatically to "no", and dns server 1 to "8.8.8.8" and dns server 2 to "8.8.4.4" and try again to update your plugins and plex

And that is? Changing emhttp to something else? Or something entirely different?

Time to add some new feature request now? What about a working powerdown now that the powerdown plugin is deprecated? (Not blaming dlandon here, he have done an awsome job with it. Now it is LT time to fix this issue for real!)

You could try to change your dns server to 8.8.8.8 and 8.8.4.4

Storing docker.img on a unassigned device is not support on 6.2

The check for updates button does not work in 6.1.x, you need to click advanced view and then force update. The check for updates button works on 6.2. Thanks but it doesn't seems to do anything. Here is what I obtain Did I missed something? Does not look like it, no idea then. Hopefully someone other can take a look

Do you know if the android app detects the installation if you use a "normal" address, like mydomain.net instead of a dyndns address? I use my bought domain name. It like mydomain.de. When I use the the normal Nextcloud container on the 443 Port, the Adress works correctly. So it is not that fault i guess.. Or do think it is? Then I don't think the dynsdns domain is the problem, I thought you had something like "xxx.dyndns.org". I am having some troubles with reverse proxy on the android app too, without reverse proxy it works perfectly fine. I have posted in the nextcloud forum, hope someone could help me there. https://help.nextcloud.com/t/reverse-proxy-with-android-client-does-not-work/3346 If someone is using nextcloud behind reverse proxy (prefer Nginx), does the android client work? If so, can you share your config?

The check for updates button does not work in 6.1.x, you need to click advanced view and then force update. The check for updates button works on 6.2.

Do you know if the android app detects the installation if you use a "normal" address, like mydomain.net instead of a dyndns address?

Set this up on a new server now just to test. I copied everything you did, just put on my own dns name instead. Now I can access nextcloud from my browser on both the local and external ip/dns name and from the iOS app, but NOT from the android app. I can access nextcloud from the browser on my phone, but not the app. Anyone has any idea? Can someone test if it is the same to you, or if it works for you with the setup in first post.

You can do this on 6.2 What I suggest you do: Update to 6.2 when you can Then delete docker.img and recreate it. Then add all of your previous app via CA "previous apps" tab. OK, pre-clear finished, and 6.2 installed! So far, so good. Do I uninstall the dockers first, or just blow away the docker.img file? Also, I went with the default 10GB .img file, but it seems that 15-20GB is recommended. Can I create the new .img in a larger size & still get everything to install properly? It seems that I should be able to, but I just want to double check. Also - just noticed that there's an update to CA (9/17/2016) should I update that before reinstalling, or leave it on the current version (9/15/2016) for the fix, then update it? Does this mean that I should delete "docker.img" from disk, or does it mean I should go into Settings | Docker, disable docker, save it, then reenable it? http://lime-technology.com/forum/index.php?topic=42148.msg498419.msg#498419 Just make your docker image 15-20GB

You should ask in the support thread instead, bigger chance someone who use it will se your post. Or you can just try it

I'm away for a week from tomorrow so you're on your own... Who is gonna help the poor people in your/LSIO support threads then? Have a great trip or whatever you are going to do

Okey.. I think I am getting to tired for this now... Will take a look at this tomorrow instead. I will set all of this up again tomorrow on my dev server instead, and then see if this works. Will only try with Nginx-letsencrypt that time, and not apache. Hopefully it goes better this time....

Sort out the first issue before starting on the next! And I thought you were using Apache?! I switch between apache and nginx with letsencrypt. I originally did set up apache, but later find out about nginx with letsencrypt so had to try that. Only changes between nginx and apache is the one line in nextcloud, so easy to switch. with apache I can't connect to the local server, and with nginx I can't connect to my phones.. The differnce between them is this line (first post), I keep the "nextcloud/" part it in apache, but remove it in nginx. root /config/www/nextcloud/;

Same here... https://lime-technology.com/forum/index.php?topic=40937.msg481138#msg481138

I think you misunderstand. My server address is "myserver.ddns.net", then I want to have nextcloud at "myserver.ddns.net/nextcloud". The reason I don't have "myserver.net" is because this is a free dns name I got from no-ip, and then is adds the "ddns.net" part after my server name. If there is anything I have missed, please tell me

Thanks for this guide! I got a little problem, this is working fine when I access it from a web browser, but when I try to access the server from my phone with the nextcloud app (android), it does not find the server. Any idea what is causing this?