Mik3

Members
  • Posts

    15
  • Joined

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

Mik3's Achievements

Newbie

Newbie (1/14)

12

Reputation

  1. Updated from RC7. No issue so far with VPN (wireguard) or any of the docker except: Upon update the reboot wasn't successful, the system was hanging (I don't have any error/info as no monitor is attached). After 552 secs, I did a normal power down (pressing the power button and the system immediately shut down, like when no boot device found) and restart, one of the btrfs disk cache was missing (again as I did have the same issue upon reboot on the rc4/5). I shut down, changed sata port on the card and reboot. Same issue so I removed the device as the cache was raid 1 anyway so no data loss but I am not sure if the problem is my disk or the update as, as stated before, I had the issue before. The disk shows correctly under unassigned devices now that it has been removed from the cache pool. The only SMART error I have on the drive is the UltraDMA CRC that occurred after I removed the drive. I don't have diagnostics as I did 2 reboot after the changes and forgot to save what happened, however no info/issue in the system log as far as I remember. Hopefully the explanation makes sense. If not please let me know and I try to rephrase it.
  2. Oh I didn't know it was already reported.. I must have missed it. Apologies. I don't want to switch it to none (default) as I won't be able to see my docker in the folder. I can wait for a fix. Thanks again for your time.
  3. To be honest the RC4 is quite stable and I prefer to have the security fixes in place.
  4. Upgraded from rc3, no major issue however: 1) When viewing system log using the "log" button on top right side of the UI the log is displayed with white font on black background (before was black font on white background). Would be nice if this respect the "UI theme". 2) When I click on the docker to try to access the submenu I can't see the various options which should appear on the left white space (WebUI, restart, ...) Below a screenshot. I use DOCKER FOLDER and the issue is present using either MS Edge on windows with NO adblock and on Android using chrome. If I open the folder and I click on the docker I can actually see the options. Sometimes changing tab and then returning to it temporary solves the issue. Looks like a graphical glitch related to the docker folder plugin but I don't know if it is related to the rc4 release. If not apologies that I reported it here.
  5. Correct me if I am wrong but: 1) You can have different user for your SMB share. 2) You can have different user for SSH 3) You have "Docker user". Some containers are set up to allow you to specify a UID/GID to be used by passing it in as an environment variable. Probably not easy and the need for multiple vulnerability/misconfiguration but docker can be "escaped". Ex.: Consider a RCE that gives you access to a docker and from there you could possibly escape the container or if the container allows you to have "user" access to a folder, with the above vulnerability you can make it to root. Now my opinion is that regardless the vulnerability the system needs to be fixed. Security is like an onion, if too many layers are missing, the chances of something bad happening is increased. What we need is the possibility to avail of the latest security patches without waiting for a major/RC release. This topic has been brought up already before and I hope limetech will implement the changes quite fast.
  6. Thanks for your reply. The plugin came out after I wrote this guide. When I have the time I'll edit/write a new one with the updated steps. With the phrase "Just follow the instructions" I was referring to follow the topic you wrote for the NVIDIA driver as the guy is using AMD+NVIDIA so Intel-GPU-TOP is NOT applicable.
  7. @dkerlee Thank you for the nice comments. Regarding your hardware may I suggest to have a look at the NVIDIA driver plugin (coomunity apps) from the amazing @ich777. This is a link to the forum post https://forums.unraid.net/topic/98978-plugin-nvidia-driver/ This allows you to use the nvidia driver into the docker container. Just follow the instructions, then use emby settings to use the gpu for transcoding and you shouldn't have any issue. Let me/us know how it goes and if you had to take any particular steps to make it working so other can benefit as well.
  8. Mik3

    Merry Christmas

    Heeyy all, just wanted to wish a merry christmas to the whole unraid community and devs. Keep up the great work and stay safe! All the best 🎅
  9. I wasn't sure if unraid was using Apache or not that's why the question. Thanks a lot for your reply.
  10. Dear devs and member, I would like to know if unraid is vulnerable to the new APACHE vulnerability (not talking about log4j). The CVEs are the one in the subject, links to nist below. If vulnerable will an update be available soon to fix those CVE and improve the product security? https://nvd.nist.gov/vuln/detail/CVE-2021-44790 https://nvd.nist.gov/vuln/detail/CVE-2021-44224 Thank you. Merry christmas
  11. Hi, Thanks for the reply. Despite I read the release notes etc, as it was pointed by someone else not everything is clear. Regarding your statement, about facebook etc, doesn't really makes any sense. First your assumption might be wrong. The fact that million people uses facebook doesn't mean I do. Also the fact someone trust facebook doesn't mean he/she has to trust microsoft, apple and so on. With these I mean NO disrespect to limetech, actually I trust them so far as they proved to be reliable both with their OS, and the fact that they hear the community concern and most of the time they address this very quickly. Anyway I didn't want to complain at all I was just seeking some answers. I am a very happy unraid user and as I said I was already considering to buy a second licence, this I think tells more than a million word. @ich777 I read your post and answers to other people questions/discussion which partly cleared my doubts. Thanks for your time.
  12. Hi all, first of all thanks for this update. Here my bug findings and opinion/concern. BUGS: 1) So far the only thing found was the button to spool down the array works but in a strange way. In order for it to work I need to click the button 5-7 times. Tested on edge browser, adblock disabled. 2) After upgrading I had trouble logging in as the webGUI would not present and I would get only a DNS ERR_NAME_NOT_RESOLVED. I fixed this but changing my computer DNS and then I was able to log in but this is not the correct behaviour in my opinion. I have SSL in Auto mode so what I expect is that if no internet is present at home or DNS server is down I should be able to connect to the webgui using a simple HTTPS://UNRAID_IP. This would give me a cert error but still able to connect and log in. I was able to do this in the 6.9.2 version. OPINIONS/CONCERN: Regarding this UPC feature, please correct me if I am wrong. If I already have the key then it doesn't really come into play as I just don't need to opt in. If I need i key I need to use this UPC to get trial and/or buy the key then I can log out. The question is, if I don't install the plugin My server and/or I sign in for the purpose to buy a key and then log out, is any data (configs, flash backups or any flash file) sent to LimeTech server? If data is being sent, is the data collected? Please consider as well that not everyone is in the US. In Europe we have different privacy rules and most recently GDPR. Could you please clarify the concerns of the community. Would be nice to have a FAQ pages with all the common questions and answers about this new feature. I am planning to buy a second licence but only after this concerns regarding the UPC feature will be addressed. Again thanks a lot for all your hard work.
  13. Mik3

    Happy Birthday!

    Happy birthday!🍰🥂
  14. Dear members, I tryed searching the forum about this specific question but couldn't really find an answer that satisfies me. I own an unraid plus licence and since I am very happy with the product I want to buy an upgrade to support the project more and to allow for future expansion. The questions are: When I buy the upgrade from plus to pro do I receive a new licence file by email? What happens to the old one? Do I need to reinstall the key in my current unraid server or it automatically sees the upgrade? If the usb drive fail and I need to migrate my licence to the new usb, will Unraid recognize it as PRO licence? Thanks for your time Regards.
  15. Hi guys, I wanted to move from plex to emby since a while for multiple reasons. I decided to make this guide first because I want to give back something to the amazing community behind UNRAID/REDDIT/EMBY and second because I couldn't find a step by step guide so I thought it would be nice to have a lot of useful informations in a single place. If you just want to setup the hardware transcoding using intel quick sync video in emby on unraid go directly to STEP 8. I take also the opportunity to thank spaceinvaderone for the amazing videos he made about UNRAID, I learned a lot, and the linuxserver.io guys/gals for the amazing job they do supporting and maintaining the community images. Note: I am not affiliated with anybody nor I get paid to do this, this shows the steps I used to setup emby on unraid so to make it easier for you to do the same. Also english is not my native language so excuse me for any syntax/grammar error. Last premise before we start, if you want to add something or you think some steps needs additional informations to be clearer let me know in the comments. @Mods: if you think this guide is useful and you want to stick this post for ease of reference for the community please do so, thanks. Let the fun begin... PREREQUISITES: ------------------------------ UNRAID 6.9-RC1 or newer UNRAID COMMUNITY APPLICATIONS (Refer to this post on how to install: https://forums.unraid.net/topic/38582-plug-in-community-applications/) EMBY v4.5 or newer EMBY PREMIERE SETUP: ------------ STEP 1 - Setting up a dynamic DNS --------------------------------------------------------- Use your preferred dynamic dns provider to setup a custom dns tracking service. For example: "emby.hopto.org" where "emby" is the name you want and the rest is fixed depending on the dynamic dns provider. Ex.: "myembysrv.hopto.org" STEP 2 - CREATE A CUSTOM DOCKER NETWORK ----------------------------------------------------------------------------- Inside the unraid web interface, open a terminal by clicking the terminal icon on the top right corner and type docker network create cdocknet where "cdocknet" is the name of our custom docker network. You can name it whatever you want. Press ENTER and then a long string of random characters (network id) should appear meaning the custom network was successfully created. If there is an error message make sure you correctly typed in the command otherwise search google for the error message and fix it before moving onto the next step. If everything is successful you can close the terminal window and proceed to the next step. STEP 3 - Install SWAG (Secure Web Application Gateway) ------------------------------------------------------------------------------------------ Inside the unraid web interface, go to apps then in the top right corner inside the search bar search for "swag" (without quotes) Click install and you will be redirected to the container settings. Change the following settings: Network type: -> Select Custom: cdocknet (or watherver name you assigned in step 2) HTTP: -> Change it to 8080 or another port that is not in use either in unraid or any docker you have HTTPS: -> Change it to 8443 or another port that is not in use either in unraid or any docker you have EMAIL: -> Your email address DOMAIN NAME: -> The Dynamic DNS domain name, so if we use the one I setup in the first step it is going to be hopto.org Yours can be different. Ex.: ddns.net, duckdns.org SUBDOMAINS: -> Delete the "www" and replance it with the custom name you chose in step 1, in our case emby. ONLY SUBDOMAINS: -> Set it to true (we tell swag to issue the cert. only for our subdomain as we don't own the top level domain be it hopto.org or whatever else you chose) You can leave the rest as default. Now before clicking "APPLY" open a new tab and go to your router setting and setup a port forward to unraid for the port 80 and 443. I cannot give a specific guidance here as every router setting is different. Try to search for port forwarding [your router model] in google and read how to do it. You should have a table/items like this. You need to setup 2 port forwarding, one for port 80 and one for port 443. NAME/APPLICATION NAME/SERVICE NAME: Swag80 IP ADDRESS: enter unraid ip address PUBLIC PORT: enter the default HTTP port, in this case 80 PRIVATE PORT: enter the custom port you setup for the docker, in our case 8080 PROTOCOL: TCP NAME/APPLICATION NAME/SERVICE NAME: Swag443 IP ADDRESS: enter unraid ip address PUBLIC PORT: enter the default HTTPS port, in this case 443 PRIVATE PORT: enter the custom port you setup for the docker, in our case 8443 PROTOCOL: TCP After you did so go back to unraid and click apply. Once swag is installed check the log setting to make sure everything is done without error thus a certificate is created and valid. Basically you shouldn't have any red/amber warning in the log and at the end you should see a "Server ready." message. If any red/amber shows then check the port are correctly forwarded (make sure the numbers are correct, the unraid server's ip address is correct) otherwise read what the error says and do a search to fix it. STEP 4 - Install Emby ----------------------------------- As before go under the apps tab in unraid to open the community applications and search for emby. You should see 3 or more emby containers, you can use the one you prefer. For our guide we use the official emby container. Click install and again you'll be redirected to the docker settings. Change the following settings: Network type: -> Select Custom: cdocknet (or watherver name you assigned in step 2; if you have multiple custom network make sure you use the same you setup in swag otherwise the reverse proxy won't work) Host path 2:* -> Path to your media folder share. Ex.: /mnt/user0/Media Then click apply and wait for the docker to be pulled. Once it's complete you can open emby web interface by clicking on the EmbyServer icon and select "WebUI". Emby asks you to setup a username and a password. Note this one will be the admin of the server so use a strong password. Don't worry about Emby connect, this is not required at this moment so you can leave it blank. If you have one feel free to enter it. Click next. You can already setup the library in this part or skip and do it later. For the purpose of this guide we skip it as it's not difficult and there is plenty of documentation on emby website on how to do that. So now you can click finish and you will have emby UI with all the libraries (if you setup any) and the possibility to access the server settings. STEP 5 - Configure SWAG proxy-conf ------------------------------------------------------------ If you didn't change the default appdata config path in swag you will have all the config file under /mnt/user/appdata/swag. So from unraid webui set the appdata share to export with public access type. To do so just click on the appdatashare, then under SMB Security Settings set the following: Export: -> yes Security: -> Public Click apply then done. From your PC/MAC navigate to the appdata share and open the swag folder. In windows would be "This PC-> Network -> unraid_server_name -> appdata -> swag" Inside swag navigate to nginx and then open proxy-conf folder. Search and open a file named emby.subdomain.conf.sample with your preferred text editor be it notepad, notepad++, gedit or whatever. Inside this file you have to change: "server_name emby.*" to whatever name you setup in step 1 for the dynamic dns. Example if your dynamic dns is myembysrv.ddns.net in this line you would setup "server_name myembysrv.*" (without quotes). The other line we have to change is the "set $upstream_app emby" by replacing emby with the container name. If you used the official emby container and you didn't change it then you would set this up to "set $upstream_app EmbyServer". You can find the container name in unraid. Now click save and rename the file by removing the ".sample" at the end. So the new file name will be "emby.subdomain.conf". Go back to unraid webui, click on the swag container icon and restart the container. (This reloads the configuration files in swag like the one we just modified) STEP 6 - Configure remote access on Emby --------------------------------------------------------------------- Open emby webui by clicking on the emby docker icon in unraid, go to settings -> network. Tick the "Allow remote connections to this emby server" now some extra settings will appear. Scroll down till you find "Public HTTPS port number" and change it to "443" Right below you find the "External domain:" and set this to the dynamic dns we setup in step 1. In our case is "emby.hopto.org" Then scroll down a bit more till you find "Secure connection mode:" and change it to "Handled by reverse proxy" Then just below it untick the "Enable automatic port mapping" and then scroll at the end of the page and click save. Go back to unraid webui and restart emby docker. STEP 7 - Test the remote connection ----------------------------------------------------------- Open a new tab and go to "https://emby.hopto.org", of course replace this with your custom dynamic dns entry. Ex.: "https://myembysrv.ddns.net" You should see a "Please sign in" page with emby logo asking you for a login and password. If you see a connection timeout then you did something wrong. Go back and re-read all the steps and make sure you did everything correctly. If you see an SSL cert error/browser warning that the connection is not secure then you messed up with the ports or skipped some steps. Again re-read and make sure you did everything properly. STEP 8 - Setting the HW (hardware) transcoding in Emby with intel QSV (Quick Sync Video) -------------------------------------------------------------------------------------------------------------------------------------------------- Requirements: Emby premiere Intel CPU that has Quick Sync Video (search your cpu at https://ark.intel.com/content/www/us/en/ark.html#@Processors) Compatible motherboards (sometimes iGPU has to be enabled in BIOS/UEFI, in some other cases you need a VGA/HDMI plugged-in to have it functional either by plugging in a monitor or by using a dummy VGA/HDMI adapter) If you meet the above requirements please read on... Open a terminal window in unraid (top right corner, click on the terminal icon inside the unraid webui) and type the following: ls /dev/dri and press ENTER If you see something like by-path/ card0 renderD128 this means that the QSV is already enabled in your unraid server and you can skip to the docker setting step otherwise read on. In the terminal window type: modprobe i915 then press ENTER (if there is any error stop and solve this before moving on. Make sure you meet all the requirements) Then type: ls /dev/dri and press ENTER. Now you should see something like this: by-path/ card0 renderD128 Now type chmod -R 777 /dev/dri to set the permission on the folder so we can access to it from the emby docker container. Once that's done close the terminal window, go over Emby docker container icon and click "Edit". This will bring the container settings up like the first time we installed it. Scroll down at the bottom and click on "+ Add another path, port, variable, label or device". A new window/popup will open. Change the following settings: Config Type -> Device Name -> /dev/dri Value -> /dev/dri Description -> Intel Quick Sync Video Then click "ADD" and the "APPLY" and after the container is pulled down again click on "DONE". Now open emby webui, go to "Settings -> Transcoding" and make sure you have "Enable hardware acceleration when available:" set to "Yes" or "Advanced". With advanced you can see the various preferred hardware encoders/decoders emby will use and tick/untick the ones you want. Scroll to the bottom and click on "Save". STEP 9 - Testing the hardware transcoding and make Intel QSV persistent across unraid server reboots -------------------------------------------------------------------------------------------------------------------------------------------------------------------- To test if the hardware trascoding is working as intended just go to your library, open a movie and select a different quality. For example you can set it to 480p - 1Mbps and click play. If you go in your server dashboard inside emby webui settings you will see under "Active devices" the client name that is reproducing the movie and just below informations about wether it is being transcoded or not and which encoder/decoder is being used. For example if you see VAAPI (Video Acceleration Api) means the hardware transcoding is working using the intel QSV by accessing /dev/dri (Direct rendering infrastructure). Finally last step is to go back into unraid webui, open a terminal window and edit the go file to make sure Intel QSV is always on even if we reboot the server. To do so type: nano /boot/config/go and press ENTER Nano editor will open and you will see the content of the file. If you never modified it before it should be similar to: #!/bin/bash # Start the Management Utility /usr/local/sbin/emhttp & Just add the following lines to the bottom of the file modprobe i915 chmod -R 777 /dev/dri Your go file should look like this: #!/bin/bash # Start the Management Utility /usr/local/sbin/emhttp & modprobe i915 chmod -R 777 /dev/dri Save using the CTRL + O and then CTRL + X to exit Done! If you read it this far I thank you for the attention and I hope you found this guide useful. Finally you can enjoy your media on the sofa.