Leaderboard

Popular Content

Showing content with the highest reputation on 12/23/20 in all areas

  1. Developer / Maintainer Profiles CA supports developer profiles. This allows a user to look at and compare the developers who are creating / supporting the various containers / plugins. In order to take advantage of this, create a file within your template repositories called ca_profile.xml For most developers, the profile would be something akin to: <?xml version="1.0" encoding="utf-8"?> <Maintainer> <Icon>https://raw.githubusercontent.com/ich777/docker-templates/master/ich777/images/avatar.jpg</Icon> <Profile> Creating Docker containers with a little different approach than most developers, the container only has the dependencies installed and also the start script and downloads the application itself on the first start and updates the application on every start/restart of the container. </Profile> <DonateLink>https://www.paypal.me/chips777</DonateLink> <DonateText>If you like my work please consider Donating.</DonateText> </Maintainer> However there are also other entries which can be utilized if so desired: <Forum> - A link to a forum page here (announcement thread, general support thread etc) <WebPage> - A link to a webpage you operate <Facebook> - A link to a facebook group / page <Reddit> - A link to a reddit group <Discord> - A link to a discord site <Twitter> - A link to a twitter page Whenever a user happens to look at the repositories that are present in any given search result, the ones which have the profile filled out are displayed first in the list.
    5 points
  2. Hello @DemonWarrior, it is okay to use the version you prefer, no one can say anything about that as it is your decision. But this went way to far here. @ich777doesn't have to admit anything to you. You want to use something he provided to the community. If you want to benefit from that just update. If you don't want to update you miss an oppertunity here. But its your decision, not his... You should rather appreciate what he does for the community.
    4 points
  3. @DemonWarrior I don't get it man.. you're mad because @ich777 won't bend over backwards for you for an old release? @ich777 is a non-paid community developer sharing his hard work and time with us for free. If anything you should be more respectful and have a thankful attitude for what he has done. I know I am. I don't think you're looking at the big picture here with all those accusations. Ease up, not everybody is out to get you..
    2 points
  4. @ich777 don't let DemonWarrior get under your skin. Some people just don't understand the difference between community apps and software companies. Its like getting mad at a software developer for not making it backwards compatible with windows XP. Tones of people still use it and refuse to upgrade to a newer windows version. This is not a developers issue, it theirs for not wanting to upgrade. I am sure you would rewrite the script if you were getting paid to do so. But why waste your time when you do it for free and only a small handful of people might need it. I see he keeps referring to personal reasons, wonder what they are. Seems kind of fishy.
    2 points
  5. Who is we? I don't rewrote the script from them, I have to learn/discover all myself because I mainly needed a way to integrate the Nvidia drivers and also DVB drivers into one image. You can also use the prebuild 6.8.3 from the first post that I made, keep in mind you can only choose between things that are available. That's a thing you have to ask linuxserver.io. They don't have to shutdown their plugin but they did. This is not a Plugin this is a Docker Container where you can compile custom builds for Unraid with whatever you want. Linuxserver never made their sourcecode available to the public, can't help with that, I stand in no relation to them. Sorry don't get me wrong, but why should I rewrite the script for an outdated version of Unraid, I'm currently on Unraid 6.9.0 RC2 and I love it so far, this is not my only Container that I have to maintain here and I'm not interested in making modifications, as I said, for an outdated version (only to let you know this would mean I had to downgrade to 6.8.2 to test everything if it's working correctly and I'm really not interested in that because it's really time consuming and I got a life too ). This is completely out of context, I have to present nothing only because someone pulled his Plugin from the CA App... This is also out of context, if someone leaves and deletes his content I'm not responsible for that. No, I said I won't rewrite the script for 6.8.2 I'm also no fool... Sorry but this is a dead end, I won't rewrite the script.
    2 points
  6. Hello Unraid Community, I made a beginners guide/tutorial to install/setup Unraid (It was using v6.6.6). I cover the following topics: USB Key - 18:00 BIOS - 3:42 Disk Array - 4:56 Parity Check - 10:30 Format Drives - 11:03 Single Share - 11:38 PSA - 21:11 Security - 22:11 Share per Media Type - 28:43 APC UPS - 40:36 10 Gigabits/Second Transfer Test - 43:11 Share Troubleshooting - 44:41 I hope it helps those looking for some initial direction to get started and be inspired to continue their Unraid journey. How to Install & Configure an Unraid NAS - Beginners Guide
    1 point
  7. As always, prior to updating, create a backup of your USB flash device: "Main/Flash/Flash Device Settings" - click "Flash Backup". Hopefully spin-up/down sorted: External code (docker containers) using 'smartctl -n standby' should work ok with SATA drives. This will remain problematic for SAS until/unless smartmontools v7.2 is released with support for '-n standby' with SAS. SMART is unconditionally enabled on devices upon boot. This solves problem where some newly installed devices may not have SMART enabled. Unassigned devices will get spun-down according to 'Settings/Disk Settings/Default spin down delay'. Updated to 5.10 Linux kernel (5.10.1). Updated docker. Fixed bug joining AD domains. Version 6.9.0-rc2 2020-12-18 (vs -rc1) Base distro: bind: verison 9.16.8 docker: version 19.03.14 krb5: version 1.18.2 Linux kernel: version 5.10.1 Management: emhttpd: fix external 'smartctl -n standby' causing device spinup emhttpd: enable SMART on devices upon startup emhttpd: unassigned devices spin-down according to global default emhttpd: restore 'poll_attributes' event callout smb: fixed AD join issue webgui: do not try to display SMART info that causes spin-up for devices that are spun-down webgui: avoid php syntax error if autov() source file does not exist
    1 point
  8. While the current system is great for the average home network as a media server storing non-critical and non-confidential information on a private network, with a few changes, it could be ready for so much more... Where I'm coming from: I'm new to unraid, and I am a long time Linux-user with widows as a side OS I avoid as much as possible. Currently I've been setting up a VFIO system, and because I won't just be using it to store media but to actually be my daily driver, I have certain security concerns with the current default configurations. The following is a list of changes I've compiled, largely from http://kmwoley.com/blog/securing-a-new-unraid-installation/ and somewhat ordered by importance: - SMB 1 disabled by default - FTP and Tellnet disabled by default - HTTPS enabled with a self-signed cert out of the gate (love the cert authority setup though!) - make it more clear how to encrypt new drives (can't choose to encrypt when adding the device, has to be changed in the default filesystem setting) - new shares not exported by default, and when exportrd, Private by default - Don't export the USB boot media!!! (At least not by default and add an are you sure if you try to enable it) - firewall such as UFW installed and enabled by default with only TCP port 80 and 443 set to LIMIT and whatever SMB uses opened. GUFW could be pulled from for the GUI. And providing quick check boxes for common ports would make it easy, possiblity auto enabling when you enable a core service. - Docker Isolation through Linux namespaces / subuids - allow tagging more shares for direct Linux VM mounting to prevent the need to pass through /mnt/user - better multiple-user support, it's a server, right? So people other than root should be able to ssh in and access the UI; ideally root login would be disabled with use of a wheel group instead - don't use 777 permissions by default, ideally users + groups, but at a minimum there is no reason for most things to be read, write, and execute by default! - support for openvpn - support for multiple different encryption keys And add other lurking issues to this. Even if you're not exposing a system to the public internet, a lot of these things can still cause problems if the system is up 24/7. There is no such thing as a "friendly environment" outside air-gapped systems, and my daily driver will definitely not be air gapped. Anyway, if you've made it this far and feel like this is a list of complaints, I'm sorry. I do like unraid and I already feel excited for where it's going.
    1 point
  9. The latest Unraid blog highlights all of the new major changes in Community Applications 2020.12.14 including: New Categories and Filters Autocomplete Improvements Repositories Category/Filter Community Applications now viewable on Unraid.net As always, a big thanks to @Squid for this amazing Unraid Community Resource! https://unraid.net/blog/community-applications-update
    1 point
  10. thats fine i already reached out to them. Im just baffeled i gave you as a developer mutliple chances to admit fault. Thats fine i really dont care what your beliefs are. All im saying is this is 100% wrong. I meant we as in the commuity. Something is more than fishy with these statements. You can find on this direct forum Unraid-Nvidia-Plugin was one day shutodown no notice. They just say it will no longer be supported. They also seemed really angry that they were having to depreciate the repo. Im pretty sure it wasnt a choice they had bud. You can say whatever you want. I was hoping you would be a bigger person and admit that you wont develop for 6.8.2 or any other beside 6.8.3 or higher becuase unriad told you not to which is the in fact case. Because i know what security flaw your are talking about and I paid for my version of unraid and i feel its not okay that all of us are getting punished for a few bad apples that found the vulnerability. So unraid decided as a COMPANY not a sole community they would deal with it by patching the security flaw and dropping all support for anyone that doesnt upgrade to 6.8.3 version or higher. I dont understand how as a company who has a big opensource community you would shaft a majority of the open source community by make only certain services allowing to use your software for updates and current software development. I know its not your fault and im pretty sure your no the one enforcing this. But im my mind this business practice is no better than Google, Apple, Microsoft, Comcast or any other monopolized market we have now a days. Again this is not against you im directing this. I just dont understand how no one has got outraged by this in general.
    1 point
  11. This is the usecase of most users here. No because I have to rewrite the container or better speaking the script. Yes you have the right to choose, but please don't compare me to anything like Google, Apple or Microsoft... This is a community driven project and stands in no relation to Unraid itself. You can stay on whatever version you want. EDIT: Keep in mind that Unraid implemented the Nvidia driver feature at version 6.9.0beta35+ before that everything was community driven as I said above, I even recommend in the first post to upgrade to 6.9.0beta35+ because it's easier to install.
    1 point
  12. Did the issue appear after connecting a usb device/stick? If so I found the issue didn't happen if the drives where spun up. So you can uninstall UD to stop the auto discovery which now does a call to unraid for it to update the disks or make sure the array is spinning whilst plugging/unplugging devices. Hopefully Limetech will be fix for rc3.
    1 point
  13. This is a known bug, just released an update that fixes that.
    1 point
  14. Or if they're containing data, then the Unassigned Devices Plugin.
    1 point
  15. That's not a supported version, 6.8.3 is the oldest version actively supported. If there is something in 6.8.3 that doesn't work with your setup, try the latest 6.9 release candidate. It's not a good idea to stay with that old of a release anyway, there are vulnerabilities that are fixed in the newest versions, and you will need to eventually go to the 6.9 series anyway, so if there is some incompatibility with the current 6.9 release candidate with your setup it would be good to get that addressed with limetech before the 6.9 release. That's not going to happen, for the reasons I just stated.
    1 point
  16. I get decent speed with ovpn. Never tried wireguard. Perhaps someone else can answer that.
    1 point
  17. You may want to backup all your .torrent files so you don’t loose them if you misconfigure the new qbittorrent app. Just saying 😁.
    1 point
  18. Thanks for posting it here. I'am facing exactly the same issues as you mentioned on 6.9.0-rc2. I thought I had broke something on my own fault. Happy to hear it is (again) a release issue from Plex. Let's hope it will be fixed quickly.
    1 point
  19. its a requirement from PIA, you need to rebind every 15 mins in order to keep the port assigned, otherwise it will be removed and re-assigned to the pool.
    1 point
  20. 1060 Super specifically has Turing NVENC the non super 1060 doesn't. 1660s are Turing far as I am aware Atleast the one I have coming is
    1 point
  21. Correct, it only works currently on cache. It will need to be upgraded and I'll have a look at that.
    1 point
  22. Steam oauth was down for a while - working now!
    1 point
  23. Turbo write has nothing to do with disk size, it parity check is failing and the server locking up there are other issues.
    1 point
  24. Ah. I am still on the latest stable version of unraid. I think my problem is that whenever I try to use apk, it says that it is not installed for me. I guess I will look in to GUS as well.
    1 point
  25. That is 10 times as large as should be needed. And you want appdata and system shares to stay on cache so docker performance won't be impacted by slower parity. And if they are on the array disks will stay spunup because these files are always open. And mover can't move open files, but you shouldn't want to move them from cache anyway. If possible before rebooting and preferably with the array started Go to Tools - Diagnostics and attach the complete Diagnostics ZIP file to your NEXT post in this thread.
    1 point
  26. If you had the disk as a UD disk at any time, UD will show it as missing because it is in the array now. Just remove the historical configuration and UD will forget it.
    1 point
  27. @ich777 Hey, I downloaded and setup your CSMM 7dtd container with reverse proxy pointing to my domain. I believe I have all that setup correctly as I have no issues hitting the CSMM homepage from both Unraid and externally via the web. However, when I click "Get Started" to get connected with Steam I get the following error. Have you seen this before? I wonder if it's actually down for maintenance or it's something else since it's my first time setting this up. Thanks for any help. Edit1: I don't see anything in the CSMM logs that point to anything wrong, only that it's trying to redirect to /sdtdserver/addserver since I'm not logged in. Edit2: Looks like from Googling, steam has maintenance every Tuesday. I'll wait!
    1 point
  28. Keine Ja. Nur die BX500 gilt es zu meiden (kein DRAM). - bei RAID0 hättest du volle 10G LAN Bandbreite (wenn vorhanden) - bei RAID1 hättest du mehr Ausfallsicherheit, da noch nicht vom Mover bewegte oder schlicht ignorierte Dateien bei SSD Ausfall sonst verloren gingen.
    1 point
  29. Thanks to ich777 for taking time out of his day to do some troubleshooting on my issue. Turns out, this behavior (Nvidia transcoding processes terminating when changing playback quality from inside the Web Player) is consistent across multiple client browsers and server platforms -- including Windows. This indicates that it's a Web Player issue, and has nothing to do with the Nvidia Drivers plugin. All other clients are playing just fine. I created a ticket on the Plex Forum to report this issue, which has been experienced by others. Thanks again to ich777 for his help! The plugin is working great.
    1 point
  30. Oh, das hab ich gar nicht bemerkt. Dann würde ich das auch nicht nehmen. Nichts geht über werkzeuglos. Unraid erstellt eine virtuelle Festplatte namens "docker.img". Diese ist standardmäßig unter "/mnt/user/system/docker/docker.img" zu finden. Also im Share "system". Daher empfiehlt es sich diesen Share mit dem Cache "Prefer" zu versehen. Also dauerhaftes Ablegen auf der SSD. Dieses "docker.img" enthält aber nur den Docker Dienst und keine Nutzerdaten. Die sind sauber getrennt und liegen im Verzeichnis "/mnt/user/appdata/ContainerName" bzw diesen Pfad kann man bei jedem Container selbst noch ändern. Auch bei dem Share "appdata" empfiehlt sich also "Prefer" bei der Cache-Einstellung. Dann läuft Docker ausschließlich auf der SSD
    1 point
  31. I was having a similar issue. When I would reboot the server, plugins would be able to install again. That is until I rebooted the server and it didn't boot properly. Turned out it was a flash drive issue, plugins were failing when trying to write to the USB, and ultimately the USB was so corrupted it failed in creating the file system on boot. I'd make a backup of my flash drive ASAP, just in case it's failing.
    1 point
  32. You can switch to PIA’s next-gen servers to correct your connection issues but this will also require upgrading the docker container (and the Deluge app) to the latest version. You will likely see the original issues with Deluge return since it’s probably still the same version you originally had issues with. I switched docker containers instead. I’m now using binhex-qbittorrentvpn docker with the PIA next-gen servers until Deluge releases an update that hopefully fixes some of their bugs.
    1 point
  33. @limetech Here's what I did: Deleted the two files from /boot/config: rsyslog.cfg rsyslog.conf Rebooted Started the Array Reconfigured the Syslog settings Hit Apply Checked the Syslog and saw that rsyslogd started Verified that there was a file in my share Verified that data was in the file
    1 point
  34. @GaLaReN, I've got a working one with a RTX 2080 passed through
    1 point
  35. I found the Driver he's talking about Browse My Computer Let me pick from list System Devices *then the missing step above* On left do (Standard System Devices), Then on the right "ACPI Processor Container Device" This gets me to AntaresUK's solution, of selecting the driver he specifies that people couldnt find. HOWEVER, I still get the different icon, but still "Unknown Device" shown by DrJake. So its not a true resolution.
    1 point
  36. Stop the container, delete the photoprism folder from your appdata directory and start it again.
    1 point
  37. That looks pretty good.. you should upload your script for us! I can't help ya on this because I don't know how to implement the themes, but you might be able to gain some insight by dissecting the current theme plugin and see how it applies stuff on a permanent basis. You can download the plugin file and extract it like a zip file to see how it's put together.
    1 point
  38. ok, one more to go. As @Kash76 has a failure of 99 - iam only having a "failure" of 1. As we both having a crucial ssd I found out (but not 100% sure) that iam just reached the 1% of the lifetime of, of course, 100%. The SSD of @Kash76 should be actually dead with the value of 99. Than, it might be really nothing to worry about - yet.
    1 point
  39. It means the SSD reached the estimated life, it doesn't mean it's failing, it can work for a long time without issues, you can acknowledge the SMART attribute by clicking on the dashboard warning.
    1 point
  40. You dont need to run 2 instances, just map your movies folder and kids_movies so do something like this in your docker setup ( depending on how your shares are setup ) /movies -> /mnt/user/movies /kids_movies -> /mnt/user/kids_movies Then in Radarr add a movie and in the path dropdown when your adding kids movies you would choose kids_movies and other movies you would choose movies If you do not see movies or kids_movies in the dropdown then choose the select different path option and click the folder button to search for path and find the movies or kids_movies path
    1 point