[Support] Linuxserver.io - Nextcloud


Recommended Posts

Quote

root@VenturaNas:~# docker exec -it nextcloud updater.phar  
Nextcloud Updater - version: v20.0.0beta4-11-g68fa0d4

Current version is 21.0.5.

Update to Nextcloud 21.0.9 available. (channel: "stable")
Following file will be downloaded automatically: https://download.nextcloud.com/server/releases/nextcloud-21.0.9.zip
Open changelog ↗

Steps that will be executed:
[ ] Check for expected files
[ ] Check for write permissions
[ ] Create backup
[ ] Downloading
[ ] Verify integrity
[ ] Extracting
[ ] Enable maintenance mode
[ ] Replace entry points
[ ] Delete old files
[ ] Move new files in place
[ ] Done

Start update? [y/N] y

Info: Pressing Ctrl-C will finish the currently running step and then stops the updater.

[✔] Check for expected files
[✔] Check for write permissions
[ ] Create backup ...PHP Warning:  copy(/data/updater-oc9q1ejvugli/backups/nextcloud-21.0.5.1-1645524247/apps/mail/l10n/ca.js): failed to open stream: No error information in phar:///config/www/nextcloud/updater/updater.phar/lib/Updater.php on line 395
[✘] Create backup failed
Could not copy "/config/www/nextcloud/apps/mail/l10n/ca.js" to "/data/updater-oc9q1ejvugli/backups/nextcloud-21.0.5.1-1645524247/apps/mail/l10n/ca.js". Destination /data/updater-oc9q1ejvugli/backups/nextcloud-21.0.5.1-1645524247/apps/mail/l10n/ca.js is not writable                                                   
                                   

Update failed. To resume or retry just execute the updater again.
root@VenturaNas:~# docker exec -it nextcloud updater.phar  
Nextcloud Updater - version: v20.0.0beta4-11-g68fa0d4

Current version is 21.0.5.

Update to Nextcloud 21.0.9 available. (channel: "stable")
Following file will be downloaded automatically: https://download.nextcloud.com/server/releases/nextcloud-21.0.9.zip
Open changelog ↗

Steps that will be executed:
[ ] Check for expected files
[ ] Check for write permissions
[ ] Create backup
[ ] Downloading
[ ] Verify integrity
[ ] Extracting
[ ] Enable maintenance mode
[ ] Replace entry points
[ ] Delete old files
[ ] Move new files in place
[ ] Done

Start update? [y/N] y

Info: Pressing Ctrl-C will finish the currently running step and then stops the updater.

[ ] Check for expected files ...PHP Warning:  mkdir(): I/O error in phar:///config/www/nextcloud/updater/updater.phar/lib/Updater.php on line 997
[✘] Check for expected files failed
Could not create $updaterDir

Update failed. To resume or retry just execute the updater again.

 


I'm having this problem.

tried everything

Link to comment
On 2/22/2022 at 12:12 AM, shpitz461 said:

Did you try in incognito mode? Also try to clear cookies and re-try.

 

Yes I have tried different pc's different browsers and still nothing. Also noticed my auto uploads from my phone have stopped working. I did post in mariadb about a warning I was getting in relation to a mysql upgrade but having done that the problem still persists with nextcloud! no warnings in logs either which is making it a real pain to try diagnose. 

Link to comment

Does anyone have any suggestions on what logs to look at to troubleshoot upload issues?  I seem to be running into issues uploading larger files (2GB is what I'm currently testing with) and receive a "Cannot upload...." message when I try using a folder shared as a File Drop (upload only).  When I set the folder to "Allow upload and editing", I receive a "An unknown error has occurred" message.  I am running NextCloud and Swag.

 

NextCloud v23.0.2

  • The UI under System shows PHP Upload Max Size as 100GB
  • NextCloud's nginx.conf file has client_max_body_size set to 0 (disabled)
  • Swag's nginx.conf file has client_max_body_size set to 0 (disabled)
  • Swag's nextcloud.subdomain.conf file has client_max_body_size set to 0 (disabled)

I've turned the logging value to 1 (0 was just impossible to find anything) and do not see anything in both the UI Logs area or the nextcloud.log file.  I don't see any logs in var/logs/nginx or var/logs/php.

Link to comment
1 hour ago, gacpac said:

It's been answered couple times in the forum, you'll probably have to scroll back

Sent from my Pixel 6 Pro using Tapatalk
 

 

I've searched for every term I can think of in this thread and across other sites and everything I'm finding leads back to changing stuff I mentioned above.  I did just find something about changing a user.ini file but that didn't help either.  If you know of a resolution somewhere in this thread, please link me to it when you get the chance.

I did do some more testing and found that it's failing on files over 500ish MB (through Google Chrome).  So while it looks like I've taken a lot of steps to increase this, I'm still missing something somewhere.  Back through the documentation I go.

Link to comment

Oh boy, hold in let me look up my history. But long story short it comes down to the swag container, they fixed it in future updates in the container but you have to delete the files in order to pull the new ones with the correct codes. 

 

Link to comment
14 minutes ago, gacpac said:

Oh boy, hold in let me look up my history. But long story short it comes down to the swag container, they fixed it in future updates in the container but you have to delete the files in order to pull the new ones with the correct codes. 

 

 

Hmm...I found this thread which sounds like what you stated but am unsure which nginx.conf file(s) I should be deleting.

https://github.com/linuxserver/docker-swag/issues/91

I tried deleting (just renamed) both nginx.conf files in Swag (/defaults/) and NextCloud (/defaults/) and restarted both containers but neither of them have recreated.

Link to comment
13 hours ago, gacpac said:

Oh boy, hold in let me look up my history. But long story short it comes down to the swag container, they fixed it in future updates in the container but you have to delete the files in order to pull the new ones with the correct codes. 

 

 

I renamed the nginx.conf file in Swag (/etc/nginx/) and restarted Swag and it looks like it downloaded a new copy as it had an older date.  I updated the client_max_body_size set to 0, restarted again, and I was able to upload larger files when logged in as the user.

 

I went back to my original test scenario and tried uploading a 500MB test file via a File Drop link and after almost a minute, I received a "Connection to server lost" message.  I changed the folder to have "Allow update and editing" permissions and tried again and received the same error message but this time it took about 1:30.  Looks like I have something new to look into.

Link to comment

Hi I just installed this Docker along with Mariadb and Swag, exactly as per Space Invader One's video, and everything is working fine. I'm brand new to Unraid and Dockers, so I followed every step very carefully.

 

My problem is that there seems to be an upload size limit. Files over 1GB are not uploaded and my Mac desktop app shows the error "Server replied "413 Request Entity Too Larg..."

 

I have searched this thread and the web without finding a clear resolution that I can understand. Are there some clear instructions to increase the max file size somewhere?

 

Thanks!

Screen Shot 2022-02-24 at 7.17.09 PM.png

Link to comment
42 minutes ago, malebron said:

Hi I just installed this Docker along with Mariadb and Swag, exactly as per Space Invader One's video, and everything is working fine. I'm brand new to Unraid and Dockers, so I followed every step very carefully.

 

My problem is that there seems to be an upload size limit. Files over 1GB are not uploaded and my Mac desktop app shows the error "Server replied "413 Request Entity Too Larg..."

 

I have searched this thread and the web without finding a clear resolution that I can understand. Are there some clear instructions to increase the max file size somewhere?

 

Thanks!

Screen Shot 2022-02-24 at 7.17.09 PM.png

 

Please take a look at the six or so posts directly above yours.  There should be some info in there to help.

Link to comment

Thanks snowboarder714, Yeah I looked at these but the situation doesn't look like my issue ...and I don't see a resolution.

 

I have a brand spanking new clean install on a brand new server. I have only installed the required Dockers for Nextcloud -- everything exactly done per Space Invader One's video. Other than upload file size, its working well. So...
 

1) Is there SUPPOSED to be a file size limit? In which case, I'm looking for the settings or parameters to increase this value?

    OR

2) Is file size SUPPOSED to be unlimited, and this condition is an error which needs troubleshooting?

 

Also: total noob here, so you know...

 

Thanks.

Link to comment
1 hour ago, malebron said:

1) Is there SUPPOSED to be a file size limit? In which case, I'm looking for the settings or parameters to increase this value?

 

 

may start here

 

https://docs.nextcloud.com/server/latest/admin_manual/configuration_files/big_file_upload_configuration.html#:~:text=The default maximum file size,filesystem and operating system allows.

 

its been also discussed several times here, now depending on your setup (i assume lsio and reverse proxy etc) i would look at the nginx parts on all documentations about file size upload limits.

Link to comment

Hmm. This talks about a parameter for letsencrypt -- which I don't have installed. Just swag (per the video).

 

I found a "client_max_body_size" parameter in ~appdata/swag/nginx/nginx.conf, but that was correctly set to 0.

 

However, IF that had been set too low, it would have generated the 413 error I'm seeing.

 

Just for grins I tried changing it to 10G and restarting the container, but no change.

 

Are there any other conf files I should be looking for?

Screen Shot 2022-02-25 at 9.34.50 AM.png

Link to comment
On 2/17/2022 at 11:12 AM, Tucubanito07 said:

Anyone has this issue on their Nextcloud instance? I have searched multiple times everywhere and nothing. I also checked the logging screen in nextcloud and nothing comes up. I am on version 23.0.2. Any help is greatly appreciated.

 

image.thumb.png.0108dc8007e06126c8dcd0f7e3becdd8.png

Hello,

 

Has anyone encounter this issue or does anyone know how to resolve this? I dont see anything on the logs.

Link to comment
2 hours ago, JonathanM said:

The swag container was originally known as letsencrypt, before the people running the letsencrypt service objected.

Ah thanks JonathanM! I'd never have guessed. It's like getting to a strange town and being told to "turn left where the MacDonalds used to be"... :)

Link to comment

Max upload file size issue: The plot thickens...

 

I originally saw the errors (413) when uploading >1GB files from my desktop using Nextcloud's Mac desktop app.

Today I tried dragging and dropping to the web GUI instead. Whaddayaknow, a 1.1GB and 3.1GB uploaded with no errors  AND synced correctly back to my desktop. (These failed using the other method)

 

However a 4.3GB file failed to upload with "Error When assembling chunks, status code 504"

 

(Note: Adding new files >1GB to the Nextcloud folder on my Mac still fail with a 413 error.)

 

1) Any idea what the 504 "chunks" error could be about?

 

2) Does anyone know if the desktop app communicates to Nextcloud differently to the web GUI? Is there another conf file? Maybe there's a different desktop app I can test with  (eg can I use the Owncloud app with Nextcloud?)

 

Thanks!

Link to comment

How can I change my database to a different database for Nextcloud? I tried just changing it in next cloud and I started getting a database error. I also tried reinstalling Nextcloud with the new location and that didn’t work either. 

Link to comment
root@VenturaNas:~# docker exec -it nextcloud updater.phar  
Nextcloud Updater - version: v20.0.0beta4-11-g68fa0d4

Current version is 21.0.5.

Update to Nextcloud 21.0.9 available. (channel: "stable")
Following file will be downloaded automatically: https://download.nextcloud.com/server/releases/nextcloud-21.0.9.zip
Open changelog ↗

Steps that will be executed:
[ ] Check for expected files
[ ] Check for write permissions
[ ] Create backup
[ ] Downloading
[ ] Verify integrity
[ ] Extracting
[ ] Enable maintenance mode
[ ] Replace entry points
[ ] Delete old files
[ ] Move new files in place
[ ] Done

Start update? [y/N] y

Info: Pressing Ctrl-C will finish the currently running step and then stops the updater.

[✔] Check for expected files
[✔] Check for write permissions
[ ] Create backup ...PHP Warning:  copy(/data/updater-oc9q1ejvugli/backups/nextcloud-21.0.5.1-1645524247/apps/mail/l10n/ca.js): failed to open stream: No error information in phar:///config/www/nextcloud/updater/updater.phar/lib/Updater.php on line 395
[✘] Create backup failed
Could not copy "/config/www/nextcloud/apps/mail/l10n/ca.js" to "/data/updater-oc9q1ejvugli/backups/nextcloud-21.0.5.1-1645524247/apps/mail/l10n/ca.js". Destination /data/updater-oc9q1ejvugli/backups/nextcloud-21.0.5.1-1645524247/apps/mail/l10n/ca.js is not writable                                                   
                                   

Update failed. To resume or retry just execute the updater again.
root@VenturaNas:~# docker exec -it nextcloud updater.phar  
Nextcloud Updater - version: v20.0.0beta4-11-g68fa0d4

Current version is 21.0.5.

Update to Nextcloud 21.0.9 available. (channel: "stable")
Following file will be downloaded automatically: https://download.nextcloud.com/server/releases/nextcloud-21.0.9.zip
Open changelog ↗

Steps that will be executed:
[ ] Check for expected files
[ ] Check for write permissions
[ ] Create backup
[ ] Downloading
[ ] Verify integrity
[ ] Extracting
[ ] Enable maintenance mode
[ ] Replace entry points
[ ] Delete old files
[ ] Move new files in place
[ ] Done

Start update? [y/N] y

Info: Pressing Ctrl-C will finish the currently running step and then stops the updater.

[ ] Check for expected files ...PHP Warning:  mkdir(): I/O error in phar:///config/www/nextcloud/updater/updater.phar/lib/Updater.php on line 997
[✘] Check for expected files failed
Could not create $updaterDir

Update failed. To resume or retry just execute the updater again.

 

can anyone assist?

i dont know what to do, tried some commands, without success.

Link to comment
1 hour ago, snowborder714 said:
On 2/25/2022 at 1:58 PM, malebron said:

However a 4.3GB file failed to upload with "Error When assembling chunks, status code 504"

 

I'm now getting this when logged into NextCloud on a laptop browser.  Mine is happening for anything above 1GB I believe.

Actually - I discovered that (despite this 504 error code) the file actually uploaded OK and synced to my Mac too. My research seems to point to nginx timeout values - but others have tried to fix this error with no success.

 

I'm still unable to upload files >1GB from the Nextcloud desktop client (Mac) even though these upload OK from the web GUI.

Link to comment

UPDATE: If you are having the same issue (upload from Nextcloud's Mac desktop client fails for large files with 413 error) - I can confirm that the Owncloud Mac client uploaded files up to 4.3GB no errors.

 

Looks like the Nextcloud desktop client is the problem. (Also the Owncloud client can generate public links from the desktop - the Nextcloud client cannot). Note: There is a "server version unsupported" message - so no guarantee of future compatibility.

Link to comment
On 11/9/2021 at 6:40 AM, PSYCHOPATHiO said:

I have wiped my nextcloud & started from scratch & I found out that there are some LDAP issues with this build... I tried the official nextcloud build & LDAP works flawlessly but in Linuxserver build I'm not sure what is wrong but all the fields after I fill them up seem to have no effect.

 

 

also onlyoffice isnt working on Linuxserver build but works on the official build.

 

i get this message in my logs:

Could not detect any host in http:///data/htaccesstest.txt

RuntimeException: Could not get appdata folder for preview

 

 I dont know if what I said makes any sense :)

You ever get LDAP working on this docker? I'm running into the same issue as you with all the fields and buttons greyed out in the "LDAP/AD integration" app. 

Link to comment
15 hours ago, chanrc said:

You ever get LDAP working on this docker? I'm running into the same issue as you with all the fields and buttons greyed out in the "LDAP/AD integration" app. 

oooh yeah, but I used the official nextcloud docker, all others are broken.

The official docker is much faster when paired with redis & everything works nicely.

if you need help you could add me on matrix https://matrix.to/#/@psychopathio:sykorp.com

Edited by PSYCHOPATHiO
  • Like 1
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.