both works, either you mount the pathes in nextcloud docker and then they are available to add as local pathes in nextcloud,

or you simply just add your network shares in there ... pretty self explained.

 

all in the external storage plugin, local, SMB, google drive, etc ...

 

for example, i mounted media to nextcloud docker

 

 

then i added this in external storage, here u also specify access and priviledges.

 

 

then in nextcloud its shown as share

 

 

pretty simple and working

6 hours ago, alturismo said:

both works, either you mount the pathes in nextcloud docker and then they are available to add as local pathes in nextcloud,

or you simply just add your network shares in there ... pretty self explained.

 

all in the external storage plugin, local, SMB, google drive, etc ...

 

for example, i mounted media to nextcloud docker

 

 

then i added this in external storage, here u also specify access and priviledges.

 

 

then in nextcloud its shown as share

 

 

pretty simple and working

got it, thank you

7 hours ago, alturismo said:

both works, either you mount the pathes in nextcloud docker and then they are available to add as local pathes in nextcloud,

or you simply just add your network shares in there ... pretty self explained.

 

all in the external storage plugin, local, SMB, google drive, etc ...

 

for example, i mounted media to nextcloud docker

 

 

then i added this in external storage, here u also specify access and priviledges.

 

 

then in nextcloud its shown as share

 

 

pretty simple and working

Im getting a red square and not sure why. Can you see what's wrong with the config? I added a path variable called /music to the docker.

 

Nextcloud is running on its own IP 192.168.1.91:443

UNRAID host is running on 192.168.1.90

 

 

 

Edited December 3, 20178 yr by mikeyosm

5 minutes ago, mikeyosm said:

Im getting a red square and not sure why. Can you see what's wrong with the config? I added a path variable called /music to the docker.

 

Nextcloud is running on its own IP 192.168.1.91:443

UNRAID host is running on 192.168.1.90

 

 

 

avoid empty fields, use dot for Domain, and choose some subfolder too..

3 minutes ago, uldise said:

avoid empty fields, use dot for Domain, and choose some subfolder too..

Not made a difference. Doesn't "." imply localhost? My UNRAID is running on a different IP.

Can you show me your external storage config please?

17 minutes ago, mikeyosm said:

Not made a difference. Doesn't "." imply localhost? My UNRAID is running on a different IP.

Can you show me your external storage config please?

ahh, just looked at my config, i have no value for Domain field. Remove slash for share name, use just "music" ..

and for SMB/CIFS you don't need local folder mapping, just a proper samba share from your unRAID.

Edited December 3, 20178 yr by uldise

When u add in docker, mount as local ... Not as SMB ...

Gesendet von meinem SM-G950F mit Tapatalk

3 minutes ago, alturismo said:

When u add in docker, mount as local ... Not as SMB ...

Gesendet von meinem SM-G950F mit Tapatalk
 

That's it, worked. Thank you

1 hour ago, alturismo said:

When u add in docker, mount as local ... Not as SMB ...

how about disk spinups when using Local vs SMB?

I have some structural issues that prevent me from opening ports on my router.

 

I have been thinking of work-arounds and having a VPS may be a good and safe solution? I got inspired by this article https://jordancrawford.kiwi/home-server-without-portforward/.

 

Would love to get your thoughts whether that's possible with Nextcloud running in an Unraid Docker. If I read this correctly, I may not need letsencrypt in this case, but it would require me to tunnel the Unraid Nextcloud docker to my VPS through some form of VPN?

 

Any thoughts and advice for me?

Hi. When I try to upload files in documents i get a message that says "forbidden" Any clues?

I try to serch for help but could not find anything relevant.

I changed the permissions on my user folder to 777, but no change.

 

Problem was fixed when i changed the entire datafolder to 777.

 

Edit2 ; Problem was only fixed for one user. Deleted the other user.

Edited December 11, 20178 yr by mrvilla

Hi,

 

i was wondering if there was a way to point the nextcloud Docker to a share on my unraid system that it would sync with. 

 

For example if I had a share for documents whenever I uploaded a pdf to this share it would also appear in nextcloud 

 

thank you

5 minutes ago, davidk845 said:

Hi,

 

i was wondering if there was a way to point the nextcloud Docker to a share on my unraid system that it would sync with. 

 

For example if I had a share for documents whenever I uploaded a pdf to this share it would also appear in nextcloud 

 

thank you

 

I replied to your question in dlandon's Owncloud thread

39 minutes ago, CHBMB said:

 

I replied to your question in dlandon's Owncloud thread

Sorry CHBMB that was very helpful thank you very much 

Hi,

 

my Nextcloud data share has always been the only share which only had one specific disk associated with it.

As that disk runs out of space I'm asking myself if there's any downside in simply including all disks now?

Maybe that's not convenient for Nextcloud!?

If it's not an issue, what split level are other people using here?

Hi,

I'm getting notifications that state I need to update the brute-force-settings app to v1.0.3. I went into the apps->security and clicked the update button. All that happened was an "updating" message (state never changed). I refreshed the screen and the button reverted to "Update to 1.0.3", but now also shows "You have 1 app update pending" in a banner across the top of the page. After waiting for an hour without the app updating, I restarted the nextcloud docker. After logging back in, the state was the same (app needs an update and the "pend" message at the top).

 

Is there some secret recipe to get app updates to work (akin to the nextclould update procedure)?

 

I somewhat remember trying to initially install some apps (way back when) and saw the same behavior, so I think this is more a general problem with app install/update rather than specific to this update.

 

I did check a few logs an saw nothing (but I'm no expert - probably looking in the wrong places). I also checked the general file permissions by logging into the docker and found most files were the 'abc' owner and group except for a few files owned by 'root'. I believe this is normal.

 

Any pointers would be most appreciated!

Hello, not sure if I should post it here or the letsencrypt forum, but I followed the guide here and almost got all the steps except getting letsencrypt to work.

 

This is the log file shown in the letsencrypt.

 

Certbot can obtain and install HTTPS/TLS/SSL certificates. By default,
it will attempt to use a webserver both for obtaining and installing the
cert.
certbot: error: argument --cert-path: No such file or directory
Generating new certificate
Saving debug log to /var/log/letsencrypt/letsencrypt.log
Obtaining a new certificate
Performing the following challenges:
tls-sni-01 challenge for www.nextcloud.sevenz.id
Waiting for verification...
Cleaning up challenges
Failed authorization procedure. www.nextcloud.sevenz.id (tls-sni-01): urn:acme:error:unauthorized :: The client lacks sufficient authorization :: Incorrect validation certificate for tls-sni-01 challenge. Requested 649cc8da09ee4b25e364c0cfb83940c9.39736846123211ed6c97ba1fdcec0678.acme.invalid from 66.96.235.118:443. Received 1 certificate(s), first certificate had names "*"
IMPORTANT NOTES:
- The following errors were reported by the server:

Domain: www.nextcloud.sevenz.id
Type: unauthorized
Detail: Incorrect validation certificate for tls-sni-01 challenge.
Requested
649cc8da09ee4b25e364c0cfb83940c9.39736846123211ed6c97ba1fdcec0678.acme.invalid
from 66.96.235.118:443. Received 1 certificate(s), first
certificate had names "*"

To fix these errors, please make sure that your domain name was
entered correctly and the DNS A record(s) for that domain
contain(s) the right IP address.
- Your account credentials have been saved in your Certbot
configuration directory at /etc/letsencrypt. You should make a
secure backup of this folder now. This configuration directory will
also contain certificates and private keys obtained by Certbot so
making regular backups of this folder is ideal.

 

Anything I should do to fix this?

 

That's a Letsencrypt log,@aptalca is the expert

Sent from my LG-H815 using Tapatalk

Ahh sorry, should I post in Letsencrypt instead?

 

EDIT: Nevermind I got it working! Turns out I need to port letsencrypt to 443 and nextcloud to 444, not the other way around!

Edited December 19, 20178 yr by sevenz
fixed

On 12/18/2017 at 9:52 AM, bobe99 said:

Is there some secret recipe to get app updates to work (akin to the nextclould update procedure)?

 

From the silence I take it people are generally not having this issue.

 

Can anyone confirm this is supposed to work with this docker?

 
From the silence I take it people are generally not having this issue.
 
Can anyone confirm this is supposed to work with this docker?

Sorry, I'm a bit time poor nowadays so tend to forget to reply to things when I get a free minute.

No, I have no problems upgrading my apps, but you haven't said what version of Nextcloud you're running?

Sent from my LG-H815 using Tapatalk

UNRAID 6.4 RC17 has broken the docker for me. I run nextcloud on its own IP and now it doesnt have any internet connectivity so I cant access nextcloud from outside my network or even load the nextcloud apps page. Loads of connection problems in the log...

This was all working fine with 6.4 RC15e.

 

Anything I can do within nextcloud to troubleshoot the internet connection? All other dockers that share the UNRAID host IP appear to work fine.

 

 

 

4 hours ago, mikeyosm said:

UNRAID 6.4 RC17 has broken the docker for me. I run nextcloud on its own IP and now it doesnt have any internet connectivity so I cant access nextcloud from outside my network or even load the nextcloud apps page. Loads of connection problems in the log...

This was all working fine with 6.4 RC15e.

 

Anything I can do within nextcloud to troubleshoot the internet connection? All other dockers that share the UNRAID host IP appear to work fine.

 

 

 

Hmm just checked and I think my installation is broken on 17b - just upgraded today.  Will check properly when get home.  My address is nextcloud.domain.com - my other dockers e.g domain.com/sonarr are working

 

Update: False alarm - restarting the docker did the trick

Edited December 22, 20178 yr by DZMM

I have a static IP address, do i still need to purchase a domain?

31 minutes ago, Greygoose said:

I have a static IP address, do i still need to purchase a domain?

No, as long as you're happy using your static ip address instead of a domain name.