[Support] Linuxserver.io - Nextcloud


Recommended Posts

On 3/30/2019 at 10:29 AM, Niklas said:

I looked for clamav in the container first.

The plugin needs clamscan
/usr/bin/clamscan
bash: /usr/bin/clamscan: No such file or directory

Edit:

One solution:

Added this container: https://hub.docker.com/r/mkodockx/docker-clamav/

Configured the plugin in Nextcloud to connect to ClamAV-container using ip and port 3310.

Capture_ServerDocker_-_Google_Chrome_2019-03-30_17-17-59_46260352.png.834e8a7f30db989e038574d660b3eec7.png
 

Capture_Settings_-_nSoft_Cloud_-_Google_Chrome_2019-03-30_17-19-13_37783157.png

 

Capture_Activity_-_nSoft_Cloud_-_Google_Chrome_2019-03-30_17-20-27_26350508.png

 

 

 

@Niklas Could you offer any help on setting up that Clam AV docker? When I install it here is what I end up with:

 

1194254299_ScreenShot2019-10-30at5_08_34PM.thumb.png.3e8f75a399701051f07ba10bf4b300b2.png

 

 

Edited by Smooth Beaver
Link to comment

Hi, hope someone can help! I’ve noticed that whenever anyone downloads a file from Nextcloud my docker image fills up to 100% and then drops back to normal! Is there a buffer somewhere that needs configuration? I’ve looked everywhere I can think of! This is downloading not uploading which is why I find it strange! It’s always from an Unraid share that I have configured through external storage.

cheers,

Tim

Link to comment

Hi - hoping I can get some help. I have been happily running this container for a few years - its awesome. Unfortunately, I recently had some issues with a disk that was failing (it has been replaced and parity rebuilt). During this time I also had to hard down the unraid server once. I ran the parity check after before proceeding with the disk replacement.

 

Now - my nextcloud docker will start, but my clients do not connect (red icon) and when I try to browse to the webpage I get

 

Internal Server Error The server encountered an internal error and was unable to complete your request. Please contact the server administrator if this error reappears multiple times, please include the technical details below in your report. More details can be found in the server log.

If i look at the docker log I see:
 

-------------------------------------
_ ()
| | ___ _ __
| | / __| | | / \
| | \__ \ | | | () |
|_| |___/ |_| \__/


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

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...
chown: changing ownership of '/data': I/O error
[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] 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.

 

I tried running the Docker Safe New Permissions. I am not sure if it actually ever finished (the page errored out after like 12 hours) - but it did not help.

 

My nextcloud share (mapped to /data in the docker) has the following permissions on the share folder, and the folder below (I obfuscated the user folder names):

root@ur01:/mnt/user# ls -al | grep nextCloud
drwxrwx--- 1 nobody users         252 Jan  7  2018 nextCloud/

root@ur01:/mnt/user# ls -al nextCloud/
total 112856
drwxrwx--- 1 nobody users       252 Jan  7  2018 ./
drwxrwxrwx 1 nobody users        48 Nov  4 11:57 ../
-rw-rw-rw- 1 nobody users      4096 Jan 26  2017 ._.DS_Store
-rw-rw-rw- 1 nobody users       324 Oct  8 10:40 .htaccess
-rw-rw-rw- 1 nobody users         0 Jan 26  2017 .ocdata
drwxrwxrwx 1 nobody users        44 Jan 31  2017 admin/
drwxrwxrwx 1 nobody users       115 Aug 21  2018 appdata_ocnuvolb7k5t/
drwxrwxrwx 1 nobody users        96 Apr  5  2018 user1/
drwxrwxrwx 1 nobody users         6 Oct  8 10:40 files_external/
-rw-rw-rw- 1 nobody users         0 Jan 26  2017 index.html
drwxrwxrwx 1 nobody users        96 Jan  7  2018 user2/
-rw-r----- 1 nobody users 110798670 Nov  8 10:00 nextcloud.log
-rw-rw-rw- 1 nobody users    581632 Jan 26  2017 owncloud.db

 

I have also deleted the docker.img file (because of issues on a different docker) and the problem persists.

 

Any idea what i can look at to fix this? Thank you!

Edited by daemian
Link to comment

Re-did my container setup today, with letsencrypt configured finally. I can access my nextcloud via my ddns name, but once I'm on LAN, my phone cannot see the nextcloud server. Anyone run into this issue before, I have Hairpin NAT enabled on my edgerouter, followed Spaceinvaders video on setting both up.

Link to comment
18 minutes ago, Seanraz said:

Re-did my container setup today, with letsencrypt configured finally. I can access my nextcloud via my ddns name, but once I'm on LAN, my phone cannot see the nextcloud server. Anyone run into this issue before, I have Hairpin NAT enabled on my edgerouter, followed Spaceinvaders video on setting both up.

Do you have a static host mapped? I tried that last night with my UniFi stack and yep that's a no go, I cannot access it internally, but you can access it externally, killed the static host map and voila works like it should except traffic is directed out to WAN then back in.... if you figure this out please pass the info down...

Link to comment
35 minutes ago, Smooth Beaver said:

Do you have a static host mapped? I tried that last night with my UniFi stack and yep that's a no go, I cannot access it internally, but you can access it externally, killed the static host map and voila works like it should except traffic is directed out to WAN then back in.... if you figure this out please pass the info down...

Feel dumb, I was connected to my IoT network which has outbound network blocking. What also didn't help was I had accidentally set one of my ports on my switch to the different vlan. After setting it back to my main LAN, everything works.

Link to comment
Feel dumb, I was connected to my IoT network which has outbound network blocking. What also didn't help was I had accidentally set one of my ports on my switch to the different vlan. After setting it back to my main LAN, everything works.

Unrelated but story of my life. Always tinkering with stuff LOL. Is EXACTLY something somehow I’d manage to pull off messin around (sorry I know it’s not FUNNY but I can relate)
Link to comment
Just curios without doing a manual update/upgrade how many of the users have been prompted to NextCloud 17, i just go an update but it went from  16.05 to 16.06

I’ve had 17 for a month now maybe. It prompted one day. I’m on “stable”. It’s been alright; nothing worth writing home about that I’ve noticed.
Link to comment
4 hours ago, Smooth Beaver said:

I received a notification that 17.0.1 is available. Are we supposed to wait for a docker container update or can we use the built in Updater?

 

When I tried to use the updater I get this error:

253334466_ScreenShot2019-11-08at10_54_08PM.thumb.png.e1b09b4dc33dabd20699960679e8a108.png

 

Where exactly is it looking for to find those files so I can remove them..

Update the container first if it's not up to date, then update through the webui. If that fails, go to the first post and go to the link for updating using command line.

  • Like 1
Link to comment
On 11/8/2019 at 3:05 PM, CHBMB said:

Check your /config/nginx/logs/ folder to see what that says.

 

That IO error is a bit concerning, makes me wonder if your appdata has become a bit corrupted.

You were exactly right. Started looking into some other issues I had and there was something wrong with the new disk I inserted. Not sure if my failed disk wrote to corrupted data to parity or what exactly happened but at the end of the day I had to re-format my new disk. Some data was certainly lost - but I will see if I can get anything off the old disk or restore from backups. The good news is my stuff is working again.

 

Thanks anyhow!

  • Like 1
Link to comment
On 11/8/2019 at 9:17 PM, ijuarez said:

Just curios without doing a manual update/upgrade how many of the users have been prompted to NextCloud 17, i just go an update but it went from  16.05 to 16.06

I had the same thing happen. I'm not really sure why some people are prompted to go to 16.06 and some to 17.... it's strange. 

Link to comment
On 11/4/2019 at 11:11 AM, Ustrombase said:

Does anyone have redis installed?

I do, and only have the connection port set in dockerMAN. These are the settings I added to the Nextcloud config.php:

 

  'filelocking.enabled' => 'true',
  'memcache.locking' => '\\OC\\Memcache\\Redis',
  'redis' =>
  array (
    'host' => '10.66.0.10',
    'port' => 6379,
    'timeout' => 0.0,
  ),

 

Link to comment

So I updated from 16.04 to 16.06 and got an issue.

Everything seemed like normal except I could not share with link from stuff that is external storage.
Found out the allow share setting was turned off after the update, so I tried to activate it again.
But no, error symbol but it does not tell me what the error is!
Then I tried to remove it to then add it again, but I cant add it again because the same thing happens! It just shows an red ! but doesnt say why! its exactly how it was when it worked before the update....

holding over the ! doesnt showing it, clicking on it doesnt show anything! Anyone know why?
In worst case, can I revert back to 16.04?

Nextcloud cant add exsternal.png

Link to comment

My Nextcloud server has a update from 17.0.0 to 17.0.1. Tried to auto update inside Nextcloud and it failed to make a backup for some reason. At any rate, can anyone confirm update instructions linked in OP are still relevant and functional in 17 before I cause myself a mess lol? Don’t think anything would’ve changed as far as updating container but I’d rather ask and be safe over sorry...

Link to comment
11 hours ago, blaine07 said:

My Nextcloud server has a update from 17.0.0 to 17.0.1. Tried to auto update inside Nextcloud and it failed to make a backup for some reason. At any rate, can anyone confirm update instructions linked in OP are still relevant and functional in 17 before I cause myself a mess lol? Don’t think anything would’ve changed as far as updating container but I’d rather ask and be safe over sorry...

Worked fine for me two days ago.

  • Like 1
Link to comment
On 11/11/2019 at 9:39 PM, xthursdayx said:

I do, and only have the connection port set in dockerMAN. These are the settings I added to the Nextcloud config.php:

 


  'filelocking.enabled' => 'true',
  'memcache.locking' => '\\OC\\Memcache\\Redis',
  'redis' =>
  array (
    'host' => '10.66.0.10',
    'port' => 6379,
    'timeout' => 0.0,
  ),

 

What do you mean port set to dockerMan? Secondly, how do you know if there is improvement by using redis? What would be noticeable?

Edited by Ustrombase
additional question
Link to comment

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.