[Support] Linuxserver.io - Nextcloud


4529 posts in this topic Last Reply

Recommended Posts

  • Replies 4.5k
  • Created
  • Last Reply

Top Posters In This Topic

Top Posters In This Topic

Popular Posts

Application Name: Nextcloud Application Site: https://nextcloud.com/ Docker Hub: https://hub.docker.com/r/linuxserver/nextcloud/ Github: https://github.com/linuxserver/docker-nextcl

Here's my list of instructions....    Use them at your own risk.....   If upgrading to v12 please see here:   ##Turn on maintenance mode docker exec -it nextcloud occ m

Thanks, fixed for me as well, and I also added this line add_header Referrer-Policy no-referrer always; to appdata/nextcloud/nginx/site-confs/default   And now I have a green

Posted Images

On 2/25/2018 at 1:37 PM, gareth_iowc said:

I'm having trouble getting it to update:

 

 

any ideas?

 

thanks

 

Well, I hope those with more knowledge chime in for you, but the last couple times I had that exact same issue, it was because I had inadvertently allowed a file to be created where NC didn't like it.  So, what worked for me was to backup your NC appdata folder, then find that offending file and delete it.  It should allow the upgrade to proceed.

Link to post

I'm having a lot of trouble getting this working in a reverse proxy for me. I am trying to get it working with xxx.duckdns.org/nextcloud. I have tried a few different way that were suggested throughout this forum... right now im at a point where when i type in 192.168.1.18:4433/nextcloud it will access nextcloud without going through the reverse proxy. Although I can  no longer openWebUI through unraid anymore.... If i type in xxx.duckdns.org/nextcloud it just appears to redirect me to the local page and not actually going through the reverse proxy at all. I am fairly new to this and trying to learn as i go so please bare with me. Also my sonarr and couchpotato work properly through the reverse proxy.  

 

 

 

default.txt

config.php

Edited by tazire
Link to post
3 hours ago, killeriq said:

nextcloud is using some port you set..

 

For example 8888 so xxx.duckdns.org:8888 should work or maybe https://xx.duckdns.org:8888 , there shoulnt be anything /nextcloud - it should fill automatically after you hit that url

 I assume you are referring to the nextcloud config. The only line i have that refers to /nextcloud is on line 20

 

  'overwritewebroot' => '/nextcloud',

 

I know removing this will make accessing nextcloud through the unraid webui return. but at the same time its not my main issue. I just cant get the reverse proxy to work at all. I have tried the directions given and it results in my nextcloud being un-accessible through any means.  

 

EDIT

 

Ok little update to this. outside the server it is working 100% as i want it. through letencrypt etc. only issue i have is when i connect while on network. The link I want works. but while on the network it bypasses letsencrypt, i assume that is normal? Also I have to put /nextcloud at the end of the address ie 192.168.1.18:4433/nextcloud. And this is the only way I can access it while on the network. So the unraid webgui doesnt work because of this. 

 

Also my android app wont find the server in the current setup which is an issue. 

Edited by tazire
Link to post

I can no longer upload from my Android devices, getting "server unavailable" error. I have not done anything to the Nextcloud setup or other settings. I can sync through the PC and can get into the WebUI. Where should I start the troubleshooting?

 

Thanks.

Link to post
10 hours ago, levster said:

I can no longer upload from my Android devices, getting "server unavailable" error. I have not done anything to the Nextcloud setup or other settings. I can sync through the PC and can get into the WebUI. Where should I start the troubleshooting?

 

Thanks.

Strange, my IOS app just got same error today. Same symptoms, web works fine, app was working last time I checked a few days ago but now it's timing out.

Link to post
11 hours ago, levster said:

I can no longer upload from my Android devices, getting "server unavailable" error. I have not done anything to the Nextcloud setup or other settings. I can sync through the PC and can get into the WebUI. Where should I start the troubleshooting?

 

Thanks.

I've had the same problem with the Android app for the last few days.

 

The Auto-Upload of images taken with the camera gives the "Server unavailable" message, however images from other apps, e.g. WhatsApp, are uploading fine.

Everything else about the Android app seems fine, can browse, download files, etc. without any problems.

 

The logs don't show any errors at all.

 

The successful uploads show something like the following in the access.log:

172.17.0.1 - aleary [01/Mar/2018:14:12:02 +0000] "GET /index.php/204 HTTP/1.1" 204 0 "-" "Mozilla/5.0 (Android) ownCloud-android/3.0.2"
172.17.0.1 - aleary [01/Mar/2018:14:12:02 +0000] "GET /index.php/204 HTTP/1.1" 204 0 "-" "Mozilla/5.0 (Android) ownCloud-android/3.0.2"
172.17.0.1 - aleary [01/Mar/2018:14:12:09 +0000] "HEAD /remote.php/webdav/InstantUpload/WhatsApp%20Images/ HTTP/1.1" 200 0 "-" "Mozilla/5.0 (Android) Nextcloud-android/3.0.2"
172.17.0.1 - aleary [01/Mar/2018:14:12:09 +0000] "GET /index.php/204 HTTP/1.1" 204 0 "-" "Mozilla/5.0 (Android) ownCloud-android/3.0.2"
172.17.0.1 - aleary [01/Mar/2018:14:12:13 +0000] "PUT /remote.php/webdav/InstantUpload/WhatsApp%20Images/IMG-20180301-WA0000.jpg HTTP/1.1" 201 0 "-" "Mozilla/5.0 (Android) ownCloud-android/3.0.2"
172.17.0.1 - aleary [01/Mar/2018:14:12:14 +0000] "PROPFIND /remote.php/webdav/InstantUpload/WhatsApp%20Images/IMG-20180301-WA0000.jpg HTTP/1.1" 207 867 "-" "Mozilla/5.0 (Android) ownCloud-android/3.0.2"
172.17.0.1 - aleary [01/Mar/2018:14:12:15 +0000] "HEAD /remote.php/webdav/InstantUpload/WhatsApp%20Images/ HTTP/1.1" 200 0 "-" "Mozilla/5.0 (Android) Nextcloud-android/3.0.2"
172.17.0.1 - aleary [01/Mar/2018:14:12:15 +0000] "GET /index.php/204 HTTP/1.1" 204 0 "-" "Mozilla/5.0 (Android) ownCloud-android/3.0.2"
172.17.0.1 - aleary [01/Mar/2018:14:12:15 +0000] "GET /index.php/apps/files/api/v1/thumbnail/256/256/InstantUpload/WhatsApp%20Images/IMG-20180301-WA0000.jpg HTTP/1.1" 200 14287 "-" "Mozilla/5.0 (Android) ownCloud-android/3.0.2"

 

But the failed ones only log a single line:

172.17.0.1 - aleary [02/Mar/2018:15:06:14 +0000] "GET /index.php/204 HTTP/1.1" 204 0 "-" "Mozilla/5.0 (Android) ownCloud-android/3.0.2"

 

Might be a problem in the Android app itself, then doesn't attempt to actually upload.

 

 

Edited by aleary
Link to post
I've had the same problem with the Android app for the last few days.
 
The Auto-Upload of images taken with the camera gives the "Server unavailable" message, however images from other apps, e.g. WhatsApp, are uploading fine.
Everything else about the Android app seems fine, can browse, download files, etc. without any problems.
 
The logs don't show any errors at all.
 
The successful uploads show something like the following in the access.log:
172.17.0.1 - aleary [01/Mar/2018:14:12:02 +0000] "GET /index.php/204 HTTP/1.1" 204 0 "-" "Mozilla/5.0 (Android) ownCloud-android/3.0.2"172.17.0.1 - aleary [01/Mar/2018:14:12:02 +0000] "GET /index.php/204 HTTP/1.1" 204 0 "-" "Mozilla/5.0 (Android) ownCloud-android/3.0.2"172.17.0.1 - aleary [01/Mar/2018:14:12:09 +0000] "HEAD /remote.php/webdav/InstantUpload/WhatsApp%20Images/ HTTP/1.1" 200 0 "-" "Mozilla/5.0 (Android) Nextcloud-android/3.0.2"172.17.0.1 - aleary [01/Mar/2018:14:12:09 +0000] "GET /index.php/204 HTTP/1.1" 204 0 "-" "Mozilla/5.0 (Android) ownCloud-android/3.0.2"172.17.0.1 - aleary [01/Mar/2018:14:12:13 +0000] "PUT /remote.php/webdav/InstantUpload/WhatsApp%20Images/IMG-20180301-WA0000.jpg HTTP/1.1" 201 0 "-" "Mozilla/5.0 (Android) ownCloud-android/3.0.2"172.17.0.1 - aleary [01/Mar/2018:14:12:14 +0000] "PROPFIND /remote.php/webdav/InstantUpload/WhatsApp%20Images/IMG-20180301-WA0000.jpg HTTP/1.1" 207 867 "-" "Mozilla/5.0 (Android) ownCloud-android/3.0.2"172.17.0.1 - aleary [01/Mar/2018:14:12:15 +0000] "HEAD /remote.php/webdav/InstantUpload/WhatsApp%20Images/ HTTP/1.1" 200 0 "-" "Mozilla/5.0 (Android) Nextcloud-android/3.0.2"172.17.0.1 - aleary [01/Mar/2018:14:12:15 +0000] "GET /index.php/204 HTTP/1.1" 204 0 "-" "Mozilla/5.0 (Android) ownCloud-android/3.0.2"172.17.0.1 - aleary [01/Mar/2018:14:12:15 +0000] "GET /index.php/apps/files/api/v1/thumbnail/256/256/InstantUpload/WhatsApp%20Images/IMG-20180301-WA0000.jpg HTTP/1.1" 200 14287 "-" "Mozilla/5.0 (Android) ownCloud-android/3.0.2"

 
But the failed ones only log a single line:

172.17.0.1 - aleary [02/Mar/2018:15:06:14 +0000] "GET /index.php/204 HTTP/1.1" 204 0 "-" "Mozilla/5.0 (Android) ownCloud-android/3.0.2"

 
Might be a problem in the Android app itself, then doesn't attempt to actually upload.
 
 

Looks like the android app was updated on February 27th. Sounds more and more like the app is the problem.

Sent from my SM-G935V using Tapatalk

Link to post

There has been an issue raised re the Android Auto-upload problem. See the following:

 

https://github.com/nextcloud/android/issues/2249

 

It seems the problem is with the creation of the new monthly directory by the Auto-upload process.

i.e. /InstantUpload/Camera/2018/03

 

When the directory doesn't exist in the Nextcloud server, the upload fails.

 

Until a fix is released you can resolve it manually by creating the missing directory and ensuring that you sync the directory to your phone before retrying the upload.

 

The following worked for me:

  • Browse in the Android app, to /InstantUpload/Camera/2018/
  • Create the "03" directory that was missing.
  • Refresh the directory to ensure everything is synced
  • Go to the Uploads section
  • Select the "Retry failed uploads".

All the outstanding uploads then uploaded without error.

Link to post
On ‎1‎/‎03‎/‎2018 at 12:31 AM, tazire said:

 

 

Also my android app wont find the server in the current setup which is an issue. 

FWIW I also had issues with the Android app not connecting.

I loaded the Android beta app and all was good.

 

Link to post
On ‎26‎/‎02‎/‎2018 at 5:37 AM, gareth_iowc said:

I'm having trouble getting it to update:

 

 

any ideas?

 

thanks

I shut down the relevant dockers and used krusader to delete the .rnd file.

 

I was able to restart nextcloud and do the update.

Everything seemed to work ok for me.

 

Edited by Jessie
Link to post
On 1/28/2018 at 4:50 PM, killeriq said:

Did u upgrade from Docker - via NextCloud web UI?

 

I just wonder if i should upgrade like that ...or there is some new Docker version coming with latest Nextcould release?

 

Thanks

Manually like CHBMB said. 

Link to post

Thank you for this!

 

Could you please consider removing these lines from nginx/site-confs/default?

  error_page 403 /core/templates/403.php;
  error_page 404 /core/templates/404.php;

These cause user creation with a weak password to fail silently (the button appears to do nothing) instead of showing an error.

 

See:

https://github.com/nextcloud/server/issues/3847#issuecomment-287740126

https://github.com/nextcloud/server/pull/2004#issuecomment-291007260

 

Thanks!

 

Link to post

I noticed that duckdns is not updating my correct IP address. When I go to the duckdns.org and try to update manually, it tells me that my IP was already xxx.xxx.xxx.xxx (which is actually wrong according to my actual IP as reported by  what's my IP) and not updated. So, how can I "synchronize" my IP?

 

When I restart duckdns I get the following in its log:

 

 



Brought to you by linuxserver.io
We gratefully accept donations at:
https://www.linuxserver.io/donations/
-------------------------------------
GID/UID
-------------------------------------

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

[cont-init.d] 10-adduser: exited 0.
[cont-init.d] 40_config.sh: executing...
Retrieving subdomain and token from the environment variables
log will be output to docker log
/app/duck.conf: line 1:xxxxxtoken_idxxxx: command not found
Something went wrong, please check your settings Fri Mar 9 20:40:27 EST 2018
[cont-init.d] 40_config.sh: exited 0.
[cont-init.d] done.
[services.d] starting services
[services.d] done.

 

PS:

 

I deleted and then re-added the xxxx.duckdns.org names on the duckdns.org website and it correctly picked up the new IP address, allowing the nextcloud to once again work. 

 

Edited by levster
Link to post
On 3/9/2018 at 8:36 PM, levster said:

I noticed that duckdns is not updating my correct IP address. When I go to the duckdns.org and try to update manually, it tells me that my IP was already xxx.xxx.xxx.xxx (which is actually wrong according to my actual IP as reported by  what's my IP) and not updated. So, how can I "synchronize" my IP?

 

When I restart duckdns I get the following in its log:

 

 



Brought to you by linuxserver.io
We gratefully accept donations at:
https://www.linuxserver.io/donations/
-------------------------------------
GID/UID
-------------------------------------

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

[cont-init.d] 10-adduser: exited 0.
[cont-init.d] 40_config.sh: executing...
Retrieving subdomain and token from the environment variables
log will be output to docker log
/app/duck.conf: line 1:xxxxxtoken_idxxxx: command not found
Something went wrong, please check your settings Fri Mar 9 20:40:27 EST 2018
[cont-init.d] 40_config.sh: exited 0.
[cont-init.d] done.
[services.d] starting services
[services.d] done.

 

PS:

 

I deleted and then re-added the xxxx.duckdns.org names on the duckdns.org website and it correctly picked up the new IP address, allowing the nextcloud to once again work. 

 

 

Figured it out. By pasting the token_id, the paste function was actually adding a space in front of the id, thereby invalidating it. 

Link to post

I am having issues with getting Nextcloud working with LetsEncrypt.

 

I have been following this tutorial.

 

I am getting a blank page when i go to mydomain.com/nextcloud (5222) and i get an error when i access my UNRAIDIP:444 (5221)

 

I have attached all of the relevant documents.

 

 

5222.PNG

^5222

 

config php.PNG

^config.php

 

letsencrypt nginx site confs default.png

^ \\SERVER\appdata\letsencrypt\nginx\site-confs\default

 

nextcloud log.PNG

^ nextcloud log

 

nextcloud nginx site confs default.png

^ \\SERVER\appdata\nextcloud\nginx\site-confs\default

 

5221.PNG

^ 5221

Edited by Aurao
Link to post
I am having issues with getting Nextcloud working with LetsEncrypt.
 
I have been following this tutorial.
 
I am getting a blank page when i go to mydomain.com/nextcloud (5222) and i get an error when i access my UNRAIDIP:444 (5221)
 
I have attached all of the relevant documents.
 
 
5222.thumb.PNG.84d1f7ec3201276db4e91341744660f6.PNG
^5222
 
5aa84dbcc4023_configphp.PNG.067627795c55ad9408e1de067c90f4c3.PNG
^config.php
 
5aa84dbd18bd6_letsencryptnginxsiteconfsdefault.png.82665c7b28fdd6a43408150c738cadf1.png
^ \\SERVER\appdata\letsencrypt\nginx\site-confs\default
 
5aa84dbd723d1_nextcloudlog.PNG.e223f54e3c0de9602939018e9a5412c6.PNG
^ nextcloud log
 
5aa84dbdbc053_nextcloudnginxsiteconfsdefault.png.2f49376fc9b57d7d6ed0272c1ccfa24d.png
^ \\SERVER\appdata\nextcloud\nginx\site-confs\default
 
5221.thumb.PNG.bdbfac2411367e9f62381cc6f7cc51df.PNG
^ 5221
I don't support that tutorial. Either follow the tutorial I wrote, linked on the first post of thus thread or get support from Cyanlabs themselves if you follow that tutorial.

Sent from my LG-H815 using Tapatalk

Link to post

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.