October 22, 20241 yr On 7/18/2024 at 11:46 AM, What's_a_Computer? said: Awesome, that helps me understand way more than trying to read manuals. When I run: docker exec -u www-data Nextcloud php occ It tells me: Cannot write into "config" directory! This can usually be fixed by giving the web server write access to the config directory. But, if you prefer to keep config.php file read only, set the option "config_is_read_only" to true in it. See https://docs.nextcloud.com/server/29/go.php?to=admin-config {"reqId":"D5aMQwP3cxwQUDQY5zHd","level":3,"time":"2024-07-18T10:33:00+00:00","remoteAddr":"","user":"--","app":"PHP","method":"","url":"--","message":"fopen(/var/www/html/config/config.php): Failed to open stream: Permission denied at /var/www/html/lib/private/Config.php#221","userAgent":"--","version":"","data":{"app":"PHP"}} As an update to using OCC commands. I recommended using the occweb app, but it appears to be broken on the latest version (I get an Internal Server Error). I've raised an issue on github for it. For running OCC commands from the Unraid console, I get the same error as you when using the above command, but the following works for me... docker exec Nextcloud php occ db:add-missing-indices Just replace the text after occ with the command that the admin console wants you to run. (also posting it here to remind myself, as I always forget)
October 23, 20241 yr I use Unraid, and have been using Immich to store my photos. I also use the Immich Android app to upload photos to the photo share that points to Immich. Admittedly I don't know a whole lot about how this all works under the hood - I followed this tutorial to set Immich up in the first place. This is a shortened version of how the photo directory Immich manages looks: ". ├── encoded-video │ └── c26556d6-2981-4807-943e-da1daf03decf │ ├── 00 │ │ ├── 10 │ │ └── d5 │ └── ff │ ├── 09 │ └── f1 ├── library ├── profile ├── thumbs └── upload └── c26556d6-2981-4807-943e-da1daf03decf ├── 00 ├── d0 │ ├── 01 │ ├── 05 │ ├── 06 │ ├── 07 ├── d1 │ ├── 00 │ ├── 01 │ ├── 05 │ ├── 08 │ ├── 09 " Anyway, I want to now instead use Nextcloud as the storage location for my photos, and just use Immich as a place to view them etc. Then I will find a way to have my camera roll on my phone automatically upload to this new Nextcloud folder. However, I don't know: - How Nextcloud will organise photos uploaded to it. - How (if at all) I should reorganise the current Immich photo directory to be compatible with this. - Anything else I am not yet considering because of my lack of knowledge. Any advice? Edited October 23, 20241 yr by icarus69
October 26, 20241 yr On 10/19/2024 at 9:03 PM, zer0.de said: 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 its still present, after update && reinstall
November 8, 20241 yr I'm running a fresh install of the container, but after start I get: => Searching for scripts (*.sh) to run, located in the folder: /docker-entrypoint-hooks.d/before-starting and it will just stop there, I checked, there are no scripts in this folder. I added one (just an echo command) it's getting called. So I assume it's something happening after this. I quite don't understand what's going on. When pulling the container I'm getting: IMAGE ID [a480a496ba95]: Already exists. So I'm not sure if this might be the culprit, but I don't think so, it's quite common, that an image already exists... fyi, I had major issues with my server, but it should be back to normal and all other containers are working fine. I just checked, this happens for every nextcloud I'm pulling, so even nextcloud-ffmpeg is showing the same behavior. Edited November 8, 20241 yr by Autchirion
November 9, 20241 yr Neither show a problem, "searching for scripts" is just that, if any it runs them but if not it's then ready to go, there's simply no more output. Edited November 9, 20241 yr by Kilrah
November 14, 20241 yr Hi i have the same problem... how can i solve this? reinstalling the Docker does not work for me! Pleas help! Edited November 14, 20241 yr by Putschgi
November 14, 20241 yr On 11/9/2024 at 5:00 AM, Autchirion said: I'm running a fresh install of the container, but after start I get: => Searching for scripts (*.sh) to run, located in the folder: /docker-entrypoint-hooks.d/before-starting and it will just stop there, I checked, there are no scripts in this folder. I added one (just an echo command) it's getting called. So I assume it's something happening after this. I quite don't understand what's going on. Hi~ How did you solve the issue? I update the Nextcloud docker and the same log as yours. I touched an empty script like you, and the Nextcloud service was stuck, I can't connect to the web UI but the app is shown online.
November 16, 20241 yr Hello, thank you for your docker. I am quite limited to transfer a 4gb file via webdav. I tried to find and modify the file: "php.ini" via the docker console. But I get "permission denied" all the time. Do you have a solution to offer me? because I don't understand how I can increase the transfer limit. Thanks in advance
November 17, 20241 yr On 11/16/2024 at 7:31 AM, sechag said: Hello, thank you for your docker. I am quite limited to transfer a 4gb file via webdav. I tried to find and modify the file: "php.ini" via the docker console. But I get "permission denied" all the time. Do you have a solution to offer me? because I don't understand how I can increase the transfer limit. Thanks in advance Same issues, getting 413 entity to large issues. Pretty frustrating since I have some zip and ISO files that are around the 5G mark... Have been messing with this for a few days blindly and am about to just start paying for storage. Tried adding these values with no change besides the WebGUI showing larger file uploads are supported. Issues only occur with the sync (webDav) from the windows client... Unraid Variable PHP_UPLOAD_LIMIT = 10G Config File Additions // New configurations for large file uploads 'filelocking.enabled' => true, 'filelocking.locking_method' => 'stat', 'filelocking.lock_timeout' => 3600, 'filelocking.lock_path' => '/tmp/nextcloud-lock/', // Increase PHP limits 'upload_max_filesize' => '100G', 'post_max_size' => '100G', 'max_input_time' => 3600, 'max_execution_time' => 3600, 'memory_limit' => '1024M', // Adjust chunk size for better performance with large files 'files.max_chunk_size' => 20971520, // Increase session lifetime for long uploads 'session_lifetime' => 86400, Edited November 17, 20241 yr by MackAttack
November 18, 20241 yr On 4/25/2024 at 6:30 AM, knex666 said: give this a try and add the parameter PHP_UPLOAD_LIMIT and set it to a bigger size Hey there, where do i have to add this line? I´m searching the whole internet since weeks, because i dont know how to increase upload limit. I´m accessing my Nextcloud via Tailscale, both running on Unraid. Currently using your Docker image and i cant find the php.ini file. Seems like there are a lot of people out there, who got the same issue and just editing the php.ini in the nextcloud folder didn´t change anything for most of them. Would appreciate some help cause i´m a total linux noob still Thank you for your work!
November 19, 20241 yr On 8/17/2024 at 3:58 PM, mattmill said: 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 Should it work like this? Hope i did it like you mentioned.
November 19, 20241 yr Thanks for your advice, but it is still not working for me. Think i will register in nextcloud forum and see if there´s somebody who can help.
November 26, 20241 yr On 11/19/2024 at 3:47 AM, einsmetaz said: Thanks for your advice, but it is still not working for me. Think i will register in nextcloud forum and see if there´s somebody who can help. What he's saying is to set the variables up like this. I just set this up and it worked great. The "Name" is just the name you see on the unraid web interface while the "key" and "value" are the actual values passed into docker. This will automatically create the "-e APACHE_BODY_LIMIT=0" line when starting up the docker image. You will need to do this for both the limit variable. Edited November 26, 20241 yr by jonathan.k
November 26, 20241 yr Hello, How do we get rid of "Accessing site insecurely via HTTP. You are strongly advised to set up your server to require HTTPS instead. " ? The documentation talk about modifying stuff in apache but doesn't say much. I'm accessing by reverse proxy so I'm already in https, but since the proxy is using http, that's the problem. EDIT: I also have the problem that I cannot run it as --user=99:100 because I'm using redis. Because I'm using redis, it will fail saying it cannot create a file on startup and crash. edit2: unsure if there's another way but I solved the problem with redis by mapping the file redis-session.php outside the container. I also copied the file outside the container and mapped it inside the docker. I'm still trying to find the solution for the HTTP error though Edited November 26, 20241 yr by Nodiaque
November 26, 20241 yr Author On 11/19/2024 at 10:04 AM, Kilrah said: No, like this Thanks for that to all of you! I have append those parameters to the App Template file.
November 27, 20241 yr 23 hours ago, Nodiaque said: I'm accessing by reverse proxy so I'm already in https, but since the proxy is using http, that's the problem. That's how mine is and there's no error, so it's not a problem if it's http between proxy and NC. Maybe you haven't set your RP to force https and are actually accessing it through http without being redirected to https by the RP.
November 27, 20241 yr 17 minutes ago, Kilrah said: That's how mine is and there's no error, so it's not a problem if it's http between proxy and NC. Maybe you haven't set your RP to force https and are actually accessing it through http without being redirected to https by the RP. I just installed it and did nothing else. Nginx talk using http cause that's the port that is configured in that docker. But Niginx itself is in https. The default swag configuration is to use port 443 and https, but these port aren't in use. And if I try to access nextcloud directly using https, it fail. Edited November 27, 20241 yr by Nodiaque
December 11, 20241 yr Hi, I'm using this container for some time without much issue. Where I live I have internet access with CGNAT only so I dont have my own IP. I'm using cloudflare tunnel to access my nextcloud instance running on my server. CF provides me an SSL so all good. However when I'm trying to access locally through IP I cannot, connection not secure. My localhost and domain is added to the config. 'trusted_domains' => array ( 0 => '192.168.1.200:8666', 1 => 'mydomain.xyz', ), 'trusted_proxies' => array ( 0 => '77.221.43.251', 1 => '172.17.0.6', 2 => '192.168.1.200', ), 'overwriteprotocol' => 'https', 'overwrite.cli.url' => 'http://192.168.1.200:8666', I want to know if there is some easy to understand description on how to attach certificate to the container and config it to be used by the container even locally. Unfortunately most of the help in this topic is to setup reverse proxy like traefik or swag and add certificate there but its not an option for me as far as I can understand or it would just add extra complexity for little to no benefit.
December 24, 20241 yr Hi, i tried to access my unraid shares with the "Lokal" varaint from external storage app. And it doenst work. My path to one of my shares is for example /mnt/user/Movies. How i have to configure it? BR Becksy
December 24, 20241 yr 9 minutes ago, Becksy said: How i have to configure it? do you have your local path also mounted in the NC docker ? sample, volume, add, /mnt /mnt makes it easier as you have the same path inside / out, then you can mount anything "local" inside your NC instance
December 24, 20241 yr 5 minutes ago, alturismo said: do you have your local path also mounted in the NC docker ? sample, volume, add, /mnt /mnt makes it easier as you have the same path inside / out, then you can mount anything "local" inside your NC instance No i havent. How i do that?
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.