July 30, 20241 yr 12 hours ago, pumperio.eu said: Hello What is the process for modifying these specific values in the most recent versions of unRAID and Nextcloud thanks Version: 8.2.21 Memory limit: 512 MB Maximum execution time: 3600 seconds Maximum upload file size: 512 MB should look something like this:
August 7, 20241 yr Hi! I need some help... Tried accessing my Nextcloud instance today and found this message: I checked and there's no update for the docker available. In fact it was updated 4 days ago. I understand I can open the console and update it using the script, but that that's not the best practice. What should I do? Thanks in advance!
August 8, 20241 yr 21 hours ago, goldfishgam3r said: Hi! I need some help... Tried accessing my Nextcloud instance today and found this message: I checked and there's no update for the docker available. In fact it was updated 4 days ago. I understand I can open the console and update it using the script, but that that's not the best practice. What should I do? Thanks in advance! Update: I opened the logs and I see the following: I never messed with these files manually...
August 13, 20241 yr On 7/20/2024 at 12:55 PM, serch826 said: Hi, how to get FFMPEG installed? Thanks! The answer can be found on the previous page at: You can add the following in the Post Arguments input field and it will install ffmpeg in a way that also survives updates. && docker exec -u 0 Nextcloud /bin/bash -c "apt update && apt install -y libmagickcore-6.q16-6-extra ffmpeg imagemagick ghostscript"
August 17, 20241 yr Hello, I'm getting 413 error when uploading large files using the windows client. So far I have: Added the environment variable PHP_UPLOAD_LIMIT=20G to my unraid container. This change is reflected in the Nextcloud Web UI but I still get the 413 errors. Added client_max_body_size 20G; to my NGINX Prxoy Manager config. Doesn't make any difference. Added php_value upload_max_filesize 20G and php_value post_max_size 20G to .htaccess. Again this is reflected in the Web UI but isn't really needed IMO as the environment variable above does the same thing. Has anyone got any other idea why I am still getting this error?
August 17, 20241 yr 2 hours ago, mattmill said: Hello, I'm getting 413 error when uploading large files using the windows client. So far I have: Added the environment variable PHP_UPLOAD_LIMIT=20G to my unraid container. This change is reflected in the Nextcloud Web UI but I still get the 413 errors. Added client_max_body_size 20G; to my NGINX Prxoy Manager config. Doesn't make any difference. Added php_value upload_max_filesize 20G and php_value post_max_size 20G to .htaccess. Again this is reflected in the Web UI but isn't really needed IMO as the environment variable above does the same thing. Has anyone got any other idea why I am still getting this error? I have managed to resolve this by adding APACHE_BODY_LIMIT=0 To my container environment variables https://help.nextcloud.com/t/server-replied-413-request-entity-too-large-to-put/154278/6?u=mattmill
August 22, 20241 yr On 8/8/2024 at 12:45 PM, goldfishgam3r said: Update: I opened the logs and I see the following: I never messed with these files manually... Same issue for me. I have re-downloaded the docker image and started working again Edited August 22, 20241 yr by daninet
September 11, 20241 yr its not possible to create nextcloud database in MySQL/Maria DB Versions: - unraid 6.12.13 - mysql (docker image) 8.4.2 (newer version not possible because of 'native-password' problematic) - nextcloud (docker image) last updated Sep 7, 2024 No problems during fetching image and installing nextcloud itself in /mnt/user/appdata AND /mnt/cachepool/appdata (only here is the "autoconfig" file). 1st run: The information shown has been provided in the installation mask. The result was an "server error". The user "oc_ncadmin" was created as well as the database but no table ! 2nd run: same error as in 1st run. 3nd run: erase "/mnt/cachepool/appdata/nextcloud" (but NOT "/mnt/user/appdata/nextcloud/") and "force update of the docker container". result see screenshot. But again: the updater created "/mnt/cachpool" ... entries. starting nextcloud fails because of access rights. 4th run: remove docker container with out erasing image. remove all nextcloud dirs re-install via "Apps" mode "Re-install froml Previous Apps" webui --> connection error 5th run: remove docker container incl. erasing image remove all nextcloud dirs same as 4th run 6th run: same as 5th run + remove all db-entries from installations before. Remark: If an IP address is used instead of a fqdn, every time a server error occurs. if user exist in the mysql db the installation procedure add new user automatically with the same username+number (counting from 1+) in the db. Is it really wanted ? I specified the user in the templates myself. Why is it not simply adopted or left as is ?:? By-the-way: Manual added vars MYSQL_HOST, MYSQL_ .... + NEXTCLOUD_ADMIN, NEXTCLOUD_ADMIN_PASSWORD ... are NOT interpreted for an "automatic install". Conclusion: Docker image in combination with the installation procedure for MySQL/Maria DB are very buggy in my case. But may be there are some tricks and hints ? Any help is appreciated ...
September 24, 20241 yr @Goulasch I had also a lots of trouble install nextcloud until I deactivated internal ssl on unraid. I assume it prevented the container talking to the db. I'm not an expert on this though. Might have also been a coindicence but right after disabling ssl it worked.
October 2, 20241 yr Hello, since the last update (Nextcloud Hub 9) i have an error about the integrity check. Almost all the files from the nextcloud folder (core, activity, dav, etc), so i don't know why :-(. Everything is working anyway, just the alert for the file.
October 8, 20241 yr On 2/11/2020 at 7:33 PM, knex666 said: ---- FOLDER RIGHTS To get the right folder/file rights add this to Extra Parameter and Post Execution <ExtraParams>--user 99:100 --sysctl net.ipv4.ip_unprivileged_port_start=0</ExtraParams> <PostArgs>&& docker exec -u 0 NAME_OF_THIS_CONTAINER /bin/sh -c 'echo "umask 000" >> /etc/apache2/envvars'</PostArgs> ExtraParams: --user 99:100 --sysctl net.ipv4.ip_unprivileged_port_start=0 PostArgs: && docker exec -u 0 NAME_OF_THIS_CONTAINER /bin/sh -c 'echo "umask 000" >> /etc/apache2/envvars' Is that still the right way? Why is it not all stored in unraid container the template? Only the --user 99:100 My cron is not running and when I start it via the console, it continues to run endlessly. I have only just installed the container and have not changed anything. when I try it this way docker exec -u www-data Nextcloud php -f /var/www/html/cron.php it says “Cannot write into ‘config’ directory!...” That's why I went directly to the container with right-click, console php -f /var/www/html/cron.php But that is endless. Edited October 8, 20241 yr by karola
October 11, 20241 yr What to do, if I need to install an additional TURN server to get Nextcloud Talk to work outside of my own network Nextcloud offers TALK as an application to do chats and include audio and videoconferencing. However in most cases a TURN server needs to be additionally installed to configure. Nextcloud adminitration manual explanes how to do this on a bare metal installation of Nextcloud. But what do I need to do, so I can use my existing Nextcloud installation based on this docker ? Is it possible ? Thank you
October 12, 20241 yr Hi there, I was running Nextcloud 29.0.8 stable and did an update to Nextcloud 30 today. The docker pull worked fine, however the upgrade fails at "Updating database schema" online, and when running running occ upgrade in terminal, it hangs forever until a Ctrl C break command is sent. Checking via occ app:list , I found that the incompatible apps are already disabled: Calendar (calendar) Contacts (contacts) Deck (deck) Draw.io (drawio) Nextcloud Office (richdocuments) Talk (spreed) I tried to roll back to 29.0.8 but Nextcloud logs say rollback to older version not possible. From what it seems, the only thing holding back the upgrade is the database update, which I cannot find any errors when the upgrade script is running and hanging. What can I do? Edited October 12, 20241 yr by nicholaschancj
October 12, 20241 yr OK I don't know what happened, but after leaving the Unraid server alone for the past 2 hours, Nextcloud suddenly works again. Thanks for reading this post!
October 14, 20241 yr On 10/2/2024 at 6:28 PM, PaCoYoH said: Hello, since the last update (Nextcloud Hub 9) i have an error about the integrity check. Almost all the files from the nextcloud folder (core, activity, dav, etc), so i don't know why :-(. Everything is working anyway, just the alert for the file. any news on that?
October 14, 20241 yr Author 2 hours ago, karola said: any news on that? Results ======= - core - INVALID_HASH - core/js/mimetypelist.js - EXTRA_FILE - core/img/filetypes/drawio.svg - core/img/filetypes/dwb.svg - nextcloud-init-sync.lock Can you post your results. Mine looks like that, and I ll try to replace them. Besides Nextcloud Office doesnt work anymore
October 14, 20241 yr 16 minutes ago, knex666 said: Can you post your results. Mine looks like that, and I ll try to replace them. Besides Nextcloud Office doesnt work anymore Results ======= - core - EXTRA_FILE - nextcloud-init-sync.lock Raw output ========== Array ( [core] => Array ( [EXTRA_FILE] => Array ( [nextcloud-init-sync.lock] => Array ( [expected] => [current] => cf83e1357eefb8bdf1542850d66d8004d920e4050a5315dc83f4a912d36ce9be47d0d13c5d85f2b0ff8318d2677eec2f62b931bd47417a41a538327af827da3e ) ) ) ) Edited October 14, 20241 yr by karola
October 14, 20241 yr Author 11 minutes ago, karola said: Results ======= - core - EXTRA_FILE - nextcloud-init-sync.lock Raw output ========== Array ( [core] => Array ( [EXTRA_FILE] => Array ( [nextcloud-init-sync.lock] => Array ( [expected] => [current] => cf83e1357eefb8bdf1542850d66d8004d920e4050a5315dc83f4a912d36ce9be47d0d13c5d85f2b0ff8318d2677eec2f62b931bd47417a41a538327af827da3e ) ) ) ) So the issue is already opened but there is no fix right now: https://github.com/nextcloud/docker/issues/2299
October 15, 20241 yr After move my old files from a copy of synology to new folder call "files" in nextcloud I ran docker exec --user 99 Nextcloud php occ files:scan --all But I get that error: root@UnRaid-Atorcha:~# docker exec --user 99 Nextcloud php occ files:scan --all Starting scan for user 1 out of 1 (David) Entry "files/00 Autocaravana/Suspensión neumatica.txt" will not be accessible due to incompatible encoding Entry "files/00 Autocaravana/Manuales Autocaravana/Autocaravana Elnagh 590 L (130 Cv) _ Precio, ficha técnica y fotos.pdf" will not be accessible due to incompatible encoding Entry "files/00 Autocaravana/Manuales Autocaravana/CBE_centralitas_PC100,PC200,DS300_manual_español.pdf" will not be accessible due to incompatible encoding Edited October 15, 20241 yr by Atorcha
October 17, 20241 yr On 10/14/2024 at 3:36 PM, karola said: any news on that? Nop nothing, still the same error.
October 17, 20241 yr Author 50 minutes ago, PaCoYoH said: Nop nothing, still the same error. Its possible to disable the check - I dont recommend that - so just wait for the issue to be fixed: 'integrity.check.disabled' => true,
October 17, 20241 yr On 10/15/2024 at 10:27 PM, Atorcha said: After move my old files from a copy of synology to new folder call "files" in nextcloud I ran docker exec --user 99 Nextcloud php occ files:scan --all But I get that error: root@UnRaid-Atorcha:~# docker exec --user 99 Nextcloud php occ files:scan --all Starting scan for user 1 out of 1 (David) Entry "files/00 Autocaravana/Suspensión neumatica.txt" will not be accessible due to incompatible encoding Entry "files/00 Autocaravana/Manuales Autocaravana/Autocaravana Elnagh 590 L (130 Cv) _ Precio, ficha técnica y fotos.pdf" will not be accessible due to incompatible encoding Entry "files/00 Autocaravana/Manuales Autocaravana/CBE_centralitas_PC100,PC200,DS300_manual_español.pdf" will not be accessible due to incompatible encoding I need help with this. I can not solve and I can not use it
October 19, 20241 yr After update to the latest version. Error in Log and stops the container w8ting of next update rsync error: some files/attrs were not transferred (see previous errors) (code 23) at main.c(1338) [sender=3.2.7] cannot delete non-empty directory: node_modules/@babel/helper-string-parser cannot delete non-empty directory: node_modules/@babel/helper-skip-transparent-expression-wrappers/lib cannot delete non-empty directory: node_modules/@babel/helper-skip-transparent-expression-wrappers cannot delete non-empty directory: node_modules/@babel/helper-simple-access/lib cannot delete non-empty directory: node_modules/@babel/helper-simple-access cannot delete non-empty directory: node_modules/@babel/helper-replace-supers/lib cannot delete non-empty directory: node_modules/@babel/helper-replace-supers cannot delete non-empty directory: node_modules/@babel/helper-remap-async-to-generator/lib cannot delete non-empty directory: node_modules/@babel/helper-remap-async-to-generator cannot delete non-empty directory: node_modules/@babel/helper-plugin-utils/lib cannot delete non-empty directory: node_modules/@babel/helper-plugin-utils cannot delete non-empty directory: node_modules/@babel/helper-optimise-call-expression/lib cannot delete non-empty directory: node_modules/@babel/helper-optimise-call-expression cannot delete non-empty directory: node_modules/@babel/helper-module-transforms/lib cannot delete non-empty directory: node_modules/@babel/helper-module-transforms cannot delete non-empty directory: node_modules/@babel/helper-module-imports/lib cannot delete non-empty directory: node_modules/@babel/helper-module-imports cannot delete non-empty directory: node_modules/@babel/helper-member-expression-to-functions/lib cannot delete non-empty directory: node_modules/@babel/helper-member-expression-to-functions cannot delete non-empty directory: node_modules/@babel/helper-define-polyfill-provider/lib/visitors cannot delete non-empty directory: node_modules/@babel/helper-define-polyfill-provider/lib/node cannot delete non-empty directory: node_modules/@babel/helper-define-polyfill-provider/lib/browser cannot delete non-empty directory: node_modules/@babel/helper-define-polyfill-provider/lib cannot delete non-empty directory: node_modules/@babel/helper-define-polyfill-provider/esm cannot delete non-empty directory: node_modules/@babel/helper-define-polyfill-provider cannot delete non-empty directory: node_modules/@babel/helper-create-regexp-features-plugin/lib cannot delete non-empty directory: node_modules/@babel/helper-create-regexp-features-plugin cannot delete non-empty directory: node_modules/@babel/helper-create-class-features-plugin/lib cannot delete non-empty directory: node_modules/@babel/helper-create-class-features-plugin cannot delete non-empty directory: node_modules/@babel/helper-compilation-targets/lib cannot delete non-empty directory: node_modules/@babel/helper-compilation-targets cannot delete non-empty directory: node_modules/@babel/helper-builder-binary-assignment-operator-visitor/lib cannot delete non-empty directory: node_modules/@babel/helper-builder-binary-assignment-operator-visitor cannot delete non-empty directory: node_modules/@babel/helper-annotate-as-pure/lib cannot delete non-empty directory: node_modules/@babel/helper-annotate-as-pure cannot delete non-empty directory: node_modules/@babel/generator/lib/node cannot delete non-empty directory: node_modules/@babel/generator/lib/generators cannot delete non-empty directory: node_modules/@babel/generator/lib cannot delete non-empty directory: node_modules/@babel/generator cannot delete non-empty directory: node_modules/@babel/eslint-parser/lib/worker cannot delete non-empty directory: node_modules/@babel/eslint-parser/lib/utils cannot delete non-empty directory: node_modules/@babel/eslint-parser/lib/convert cannot delete non-empty directory: node_modules/@babel/eslint-parser/lib cannot delete non-empty directory: node_modules/@babel/eslint-parser cannot delete non-empty directory: node_modules/@babel/core/src/config/files cannot delete non-empty directory: node_modules/@babel/core/src/config cannot delete non-empty directory: node_modules/@babel/core/src cannot delete non-empty directory: node_modules/@babel/core/lib/vendor cannot delete non-empty directory: node_modules/@babel/core/lib/transformation/util cannot delete non-empty directory: node_modules/@babel/core/lib/transformation/file cannot delete non-empty directory: node_modules/@babel/core/lib/transformation cannot delete non-empty directory: node_modules/@babel/core/lib/tools cannot delete non-empty directory: node_modules/@babel/core/lib/parser/util cannot delete non-empty directory: node_modules/@babel/core/lib/parser cannot delete non-empty directory: node_modules/@babel/core/lib/gensync-utils cannot delete non-empty directory: node_modules/@babel/core/lib/errors cannot delete non-empty directory: node_modules/@babel/core/lib/config/validation cannot delete non-empty directory: node_modules/@babel/core/lib/config/helpers cannot delete non-empty directory: node_modules/@babel/core/lib/config/files cannot delete non-empty directory: node_modules/@babel/core/lib/config cannot delete non-empty directory: node_modules/@babel/core/lib cannot delete non-empty directory: node_modules/@babel/core cannot delete non-empty directory: node_modules/@babel/compat-data/data cannot delete non-empty directory: node_modules/@babel/compat-data cannot delete non-empty directory: node_modules/@babel/code-frame/lib cannot delete non-empty directory: node_modules/@babel/code-frame cannot delete non-empty directory: node_modules/@babel cannot delete non-empty directory: node_modules/@ampproject/remapping/dist/types cannot delete non-empty directory: node_modules/@ampproject/remapping/dist cannot delete non-empty directory: node_modules/@ampproject/remapping cannot delete non-empty directory: node_modules/@ampproject cannot delete non-empty directory: node_modules/@adobe/css-tools/dist cannot delete non-empty directory: node_modules/@adobe/css-tools cannot delete non-empty directory: node_modules/@adobe cannot delete non-empty directory: node_modules/@actions/http-client/lib cannot delete non-empty directory: node_modules/@actions/http-client cannot delete non-empty directory: node_modules/@actions/core/node_modules/uuid/dist/umd cannot delete non-empty directory: node_modules/@actions/core/node_modules/uuid/dist/esm-node cannot delete non-empty directory: node_modules/@actions/core/node_modules/uuid/dist/esm-browser cannot delete non-empty directory: node_modules/@actions/core/node_modules/uuid/dist/bin cannot delete non-empty directory: node_modules/@actions/core/node_modules/uuid/dist cannot delete non-empty directory: node_modules/@actions/core/node_modules/uuid cannot delete non-empty directory: node_modules/@actions/core/node_modules/.bin cannot delete non-empty directory: node_modules/@actions/core/node_modules cannot delete non-empty directory: node_modules/@actions/core/lib cannot delete non-empty directory: node_modules/@actions/core cannot delete non-empty directory: node_modules/@actions cannot delete non-empty directory: node_modules/.bin cannot delete non-empty directory: node_modules
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.