Skip to content
View in the app

A better way to browse. Learn more.

Unraid

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

levster

Members
  • Joined

  • Last visited

Everything posted by levster

  1. Thank you! Did I enable it by accident? Also, on a separate note, I want to run docker safe new permissions. However, there are a lot of folders which were previously checked which are excluded. How do I remove them from the excluded list?
  2. Thank you. So, how do I prevent this in the future? Lev
  3. It finally came up. Here are the diagnostics. Lev tower-diagnostics-20211207-1823.zip
  4. I just tried to reboot and now the tower will not come up at all!!! I can see flash on my local network, but that is all. Help!!! I can ssh into it. Slowly, I see all of the folders through the explorer, it took about 5 minutes for them to come up. Still no GUI. tower-diagnostics-20211207-1755.zip
  5. Thanks, I'll reboot later and see. I am trying to re-install Nextcloud and am hitting a brick wall...
  6. Recently I noticed that every time I do a clean reboot my system goes into a parity check. Can someone please shed some light into this? Thanks, Lev tower-diagnostics-20211207-1712.zip
  7. I had to completely wipe out and recreate my nextcloud / swag / mariaDB and now when logging into the nextcloud I keep getting the: Welcome to your SWAG instance A webserver and reverse proxy solution brought to you by linuxserver.io with php support and a built-in Certbot client. We have an article on how to use swag here: docs.linuxserver.io For help and support, please visit: linuxserver.io/support I did not change anything in the nextcloud.subdomain.conf Here is me nextcloud config.php: $CONFIG = array ( 'memcache.local' => '\\OC\\Memcache\\APCu', 'datadirectory' => '/data', 'instanceid' => 'xxxxxxxxxxxxxxx', 'passwordsalt' => 'xxxxxxxxxxxxxxxxx', 'secret' => 'xxxxxxxxxxxxxxxxxx', 'trusted_domains' => array ( 0 => '192.168.1.130:444', 1 => 'website.duckdns.org', ), 'trusted_proxies' => ['swag'], 'dbtype' => 'mysql', 'version' => '23.0.0.10', 'overwrite.cli.url' => 'https://website.duckdns.org/', 'overwritehost' => 'website.duckdns.org', 'overwriteprotocol' => 'https', 'dbname' => 'nextcloud', 'dbhost' => '192.168.1.130:3306', 'dbport' => '', 'dbtableprefix' => 'oc_', 'mysql.utf8mb4' => true, 'dbuser' => 'nextcloud', 'dbpassword' => 'xxxxxxxxxxxx', 'installed' => true, ); Am amI doing something wrong? Thank you, Lev
  8. Good evening. I have been able to restore my docker from the backup, however, I am seeing errors between clients that I cannot fix and am deciding that probably the best way to correct everything is by completely removing and reinstalling all from scratch, including all the dockers. Is there a good guide on to how to remove and then reinstall all dockers and settings correctly? Thank you, Lev
  9. Hope someone can help. I was doing a simple update on the Apps from within the Nextcloud and now the instance is stuck in maintenance mode. Can some one shine some light on this? Here us the log: ErrorWarningSystemArrayLogin [s6-init] making user provided files available at /var/run/s6/etc...exited 0. [s6-init] ensuring user provided files have correct perms...exited 0. [fix-attrs.d] applying ownership & permissions fixes... [fix-attrs.d] done. [cont-init.d] executing container initialization scripts... [cont-init.d] 01-envfile: executing... [cont-init.d] 01-envfile: exited 0. [cont-init.d] 10-adduser: executing... ------------------------------------- _ () | | ___ _ __ | | / __| | | / \ | | \__ \ | | | () | |_| |___/ |_| \__/ Brought to you by linuxserver.io ------------------------------------- To support LSIO projects visit: 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... [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] 70-aliases: executing... [cont-init.d] 70-aliases: exited 0. [cont-init.d] 90-custom-folders: executing... [cont-init.d] 90-custom-folders: 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. [cont-finish.d] executing container finish scripts... [cont-finish.d] done. [s6-finish] waiting for services. [s6-finish] sending all processes the TERM signal. [s6-finish] sending all processes the KILL signal and exiting. [s6-init] making user provided files available at /var/run/s6/etc...exited 0. [s6-init] ensuring user provided files have correct perms...exited 0. [fix-attrs.d] applying ownership & permissions fixes... [fix-attrs.d] done. [cont-init.d] executing container initialization scripts... [cont-init.d] 01-envfile: executing... [cont-init.d] 01-envfile: exited 0. [cont-init.d] 10-adduser: executing... usermod: no changes ------------------------------------- _ () | | ___ _ __ | | / __| | | / \ | | \__ \ | | | () | |_| |___/ |_| \__/ Brought to you by linuxserver.io ------------------------------------- To support LSIO projects visit: 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... [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] 70-aliases: executing... [cont-init.d] 70-aliases: exited 0. [cont-init.d] 90-custom-folders: executing... [cont-init.d] 90-custom-folders: 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.
  10. OK. Sounds good. I'll keep an eye on this drive. Appreciate your help! Lev
  11. So, the extended Smart test reported - completed without errors. However, I see errors in the log. What do I do next about the reported errors? Do I just ignore them? Do I need to re-run parity check? Thanks, Lev tower-smart-20210802-2330.zip
  12. I am running extended test under Fix Common Problems right now. It has been for the last 45 minutes. I'll post the results as soon as it finishes, although I have no idea how long it may take. I'm also running the extended SMART test on that disk. And, yes, the errors were in the Main page, and I got alerted to them because Fix Common Problems also reported them. Thanks, Lev
  13. I just noticed that my Parity 2 disk is reporting errors. I am not sure when those popped up as the parity was just checked and passed. What do I make of these and how to correct them? Thanks. tower-diagnostics-20210801-1505.zip
  14. I think that there are a LOT smarter people here who can guide you. however, because of the holidays, their response may be a bit delayed. In the meantime, try to find the file that you are looking for manually on your server. Your data should not be affected by the troubles with NC docker.
  15. Sorry, I was assuming that you have backup/restore plugin. Do you? If yes, and you have been regularly backing up the dockers... you will have the option to "go back" or restore to an earlier version of the apps/dockers. I am not a techie and my explanation is I am sure lacking. Look under Setting/User Utilities tab to see if you have Backup/Restore Appdata option. If you do not, then I am at loss of what to do next. If you do, restoring will not affect your credentialing.
  16. You data is unaffected, even if you completely remove the NC. You can probably just browse to that folder on your server and retrieve the file that you are looking for manually. So, if you know where your files are stored, such a networked PC, and you have access to it, just browse and find the folder/file to download manually.
  17. I just restored my dockers to a few days ago, and the console is back up and running. If you don't have any other option, try restoring it as well until someone can perhaps shine some light on the "proper" fix.
  18. This morning I am also getting this exact message. Any thoughts on what this is all about and how to go about fixing it? My latest NC is 19.0.6 The Nextcloud.log is HUGE, over 310 MB, and growing all the time!
  19. Is there a way to run a DICOM server on an unRaid, accessible from outside through something like Radiant? I know that there is an app for Nextcloud, but it is a very week solution. Something like Orthanc can run on Windows, but I would like the data to live in an unRaid. Running a VM which is running an Orthanc is a very tedious and slow process. Something native to unRaid would work a lot better. In 2015 there was a thread on this topic but it seemed to end with no true solution. Any guidance would be great. Lev
  20. Oh, beautiful! Thank you. Lev
  21. I just noticed on my server that the letsencrypt is being deprecated and SWAG is the way to go. I know that this maybe a noob question, but is there an easy to follow set of instructions for the migration, hopefully without breaking anything? I hate to mess with something that is working well. Thanks, Lev
  22. I want to update this so that if anyone else is or has been struggling as I have to get the letsencrypt / nextcloud to play nice together can perhaps try these steps. They worked for me to finally get SSL recognized in my browsers. I changed the following value in the nextcloud.subdomain.conf from: proxy_max_temp_file_size 2048m; to proxy_max_temp_file_size 1024m; That seemed to do the trick. I am not sure why that would work but it did. Props go to @Agricola who suggested it here : https://forum.openmediavault.org/index.php/Thread/25212-Not-Able-to-Configure-Remote-Nextcloud/ If someone could explain why this would work, in plain English as I am a noob, it would be helpful.
  23. keep getting the same error while running letsencrypt. I've wiped and reinstalled the docker half a dozen times with the same exact result. The values I am currently using are the same that I used for the last year or two, yet now they do not work. Can someone please shed some light on this. Very frustrating. I was able to generate correct SSL certificate. For some reason I had to reset my port forwarding on the FIOS gateway. Strange that I had to do that as it was working before with no issues. Letsencrypt is all good, with no more errors reporting a valid new certificate. However, the websites still display Not secure with Certificate error. How can I correct that? And, the only way I can get into the nextcloud is by modifying the following line in the config.php to include the port: 'overwritehost' => 'domain1.duckdns.org:444',
  24. So, I reinstalled the mariadb and nextcloud and cannot log into the dns unless I change the following line to include the port. Also, I do not see the SSL certificate anymore. No errors in the letsencrypt log, that I can see. 'overwritehost' => 'mysite.duckdns.org:444', nextcloud.txt
  25. I was reinstalling my letsencrypt, mariadb and nextcloud due to the fact that for some reason I lost all connection to my nextcloud and now, when I install letsencrypt following spaceinvader's tutorial, the log files for the container report that both of my subdomains fail challenges. I have used the same duckdns.org and subdomains for several years with no problem and have installed letsencrypt the exact same way several times. This is the first time I see this error. Am I missing something? letsencryptlog.txt

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.