Jump to content

Leaderboard


Popular Content

Showing content with the highest reputation on 01/10/19 in all areas

  1. 1 point
    Support for HandBrake docker container Application Name: HandBrake Application Site: https://handbrake.fr/ Docker Hub: https://hub.docker.com/r/jlesage/handbrake/ Github: https://github.com/jlesage/docker-handbrake Make sure to look at the complete documentation, available on Github ! Post any questions or issues relating to this docker in this thread.
  2. 1 point
    App name: NowShowing v2 Docker Hub: https://hub.docker.com/r/ninthwalker/nowshowing/ Github: https://github.com/ninthwalker/NowShowing Wiki: https://github.com/ninthwalker/NowShowing/wiki (A lot of good info) The NowShowing docker provides a summary of new media that has recently been added to Plex. You can select to have it generate an email and/or create a web page for your users to visit. NowShowing is the successor of the popular plexReport docker. The original brainchild of bstascavage (https://github.com/bstascavage/plexReport). Further developed by NinthWalker & enhanced by GroxyPod, NowShowing adds additional improvements and features in a friendly, easy to install docker. Note: v1 is still available, however all work and updates are being done on the new v2. It is recommended to do a fresh new install of NowShowing v2. New for v2: Same great Email/webpage as v1 All new Web Interface for settings and customization Library Filtering! Tautulli Statistics Integration New user Setup Wizard Announcement Emails Easy Plex token retrieval Most email providers supported BCC users instead of multiple emails Password protected with Fail2ban support On-Demand and Test reports Web Log Viewer Bug Fixes & Quality of life enhancements _________________________________________________ Installation: Preferred installation method: From the Community Applications 'APPS' section in unRAID. Install the new "NowShowing v2" app. You can also install by adding the following template repository: https://github.com/ninthwalker/docker-templates/
  3. 1 point
    If you have parity2 then any change to disk assignments would require rebuilding parity2. For parity1 it doesn't matter. As long as you keep all the same disks and don't add, remove or replace any then parity1 is valid however you assign the data disks. Tools - New Config, Retain All. Reassign disks as you wish (don't assign a data disk to parity slot obviously). Check parity valid box and you're good to go.
  4. 1 point
    Who are you going to pay?
  5. 1 point
    Or you could probably add this as a repository on the docker page https://github.com/Josh5/unmanic/tree/master/docker
  6. 1 point
    If you google SMART attributes explained you'll get several results. Once a month is usually considered enough.
  7. 1 point
    A $70 increase to pro tier pricing would not cover the cost of staffing required to provide the phone support you suggest either. Not something we are considering at this time. Sent from my Pixel 3 XL using Tapatalk
  8. 1 point
    There's nothing on those logs about controllers issues, so it's likely not that, it could be related to this: Dec 19 13:23:46 Knowlage kernel: resource sanity check: requesting [mem 0x000c0000-0x000dffff], which spans more than PCI Bus 0000:00 [mem 0x000c4000-0x000c7fff window] Dec 19 13:23:46 Knowlage kernel: caller pci_map_rom+0x68/0xaf mapping multiple BARs Dec 19 13:23:46 Knowlage kernel: resource sanity check: requesting [mem 0x000c0000-0x000dffff], which spans more than PCI Bus 0000:00 [mem 0x000c4000-0x000c7fff window] Dec 19 13:23:46 Knowlage kernel: caller pci_map_rom+0x68/0xaf mapping multiple BARs Dec 19 13:23:46 Knowlage kernel: vfio-pci 0000:65:00.0: vgaarb: changed VGA decodes: olddecodes=io+mem,decodes=io+mem:owns=io+mem But VMs are not my forte and I don't really know what the above means, it could be harmless.
  9. 1 point
    Did you follow the directions at the top of the sample conf file? Once set up, you're supposed to access nextcloud through your domain not the local ip, because it will redirect everything to your ip. If you're seeing the welcome message, you have an issue with a redirect. Clear your browser cache, then recheck your settings.
  10. 1 point
    Yes Broadcom is LSI, any HBA with a SAS2008/2308/3008 chipset in IT mode, e.g., 9201-8i, 9211-8i, 9207-8i, 9300-8i, etc and clones, like the Dell H200/H310 and IBM M1015, these latter ones need to be crossflashed.
  11. 1 point
    Try this, it worked for me for an identical error, on the flash drive edit syslinux/syslinux.cfg and add root=sda to the boot option you're using after initrd=/bzroot, e.g.: label Unraid OS menu default kernel /bzimage append initrd=/bzroot root=sda
  12. 1 point
    Disk3 has a reallocated sector, it appears that was some time ago, so as long at it remains stable it should be fine for now, a couple of read raw errors here and there on the other disks but nothing to worry about for now.
  13. 1 point
    The default should appear if you delete it and restart the container.
  14. 1 point
    Definitely. If you can document the process needed to get the database manager usable in a docker image that runs on any linux, but unraid specifically, that would be great.
  15. 1 point
    Humor me a bit and try running it again with 5. If that still gives you an error I'll update the plugin with a more lax timeout
  16. 1 point
    I was reading through this thread thinking it was 10 years old..but it’s rather new! I feel the pain all around but have a glimmer of hope; I’ve been running the QB Enterprise Server on Linux for years now for multi-users and it rather “stable”. Now it was a pain in the ass, docu,entatikn is next to nothing, and the last 10 years Intuit’s support (including enterprise support) does not cover how to actually install and manage their software. I went as far as contacting them asking for support on version 2014 only to be told they didn’t have a Linux install... Christ their documentation doesn’t even change between versions, they just update the date and version number. Ok, enough complaining, on to the important bits. I’m about to roll out QB Enterpise 2019 on a Linux box and wouldn’t mind writing my own documents on it for others to use. My end goal is to containerize it and try to automate it from version to version, along with management controls for sys-admins. Any interest?
  17. 1 point
    Welcome to MarkusMcNugens docker repo support topic! I'll be adding more docker containers over time, and will provide support for the containers below. qBittorrentvpn Overview: Docker container which runs the latest headless qBittorrent client with WebUI while connecting to OpenVPN with iptables killswitch to prevent IP leakage when the tunnel goes down. Reason: I put this container together because I couldn't find a qBittorrent docker that supported dropping in your own ovpn files like Binhex's containers do. All of them had prebuilt configuration files which aren't as user-friendly when your VPN provider isn't included. Base: Ubuntu (Will have an Alpine based build in the somewhat near future, took the summer off and never worked on it) Tags: bionic/latest (403MB) Automated Build: Yes Application: https://www.qbittorrent.org/ Docker Hub: https://hub.docker.com/r/markusmcnugen/qbittorrentvpn/ Github: https://github.com/MarkusMcNugen/docker-qBittorrentvpn Note: Default WebUI credentials can be found on the Github and Docker Hub descriptions. Note 2: qBittorrent throws a Origin header & Target origin mismatch if trying to open the WebUI in unRAID with the WebUI menu link if Cross Site Request Forgery protection is enabled in the settings. This is disabled by default on new installations, on updated dockers you can edit this via the WebUI options within the WebUI or by editing the qBittorrent.conf config file and adding "WebUI\CSRFProtection=false" to it. Note 3: qBittorrent will throw a WebUI: Invalid Host header, port mismatch error if you use port forwarding with bridge networking due to security features to prevent DNS rebinding attacks. If you need to run qBittorrent on different ports, instead edit the WEBUI_PORT_ENV and/or INCOMING_PORT_ENV variables AND the exposed ports to change the native ports qBittorrent uses. (This is actually working now!!!) OpenConnect VPN Server Overview: OpenConnect VPN server is an SSL VPN server that is secure, small, fast and configurable. It implements the OpenConnect SSL VPN protocol and has also (currently experimental) compatibility with clients using the AnyConnect SSL VPN protocol. The OpenConnect protocol provides a dual TCP/UDP VPN channel and uses the standard IETF security protocols to secure it. The OpenConnect client is multi-platform and available here. Alternatively, you can try connecting using the official Cisco AnyConnect client (Confirmed working on Android). The Dockerfile was written to always download and compile the latest release of OpenConnect VPN server when built. Reason: You can never have too many kinds of VPN servers! I forked ocserv from TommyLau and updated it to the latest version of Alpine and OpenConnect Server. I made the container have persistence for configuration files, drop in your own certs if you'd like or have the container make them for you, and advanced configuration for power users that know what they are doing, and numerous other enhancements. Base: Alpine Edge Automated Build: Yes Size: 57.1MB Application: https://ocserv.gitlab.io/www/index.html Docker Hub: https://hub.docker.com/r/markusmcnugen/openconnect/ Github: https://github.com/MarkusMcNugen/docker-openconnect SFTP Server Overview: Easy to use SFTP (SSH File Transfer Protocol) server with OpenSSH and Fail2ban installed for extra hardening against brute force attacks. Forked from atmoz/sftp. Reason: I was using atmoz/sftp as an sftp docker container exposed to the internet for some friends to access and realized there was no banning mechanism included. I was getting hammered by brute force attacks so I forked his github repo and modified the image to include fail2ban, made some entrypoint modifications so files can be easily added/edited/viewed from the /config volume. Base: phusion/baseimage Automated Build: Yes Size: 236MB Application: https://www.openssh.com/ Docker Hub: https://hub.docker.com/r/markusmcnugen/sftp/ Github: https://github.com/MarkusMcNugen/docker-sftp Note: Please read the Github or Docker Hub descriptions. While this container is easy to use, it does require some small configuration.
  18. 1 point
    OK, I finally got the Dell H310 properly flashed to the 20.00.07.00 9211-8i IT firmware. I had to manually run the "megarec -cleanflash 0" as well as the P7 sas2flash with the 6GBPSAS.FW. After that, I just picked up with 3.bat (some redundancy with prior steps) and all batch files ran in sequence without error. The cards is now flashed and functional. Thanks for the tips. Reading back to the beginning of this page pointed me in the right direction as I saw exactly what @Fulcrum77 saw and the replies to him help me get it worked out.
  19. 1 point
    Putting this here because probably the most people will set it. Due to the crisis in the computing industry over Meltdown, Spectre, and the like, operating system developers have been working diligently with academia, CPU developers and hardware manufacturers to provide solutions. Some of these solutions require both hardware changes in the form of CPU microcode and software changes in the form of operating system and other subsystem mitigations. Despite what might be reported in the press, this work is ongoing. Probably everyone is familiar with the warning from motherboard providers: "Do not update your bios unless you are experiencing a problem." However some changes in the latest OS releases require corresponding bios updates. AMD is particularly affected because they don't typically provide "early microcode update" as part of OS start up like Intel does. Case in point: Everyone has to decide for themselves whether to attempt bios update, and take responsibility if something fails and you brick your motherboard. But particularly if using Virtual Machines, we highly recommend keeping your bios updated, especially for AMD platforms.
  20. 1 point
    what?!?! did you read it or what? you quoted my statement "not my creation just found it on google" seriously man, like, im speechless edit: your github was forked by "bassrock" I don't know how to fork or code or do any of this crap. all the files I tested with was from bassrock, https://raw.githubusercontent.com/bassrock/Unraid-NVIDIA-Plugin/master/plugins/UnraidNVIDIA.plg https://github.com/bassrock/plex-nvidia-docker https://hub.docker.com/r/bassrock/plex-nvidia-docker
  21. 1 point
    Scheduled for Unraid OS 6.7 release.
  22. 1 point
  23. 1 point
    One SATA cable to power 15 disks? That's a truly huge startup current to handle. With 2 A startup current, it's 30 amps to handle during startup. In general, you should avoid going over 8A / connector pin for Molex-type connectors. Each contact pin can handle up to 11 A but the cables used are normally dimensioned for 6-10 A. And avoid going over 1.5A / connector for SATA-type connector pins.
  24. 1 point
    Thanks a lot for your posts! I got it working! For anyone else looking for a way to do this in the future, here you go: I am assuming you have a domain that you want to serve as an access point to a container on your server. Let's assume your domain is www.dexter.com and you want to access books.dexter.com Your CNAMES should be: Host Record Points to TTL books yourname.duckdns.org 14400 Feel free to add as many of these CNAMES as you'd like. I am using duckDNS because it has a container that I can run on my server. What I think it does is when my IP changes, my unRAID server sends an update request to duckDNS to make sure my url (ie yourname.duckdns.org) is still pointing to my IP. If you dont have something similar with your dns service, i think you will need to manually update it everytime your ISP updates your IP (maybe someone can correct me here). Next, you go to letsencrypt's docker and you put this: Domain Name: dexter.com (dont put your dns here) Subdomain(s): books (if you ever want to add future subdomains, remember to add them here) Only Subdomains: true Validation: http (People of the future, refer to documentation to see if this is still the correct way to do this) Now, navigate to appdata\letsencrypt\nginx\site-confs\ and open default. These are the configs that I am using and it seems to be working perfectly. Obviously change dexter.com to your domain and change the local IP and ports with whatever you are accessing. This was adapted from https://technicalramblings.com/blog/how-to-setup-organizr-with-letsencrypt-on-unraid/ so if you have anything more complicated you wish to do, go there and there are templates. default: ################################################################################################################ #////////////////////////////////////////////////SERVER BLOCK\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\# ################################################################################################################ # REDIRECT HTTP TRAFFIC TO https:// server { listen 80; server_name dexter.com .dexter.com; return 301 https://$host$request_uri; } ################################################################################################################ #////////////////////////////////////////////////MAIN SERVER BLOCK\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\# ################################################################################################################ # MAIN SERVER BLOCK server { listen 443 ssl http2 default_server; server_name dexter.com; ## Certificates from LE container placement ssl_certificate /config/keys/letsencrypt/fullchain.pem; ssl_certificate_key /config/keys/letsencrypt/privkey.pem; ## Strong Security recommended settings per cipherli.st ssl_dhparam /config/nginx/dhparams.pem; ssl_ciphers 'ECDHE-RSA-AES128-GCM-SHA256:ECDHE-ECDSA-AES128-GCM-SHA256:ECDHE-RSA-AES256-GCM-SHA384:ECDHE-ECDSA-AES256-GCM-SHA384:DHE-RSA-AES128-GCM-SHA256:DHE-DSS-AES128-GCM-SHA256:kEDH+AESGCM:ECDHE-RSA-AES128-SHA256:ECDHE-ECDSA-AES128-SHA256:ECDHE-RSA-AES128-SHA:ECDHE-ECDSA-AES128-SHA:ECDHE-RSA-AES256-SHA384:ECDHE-ECDSA-AES256-SHA384:ECDHE-RSA-AES256-SHA:ECDHE-ECDSA-AES256-SHA:DHE-RSA-AES128-SHA256:DHE-RSA-AES128-SHA:DHE-DSS-AES128-SHA256:DHE-RSA-AES256-SHA256:DHE-DSS-AES256-SHA:DHE-RSA-AES256-SHA:AES128-GCM-SHA256:AES256-GCM-SHA384:AES128-SHA256:AES256-SHA256:AES128-SHA:AES256-SHA:AES:CAMELLIA:DES-CBC3-SHA:!aNULL:!eNULL:!EXPORT:!DES:!RC4:!MD5:!PSK:!aECDH:!EDH-DSS-DES-CBC3-SHA:!EDH-RSA-DES-CBC3-SHA:!KRB5-DES-CBC3-SHA'; ssl_prefer_server_ciphers on; # Custom error pages error_page 400 401 402 403 404 405 408 500 502 503 504 $scheme://$server_name/error.php?error=$status; error_log /config/log/nginx/error.log; } ################################################################################################################ #////////////////////////////////////////////////SUBDOMAINS\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\# ################################################################################################################ #CalibreWeb SERVER, accessed by books.dexter.com server { listen 443 ssl http2; server_name books books.dexter.com; location /error/ { alias /www/errorpages/; internal; } location / { proxy_bind $server_addr; proxy_pass http://LOCAL-IP:PORT; proxy_set_header Host $http_host; proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; proxy_set_header X-Scheme $scheme; } } #Copy + Paste the same "CalibreWeb SERVER" block if you want to add another domain such as plex. It may require a different set up though. Thank you everyone for your help!
  25. 1 point
    Your problem is the USB enclosure you're using it's reporting the same serial for several disks: Dec 8 05:06:22 Microserver emhttp: Hitachi_HDS723030ALA640_152D00539000-0:2 (sdd) 2930266532 Dec 8 05:06:22 Microserver emhttp: HITACHI_HUA723030ALA640_152D00539000-0:3 (sde) 2930266532 Dec 8 05:06:22 Microserver emhttp: Hitachi_HDS723030ALA640_152D00539000-0:0 (sdb) 2930266532 Dec 8 05:06:22 Microserver emhttp: Hitachi_HUA723030ALA640_152D00539000-0:1 (sdc) 2930266532 .... Dec 8 05:06:22 Microserver emhttp: Error: disk10: 152D00539000-0:0 already assigned Dec 8 05:06:22 Microserver emhttp: Error: disk11: 152D00539000-0:0 already assigned Dec 8 05:06:22 Microserver emhttp: Error: parity2: 152D00539000-0:0 already assigned To be honest I don't know how you got the other 3 working.