April 6, 20224 yr 10 hours ago, dlandon said: Edit the ownCloud Docker template and select php 7.3 or 7.4. 7.4 would be preferrable to prevent this in the future. Thanks. That did solve the error message, but I still can't login. Now I just get a generic error about not being able to reach the page; This is what I can see in the logfile; Edited April 6, 20224 yr by workermaster
April 18, 20224 yr Thanks for this. I have 3 questions for this. 1. Can this be use PostgreSQL instead of MariaDB? I hear that PostgreSQL can improve performance. Is that true? 2. How can I access mariaDB using admirer? 3. I can't login on the desktop client but web is working. It says 403 forbidden. I have 2FA and OAuth2 enabled. Can you help? Thanks. Edited April 18, 20224 yr by HHUBS
May 7, 20224 yr On 4/18/2022 at 6:25 PM, HHUBS said: Thanks for this. I have 3 questions for this. 1. Can this be use PostgreSQL instead of MariaDB? I hear that PostgreSQL can improve performance. Is that true? 2. How can I access mariaDB using admirer? 3. I can't login on the desktop client but web is working. It says 403 forbidden. I have 2FA and OAuth2 enabled. Can you help? Thanks. More info about you configuration in 3 point. What you mean in web? it avalible using domain or local ip adress?
May 11, 20224 yr Hi a newbie here :-). I installed this, filled in the important data / config. Everything is installed and working via 192.168.0.124. I have haproxy running on OPNSense and filled the info in, so, 192.168.0.124 on port 80. I tried it, but something weird is happning, I redirect to: https://_/ if I try it via my domain. How can I fix this? I added my domain as trusted domain in the config.php. UPDATE: Fixed. Changed the port to 443 and selected SSL within haproxy. Edited May 11, 20224 yr by BliXem
May 26, 20224 yr Hi, first thanks for your efforts. I think the docker updated and I got several errors. Some are now fixed, as the mysql error file can't be created, but although I can see all my files I cannot upload any new file, nor via desktop app nor webUI. I got constantly 403 errors. I have php 7.4 and mysql 15. root@ae87fc4c33d6:/config# php -v PHP 7.4.29 (cli) (built: Apr 21 2022 10:16:36) ( NTS ) Copyright (c) The PHP Group Zend Engine v3.4.0, Copyright (c) Zend Technologies with Zend OPcache v7.4.29, Copyright (c), by Zend Technologies I didn't changed anything but seems the DB tried to upgrade... but fails. No problem here. But any upload request finishes in 403 ( forbidden) 192.168.2.20 - - [26/May/2022:15:44:46 +0200] "PUT /remote.php/dav/files/Kanashii/Documents/2022_1_10__Contrato_Temporal.pdf HTTP/1.1" 403 6458 "-" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/102.0.5005.61 Safari/537.36" Data files permissions are not changed: abc / users drwxr-xr-x 1 abc users 6 Jan 23 16:21 cache drwxr-xr-x 1 abc users 117 Oct 6 2021 files drwxr-xr-x 1 abc users 63 Oct 6 2021 files_trashbin drwxr-xr-x 1 abc users 86 Oct 24 2021 files_versions drwxr-xr-x 1 abc users 24576 Feb 23 19:48 thumbnails drwxr-xr-x 1 abc users 124 Feb 28 17:21 uploads I can write a file with abc user: -rw-r--r-- 1 abc users 0 May 26 16:17 test And the nginx is using the same user as usual (abc): abc 8013 8006 0 15:33 ? 00:00:00 nginx: worker process abc 8014 8006 0 15:33 ? 00:00:00 nginx: worker process abc 8015 8006 0 15:33 ? 00:00:00 nginx: worker process I don't use privileged mode in the docker template. Paths are well set and properly visibles... so I don't know what fails... Edited May 26, 20224 yr by Kanashii
May 26, 20224 yr 4 hours ago, Kanashii said: Hi, first thanks for your efforts. I think the docker updated and I got several errors. Some are now fixed, as the mysql error file can't be created, but although I can see all my files I cannot upload any new file, nor via desktop app nor webUI. I got constantly 403 errors. I have php 7.4 and mysql 15. root@ae87fc4c33d6:/config# php -v PHP 7.4.29 (cli) (built: Apr 21 2022 10:16:36) ( NTS ) Copyright (c) The PHP Group Zend Engine v3.4.0, Copyright (c) Zend Technologies with Zend OPcache v7.4.29, Copyright (c), by Zend Technologies I didn't changed anything but seems the DB tried to upgrade... but fails. No problem here. But any upload request finishes in 403 ( forbidden) 192.168.2.20 - - [26/May/2022:15:44:46 +0200] "PUT /remote.php/dav/files/Kanashii/Documents/2022_1_10__Contrato_Temporal.pdf HTTP/1.1" 403 6458 "-" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/102.0.5005.61 Safari/537.36" Data files permissions are not changed: abc / users drwxr-xr-x 1 abc users 6 Jan 23 16:21 cache drwxr-xr-x 1 abc users 117 Oct 6 2021 files drwxr-xr-x 1 abc users 63 Oct 6 2021 files_trashbin drwxr-xr-x 1 abc users 86 Oct 24 2021 files_versions drwxr-xr-x 1 abc users 24576 Feb 23 19:48 thumbnails drwxr-xr-x 1 abc users 124 Feb 28 17:21 uploads I can write a file with abc user: -rw-r--r-- 1 abc users 0 May 26 16:17 test And the nginx is using the same user as usual (abc): abc 8013 8006 0 15:33 ? 00:00:00 nginx: worker process abc 8014 8006 0 15:33 ? 00:00:00 nginx: worker process abc 8015 8006 0 15:33 ? 00:00:00 nginx: worker process I don't use privileged mode in the docker template. Paths are well set and properly visibles... so I don't know what fails... I solved the problem and it was so simple... The www directory changed to root in privileged mode and the abc:users cannot execute de upload php script. Now it's fixed. If you can 403 in nginx check the owner of the php and data directories.
May 31, 20224 yr Noob question here, after the Unraid update, I can't seem to let Owncloud working again. How to fix this? Quote *** Booting runit daemon... *** Runit started as PID 8020 May 31 18:11:44 a98a1f39854d cron[8029]: (CRON) INFO (pidfile fd = 3) May 31 18:11:44 a98a1f39854d cron[8029]: (CRON) INFO (Running @reboot jobs) 220531 18:11:45 mysqld_safe Logging to '/config/database/a98a1f39854d.err'. 220531 18:11:45 mysqld_safe Starting mysqld daemon with databases from /config/database /usr/bin/mysqld_safe_helper: Can't create/write to file '/config/database/a98a1f39854d.err' (Errcode: 13 "Permission denied") 220531 18:11:46 mysqld_safe Logging to '/config/database/a98a1f39854d.err'. 220531 18:11:46 mysqld_safe Starting mysqld daemon with databases from /config/database /usr/bin/mysqld_safe_helper: Can't create/write to file '/config/database/a98a1f39854d.err' (Errcode: 13 "Permission denied") 220531 18:11:47 mysqld_safe Logging to '/config/database/a98a1f39854d.err'. 220531 18:11:47 mysqld_safe Starting mysqld daemon with databases from /config/database /usr/bin/mysqld_safe_helper: Can't create/write to file '/config/database/a98a1f39854d.err' (Errcode: 13 "Permission denied") 220531 18:11:49 mysqld_safe Logging to '/config/database/a98a1f39854d.err'. 220531 18:11:49 mysqld_safe Starting mysqld daemon with databases from /config/database /usr/bin/mysqld_safe_helper: Can't create/write to file '/config/database/a98a1f39854d.err' (Errcode: 13 "Permission denied") 220531 18:11:50 mysqld_safe Logging to '/config/database/a98a1f39854d.err'. 220531 18:11:50 mysqld_safe Starting mysqld daemon with databases from /config/database /usr/bin/mysqld_safe_helper: Can't create/write to file '/config/database/a98a1f39854d.err' (Errcode: 13 "Permission denied") 220531 18:11:52 mysqld_safe Logging to '/config/database/a98a1f39854d.err'. 220531 18:11:52 mysqld_safe Starting mysqld daemon with databases from /config/database /usr/bin/mysqld_safe_helper: Can't create/write to file '/config/database/a98a1f39854d.err' (Errcode: 13 "Permission denied") 220531 18:11:53 mysqld_safe Logging to '/config/database/a98a1f39854d.err'. 220531 18:11:53 mysqld_safe Starting mysqld daemon with databases from /config/database /usr/bin/mysqld_safe_helper: Can't create/write to file '/config/database/a98a1f39854d.err' (Errcode: 13 "Permission denied") 220531 18:11:54 mysqld_safe Logging to '/config/database/a98a1f39854d.err'. 220531 18:11:54 mysqld_safe Starting mysqld daemon with databases from /config/database /usr/bin/mysqld_safe_helper: Can't create/write to file '/config/database/a98a1f39854d.err' (Errcode: 13 "Permission denied") PUID 99 PGID 100
June 2, 20224 yr Dear members, When switching over to our new hosting provider I tried to use a new e-mail account. The following error appeared: "A problem occurred while sending the email. Please revise your settings. (Error: Expected response code 250 but got code "501", with message "501 Syntactically invalid HELO argument(s) ")". The new hosting provider suspects the occurs due to wrong hostname being send/shared and their server does not allow such in incoherent data as part of their safety protocols. I was wondering how I might be able to adjust the hostname which now seems to be more like password than a name; anyone suggestions? In addition, I added 'mail_smtpdebug' => true, to the config file to able to troubleshoot. However, it would seem the error are not registered in the log that is set to log 'Everything'. Is the location of "'mail_smtpdebug' => true," relevant and/or is the debugging safeted at a different location or something else? I found the /etc/hosts file that contains the error stated by Digao - see comment below -. However, every time that restart the docker the the adjustments are revered. https://stackoverflow.com/questions/86907/how-do-i-fix-501-syntactically-invalid-helo-arguments "After spending so many hours trying to fix this problem, which in my case just come up from nothing, I ended up with a solution. In my case, only the systems deployed to Suse OSs suddenly stopped sending emails but not those ( the same ) running on Ubuntu. After exhausting and eliminating all the suggested possibilities of this problem and even considering to change de OS of those machines, I found out that somehow the send email service is sensible to the hostname of the host machine. In the Ubuntu machines the file /etc/hosts have only the following line: 127.0.0.1 localhost and so were the Suse machines, which stopped sending the emails. After editing the /etc/hosts from Suse machines to 127.0.0.1 localhost proplad where proplad is the hostname of the machine, the errors were vanished. It seems that some security policy ( maybe from the smtp service ) uses the hostname information carried through the API, which was being ignored in the case of the Ubuntu machines, but not in the case of Suse machines. Hope this helps others, avoiding massive hours of research over the internet." Edited June 2, 20224 yr by LimeCenter Added new findings
June 3, 20224 yr I can’t figure out how to fix this No marketplace connection: cURL error 77: error setting certificate verify locations: CAfile: /data/files_external/rootcerts.crt CApath: /etc/ssl/certs
June 3, 20224 yr Author 3 hours ago, RSQtech said: I can’t figure out how to fix this No marketplace connection: cURL error 77: error setting certificate verify locations: CAfile: /data/files_external/rootcerts.crt CApath: /etc/ssl/certs Looks like a certificate issue. Switch to advanced mode and force an update to see if it clears up.
June 24, 20224 yr Author 8 hours ago, ubermetroid said: Is there an ETA for an update to the new version of ownCloud? ownCloud is not updated in the Docker container. You'll need to update manually. The procedure is in the second post. Don't do an auto update, it will fail.
June 24, 20224 yr Just now, dlandon said: ownCloud is not updated in the Docker container. You'll need to update manually. The procedure is in the second post. Don't do an auto update, it will fail. Thare's a way to disable autoupdate? It keeps happening although I don't want to. Maybe a environment value o extra post parameter will be nice if possible.
June 24, 20224 yr On 6/3/2017 at 10:16 PM, dlandon said: Manual update is the recommended way to update an existing ownCloud installation. Disable apps - Calendar, Contacts, and any add on apps - Settings->Apps. Access the ownCloud Docker 'docker exec -it ownCloud bash'. Install nano 'apt-get install nano'. Put ownCloud in maintenance mode by editing 'nano /config/www/owncloud/config/config.php'. Stop ownCloud docker from the unRAID Docker UI. Get into the unRAID command line. Change directory to 'cd /mnt/user/appdata/ownCloud/www'. Move the existing owncloud version 'mv ./owncloud ./owncloud-old'. Download and unzip the owncloud update from here. Copy update using a PC to \appdata\ownCloud\www\. Go back to the Unraid command line. Copy external apps 'cp -R /mnt/user/appdata/ownCloud/www/owncloud-old/apps-external/ /mnt/user/appdata/ownCloud/www/owncloud/apps-external/'. Change ownership 'chown nobody:users owncloud'. Copy the old version of config.php 'cp /mnt/user/appdata/ownCloud/www/owncloud-old/config/config.ph /mnt/user/appdata/ownCloud/www/owncloud/config/config.php'. Start owncloud docker from unRAID Docker UI. Access the ownCloud Docker 'docker exec -it ownCloud bash'. Change directory to new owncloud version 'cd /config/www/owncloud'. Change occ to executable 'chmod +x occ'' Execute upgrade: 'sudo -u abc ./occ upgrade'. Change permissions on owncloud 'chmod 755 /config/www/owncloud'. Take ownCloud out of maintenance mode by editing 'nano /config/www/owncloud/config/config.php'. Re-enable apps - Calendar, Contacts, and any add on apps. I will follow it tonight. Thanks
June 24, 20224 yr Author 18 minutes ago, Kanashii said: Thare's a way to disable autoupdate? It keeps happening although I don't want to. Maybe a environment value o extra post parameter will be nice if possible. The auto update is the container applying security and other updates to Ubuntu upon startup. It is done because many users expose it to the Internet. Why do you say it keeps happening? It only happens when the container is started, and any previous updates are kept so it doesn't have to update again.
June 24, 20224 yr Author 1 hour ago, Kanashii said: I will follow it tonight. Thanks Be sure to set php to 7.4 in the xml template. 10.10 does not run on 7.2.
June 27, 20224 yr Is there any way to make the startup scripts not cause the docker container to fail to run? I'm seeing this in the logs every time I try to start ownCloud. Hit:5 http://ppa.launchpad.net/ondrej/php/ubuntu focal InRelease Hit:6 https://mirrors.gigenet.com/mariadb/repo/10.3/ubuntu focal InRelease Reading package lists... E: dpkg was interrupted, you must manually run 'dpkg --configure -a' to correct the problem. E: dpkg was interrupted, you must manually run 'dpkg --configure -a' to correct the problem. *** /etc/my_init.d/20_apt_update.sh failed with status 100 I'd love for it to just start so I could exec in and run the dpkg line to fix it, but it dies every time. Any ideas on how to get past this?
June 28, 20224 yr Author 59 minutes ago, DMills said: I'd love for it to just start so I could exec in and run the dpkg line to fix it, but it dies every time. Any ideas on how to get past this? Turn on the "Basic View" switch to select to the "Advanced View". Then click on "Force Update". It will load a fresh Docker Image. See if that doesn't fix the issue.
June 28, 20224 yr 53 minutes ago, dlandon said: Turn on the "Basic View" switch to select to the "Advanced View". Then click on "Force Update". It will load a fresh Docker Image. See if that doesn't fix the issue. That did the trick, thanks so much!
June 29, 20224 yr On 6/24/2022 at 1:25 PM, Kanashii said: I will follow it tonight. Thanks Until today I did not know about the recommendation to update owncloud manually. In the past I used the auto updater many times without any issues. This time I'm facing a 504 Gateway Timeout error. That's why I'm here Current version is 10.9.1.2 All former updates up to version 10.9.1.2 went fine, as already mentioned. This time it seems I have to go the gard way. dlandon mentioned that the auto updater will fail. What is the reason? BR, Sascha
July 12, 20223 yr I tried to follow the upgrde instructions but when I connect back into the console of the docker container, the upgrade command fails: Any ideas?
August 2, 20223 yr On 7/12/2022 at 6:19 AM, tmchow said: I tried to follow the upgrde instructions but when I connect back into the console of the docker container, the upgrade command fails: Any ideas? Start the manual updater app. It work for me ./owncloud/occ upgrade https://central.owncloud.org/t/problem-upgrading-via-occ-command-from-10-1-0-4-to-10-2-1/20926
August 2, 20223 yr Guys, somebody know maybe where is something normal like plex, with 1 time payment becouse realy owncloud / nextcloud is shit. Then it didnt get new error, it lags
August 6, 20223 yr I've just installed OwnCloud, and it's working great. I've moved all of my files over via a share move, so I need to kick off an OCC files:scan -all and have it index everything. Is there a way to do it in the Web UI? Or is it all command-line work? And if it is, is there some documentation on how to get it to run with this docker image? Seems like OCC can't be executed.
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.