Popular Content

Showing content with the highest reputation since 12/18/17 in all areas

  1. 10 points
  2. 8 points
    I will only post this once. Feel free to refer folks to this post. A few points of clarification: The last update of this image didn't break things. Letsencrypt abruptly disabled the authentication method previously used by this image (tls over port 443) due to a security vulnerability. It is unclear whether they will ever re-enable it again. So we added the option of validating over port 80, via setting the HTTPVAL variable to true (similar to how PUID is set to 99). But you have to make sure port 80 is forwarded to the container from your router. Keep in mind that unraid gui runs on port 80, so you should map port 80 on your router to any other port, ie. 85. Then in the container settings, map port 85 to port 80. Unraid template has been updated to include this new variable setting, and I think the brand new unraid stable as well as the previous betas will automatically add that variable to your settings (not 100% sure because I'm still on 6.3.5). Either way, check your settings. If your isp blocks port 80, there's nothing we can do as it is the only port letsencrypt will validate through at this point. Someone mentioned dns validation. It's not gonna happen as it is. It requires a script to change dns settings on your dns provider. Since all the dns providers have different api's for this process, we cannot automate it for you, therefore we will not add dns validation (unless there is a standardized way to update dns entries in the future but I wouldn't hold my breath). You do not need to make changes to your nginx site config and you do not need to enable listening on port 80. Validation is done through a separate web server temporarily put up during validation and is not affected by your nginx config. And one last thing, the error message about the directory not existing is harmless, it just means that you didn't have a letsencrypt cert the last time the container was started, probably because the validation had failed.
  3. 7 points
    As I approach the end of my 2nd year using unRAID I've felt the need to express my mass appreciation to Lime Tech and the community as a whole. I started using unRAID in February of 2016. Issue after issue on my Windows Server build led to an eventual collapse of my 10 TB RAID array and the loss of all the data. At the time it felt pretty terrible as I stayed up late into that night trying to salvage what data I could only to finally accept there would be no salvage. Within the first 2 months of using unRAID I already felt like my server meltdown was the best thing that could have happened to me. Since then unRAID has provided tools to do powerful things easily and every issue I have ever had the community has resolved within days if not hours. I currently work at a computer network company and am happy to have evangelized the hell out of unRAID as I was the first person there to use it. We now have many who have done things from replacing their ESXi build, that was a more complex system than they needed, to running their server and desktop off the same machine to save on cost and space, keeping their spouse happy. So thank you Lime Tech for making a product that fuels my home server hobby and thank you to the community for making that hobby (mostly) stress-free.
  4. 6 points
    I took a stab at writing a How-To based on the feedback in the release thread. If this looks helpful, maybe it could be added to the top post? Edit: this warrants it's own topic, thank you! -tom Before you upgrade Read the first post in the release notes thread Uninstall the S3 Sleep plugin, the Preclear plugin, unmenu, and any plugins you no longer use Upgrade all other plugins (other than the main unRAID OS plugin) Delete all files from the \\tower\flash\extra folder and install them using Nerd Tools instead Review your \\tower\flash\config\go script and use a good editor (like Notepad++, not Notepad) to remove as much as possible. For instance, remove any references to "cache_dirs" and use the Dynamix Cache Directories plugin instead. Consider moving other customizations to the User Scripts plugin FYI, a completely stock go script looks like this: #!/bin/bash # Start the Management Utility /usr/local/sbin/emhttp & Consider installing the Fix Common Problems plugin and resolve any issues it highlights Consider Installing any BIOS updates that are available for your motherboard If you made any substantial changes in this section, reboot before continuing to make sure any problems are not the result of these changes. Performing the upgrade to 6.4.0: Stop the array (If 6.3.5 or earlier) Go to Plugins and update the unRAID OS plugin (but don't reboot yet) (If on one of the 6.4 rc's) Go to Tools -> Update OS and update the OS (but don't reboot yet). You may need to switch from Next to Stable to see the update. By default, the webgui in unRAID 6.4.0 will use both port 80 and port 443 (even if you don't enable SSL) and any customization you made to the port in your go script will be ignored. If you need to change the port before booting into 6.4.0 for the first time, use a good editor (like Notepad++, not Notepad) and edit \\tower\flash\config\ident.cfg Add the following lines to the end of the file, substituting the ports you want to use: USE_SSL="auto" PORT="80" PORTSSL="443" NOTE: If you need to change the defaults, be sure to pick high values over 1000. i.e. 81 and 43 are *not* good options. Try 8080 and 8443 Once you have booted in 6.4.0, you should no longer edit this file by hand. Better to use the webgui: Settings -> Identification -> SSL Certificate Settings If you are running Ryzen: Edit your \\tower\flash\config\go script (using a good editor like Notepad++ (not Notepad)) and add the "zenstates" command right before "emhttp", like this: /usr/local/sbin/zenstates --c6-disable /usr/local/sbin/emhttp & Also, go into your BIOS and disable "Global C-state control" Reboot into 6.4.0 It may be helpful to clear your browsers cache --- Solutions to Common Problems If you have problems booting after applying the upgrade, move your flash drive to a Windows or Mac machine and run checkdisk, fixing any problems it finds. If you have severe errors (no lan, array won't start, webgui won't start) try installing 6.4 on a new flash drive. If it works, that means the problem is with one of your customizations. You can either try to find and fix the problem (if you skipped the "before you upgrade" section, that would be a good place to start), or move forward with the clean flash drive. To continue with the clean drive, copy just the basics (/config/super.dat and your key file) from the old drive to the new one and then reconfigure as needed. If your cache disk has an "incompatible partition" after upgrading, it was probably created in an older version of the Unassigned Devices plugin. UD has been updated so this won't happen again. This is a one-time fix. You'll need to downgrade to 6.3.5 and move the data off the cache drive, re-format the disk and move the data back. The procedure is outlined here If you have on-board Aspeed IPMI you may find that IPMI loses video or changes color during the boot process. To resolve this, go to Main -> Boot Device -> Flash -> Syslinux Config and add "nomodeset" to your "append" line (and reboot). It should look something like this: label unRAID OS kernel /bzimage append nomodeset initrd=/bzroot If you don't see CPU load statistics on the dashboard, or if you can't use the new web-based terminal, switch to Chrome or Firefox instead of Safari. This is a shortcoming in Safari, not a bug in unRAID. To enable SSL, go to Settings -> Identification -> SSL Certificate Settings and click Provision. If you get an error about rebinding protection, wait 10 minutes and try again. If you still get the error, click Help to read how to adjust your router. Using these certificates will change your url to <some long number>.unraid.net. No it can't be changed without disabling all of the automation by switching to your own certificates. You don't need to remember the number, when you connect via IP or servername it will automatically redirect. If you are concerned about a theoretical DNS outage, know that you can overide your DNS by adding an entry to your PC's hosts file. Or in a pinch you can edit \\tower\boot\config\ident.cfg and set: USE_SSL="no" If you prefer to use your own certificates rather than the fully automated Let's Encrypt certificates, click the Help icon on the SSL Certificate Settings page. Want to check out the new themes? Navigate to Settings -> Display Settings -> Dynamix color theme. You may need to change your banner when you change the theme Note that you can now use the webgui to assign unique IP addresses to your dockers. If you manually customized your macvlans under 6.3.5 you'll need to set them up again using the webgui. Are you having problems with your Lets Encrypt docker? First, make sure the webgui and docker aren't both trying to use the same port. Beyond that, Lets Encrypt recently made some changes that break things. These issues are not related to the unRAID upgrade, refer to the LE docker thread for help Speedtest complaining about Python? The timing is coincidental, but it is not related to the unRAID upgrade, see the Speedtest thread Are you seeing a "wrong csrf_token" token in your logs? Close all your browser tabs (on all computers) that were pointed at unRAID prior to the last reboot. More info Are you still having problems? Review the expanded "Before you upgrade" section above. If that doesn't help, grab your diagnostics (Tools -> Diagnostics) if you can, and reboot into Safe Mode. If your problems go away, then the problem is likely with a plugin. If the problems persist, you'll need additional help. Either way, grab your diagnostics again while in safe mode and attach both sets to a forum post where you clearly explain the issue.
  5. 6 points
    Download If you are running a previous stable release, clicking 'Check for Updates' on the Plugins page is the preferred way to upgrade. If you are running a 6.4.0-rc, click 'Check for Updates' on the Tools/Update OS page. This release contains important security updates related to the recent Meltdown and Spectre vulnerabilities. For this reason, all users are encouraged to update. We expect additional updates in the near future as additional mitigations become available. Aside from security patches, the primary goal of this release is to implement full device encryption utilizing LUKS. Since LUKS permits the use of a passphrase as the encryption/decryption key, a secure method of entering the passphrase via the unRAID Management Utility, a.k.a., webGUI, is necessary; hence, we integrated nginx in order to provide SSL/TLS (https) support. And since https requires SSL Certificates, we partnered with Let's Encrypt to provision free SSL certificates for all of our users right from within the webGUI. Along the way several additional features and improvements have also been added, see below. Finally, we want to express our sincere thanks and appreciation to all those who helped in the Prerelease 6.4 Support board. And a special "thank you" to @bonienl who has made several amazing contributions, especially in the area of networking. Following are the Release Notes: Linux kernel This release is running Linux kernel version 4.14.13 which contains patches to address the widely reported Meltdown and Spectre vulnerabilities. This kernel fully mitigates against Meltdown, but full mitigation for Spectre is not yet complete and has not been publicly released as of this date. Management Utility We now use the nginx webserver as the front-end to the unRAID OS Management Utility (aka, webGUI). Incorporating nginx provides several benefits, including: Multi-threaded access results in much better response. Websocket support. SSL/TLS (https) support. Moving forward, use of websockets will further improve webGUI functionality and responsiveness. At present only the CPU Load Statistics on the Dashboard and the web-based Terminal application make use of websockets. Note: Unfortunately this functionality does not work with Safari. There is now a Logout button for the webGUI which appears on the right side of the menu bar when you have defined a root password and are logged in. Clicking this will log you out from all tabs/windows in that browser. Also new with this release are two new webGUI themes: Azure and Gray, along with numerous other bug fixes and improvements. Secure Access Secure webGUI access is now supported using the https protocol. We offer two methods for dealing with the SSL certificate: Use of a self-signed certificate. Use of a free SSL certificate provisioned by Let's Encrypt. The selection of http/https and SSL certificate configuration is accomplished through the Settings/Identification page. Note: The /usr/local/sbin/emhttp line in your /boot/config/go file is no longer used to specify the ports where the webGUI listens for connections. Instead you must configure these on the Identification page. Alternately if you need to set this up prior to server boot, you may add the port settings in /boot/config/ident.cfg. Please refer to /usr/local/sbin/emhttp script for more information if you care about this. Let's Encrypt SSL Certificates Lime Technology, Inc. has partnered with Let's Encrypt to provide free SSL certificates for all of our users. To obtain your certificate first go to Settings/Identification page, set Use SSL/TLS to Auto and click Apply. Next, scroll to the bottom and click Provision. In one operation this will allocate your certificate, upload it to your server, and switch nginx to redirect all http to https. After clicking anywhere else in the webGUI you should see a nice green lock icon in your browser address bar! You will also notice in your address bar a very funny looking URL consisting of a 40-hex-character subdomain of unraid.net. We have set up a LimeTech DNS server that will resolve that URL to your servers IP address on your local network. That FQDN is unique to your certificate. When your browser resolves that URL it is given your local IP address which it then uses to perform the https connection handshake. Since Let's Encrypt SSL certificates expire every 90 days, we have included a background daemon that checks once per day if your certificate is within 30 days of expiration. If so, we automatically renew and upload a new certificate for you. Finally, we have included another background daemon that checks every 10 minutes for a change in your servers IP address. If your IP address changes, then the DNS A-record for your server is updated. Device Encryption We have implemented full-device encryption as follows. In unRAID, encryption is selected as another type of file system. With array Stopped, click on a Device link and then click on File system type where you can selected encrypted versions of supported file system types: xfs – encrypted btrfs – encrypted reiserfs – encrypted If you change any device file system type to encrypted, you will notice a section on the Main page appears where you must enter a passphrase or upload an encryption keyfile before you can Start the array. DO NOT FORGET YOUR PASSPHRASE OR LOSE YOUR KEYFILE. Once a device is encrypted, if you forget your passphrase or lose your keyfile, your data is lost forever! Once you have Started the array, newly encrypted devices appear Unmountable and the Format button is available. Formatting will result in creating an encrypted partition on those devices with the specified file system type. ALL PREVIOUS DATA ON THAT DEVICE WILL BE DESTROYED. Hence it is not possible, in this release, to encrypt in-place. We plan to add a utility in a future release to accomplish this however. Also note that array Autostart following server boot will not succeed if any devices are encrypted. This is because the passphrase or keyfile is kept in RAM and thus lost upon reboot. This means that following system reboot you must log into the webGUI, enter your passphrase (or upload your encryption keyfile), and then click the Start button. In the case of a btrfs cache pool, all devices comprising the pool will be encrypted. UEFI support It is now possible configure UEFI boot mode to boot unRAID OS. This may be enabled by clicking on the Flash device link from the Main page where you will find a checkbox to select UEFI boot mode. In addition, UEFI boot mode may be selected when a new USB Flash device is provisioned using the USB Creator tool. When using the manual method of preparing a USB Flash device, the make_bootable scripts will output a UEFI boot mode selection prompt. Web-based Terminal We now have a web-based Terminal application available by clicking the Terminal button on the Menu bar. You may also open the Terminal in a new tab by right-clicking the button. This application makes use of websockets and appears to be quite fast, give it a try! NOTE: Unfortunately the web-based Terminal app does not work with Safari. Update OS Instead of bundling an unRAID Server plugin on the Plugins page, there is a new page on the Tools menu in the About section called Update OS. Here you can check for a new unRAID OS release as well as switch between the latest release in the stable branch or the latest release in the next (development) branch. In addition there is a separate control on the Notification Settings page that configures whether or not to automatically check for updates. Improved shfs/mover The unRAID user share file system (shfs) has been improved in two areas. First, we now make use of FUSE readbuf/writebuf methods. This should result in significant throughput increases. Second, the mover script/move program no longer uses rsync to move files/directories between the cache pool and the parity array. Instead the move program invokes a new shfs ioctl() call. This should result in complete preservation of all metadata including atime and mtime. Other IPv6 support. Entirely designed, coded, and tested by user bonienl who has greatly improved unRAID OS networking. We now fully support 4Kn devices, that is, devices with both 4096-byte physical and 4096-byte logical block sizes. It used to be that merely Starting the array would re-write an unRAID standard partition layout on all devices assigned to the array. This has been changed so that nothing is written to a device unless Format is invoked (except for Parity devices – those will still be written upon array Start if parity sync is indicated). Moving devices around between cache pool and array or unassigned is handled much better now. Added Flash backup button on the Flash device info page (Main/Flash). Click this button to download a zip file with the entire contents of your USB Flash boot device. This zip file may be used to restore to a new unRAID USB Flash boot device either manually, or using the USB Creator tool. We ported a simplified version of the zenstates.py utility to C (to avoid including python in bzroot) which may be used to disable Ryzen C6 states (as workaround for Ryzen idle freeze issue). We have found that sometimes bios option to disable C6 does not exist or does not do the right thing. If you want to use this utility, we suggest that you edit the config/go file on your USB flash device. Add this line just before emhttp is invoked: zenstates --c6-disable Expanded driver support and more hardware monitoring support. Kernel modules and firmware are now left on the Flash in a squashfs loopback and loaded into RAM on demand. Many more misc. improvements Known Issues Certain motherboards with on-board Aspeed IPMI graphics adaptors may lose video or switch to different colored text during the boot process. To prevent this, add the nomodeset kernel option to your syslinux append line. Some users report vmwrite syslog errors as a result of VM startup. This is a harmless message and can be ignored; however, please report if you see this. AMD Ryzen CPU is known to freeze on linux-based distros and unRAID OS is no exception. Disabling C6 state either in your bios or using our zenstates program seems to be the most reliable mitigation for this issue. Maybe some day AMD will fix this. AMD Threadripper GPU passthrough to VM's does not work reliably. This is an AMD bug, maybe some day they'll fix it.
  6. 6 points
    Waiting for VM users to confirm what issues remain. That, and waiting for the over/under pot to grow...
  7. 6 points
    I've tagged the app as being incompatible with 6.4 since this issue has existed and been reported since July. I've issued a PR to @theone with the fix. But, in the meantime you can add this either to your go file or as a user script set to run at array start to fix the problem sed -i 's/\"DISK_DATA\" => \"\"/\"DISK_DATA\" => array()/' /usr/local/emhttp/plugins/serverlayout/php/serverlayout_constants.php
  8. 6 points
    @DZMM @1812 Stop jerking around with ugly hacks. Try this instead. Copy the attached file onto the root of the flash drive Edit /boot/config/go and add the following lines before the line that says emhttp, and after the #!/bin/bash cp /boot/dockerupdate.php /usr/local/emhttp/plugins/dynamix.docker.manager/scripts/dockerupdate.php chmod +x /usr/local/emhttp/plugins/dynamix.docker.manager/scripts/dockerupdate.php You'll have to reboot for it to take effect. This fix checks for connectivity to github prior to attempting to determine if the containers have updates available for them. (Github is where the repositories are stored) Without this fix, your VM's never start until all of the cumulative timeouts are reached which could be quite a while. Let me know if this works for you and I'll put in a pull request to LT for the next revision. Note: Attached file only tested on 6.4.0-rc17b. dockerupdate.php
  9. 5 points
    I am making a series of videos on 'must have unRAID plugins' which I hope will be useful for beginners starting out with unRAID. The first part is about Squid's excellent community applications family of plugins which every unRAID user should have installed on their server! Part1 The Community Applications Family of Plugins.
  10. 4 points
    Not criticizing. It's just that simple answers to simple questions often lead to more questions, some of which may have already been answered. By the way, we are all mostly just volunteers here, so you are not really my customer in any sense. I did take the trouble to re-read the last few pages myself looking for your simple answer, but I'm not really clear on exactly what your question is. Simple questions often have a host of assumptions that I may not have in mind when trying to answer.
  11. 4 points
    OK, v6.4.0 stable is ready. Two things to bare in mind. 1. If you want to upgrade to v6.4.0 then you MUST update via LimeTech's route to the non-DVB version of v6.4.0 before you will get access to the v6.4.0 DVB builds 2. Please ensure that you have sorted out any issues with the v6.3.5 - v6.4.0 upgrade route before you install the DVB release as I am not supporting downgrading from v6.4.0 to v6.3.5.
  12. 4 points
    Status Report on version 3 Life got in the way for the past couple months and development slowed quite a bit ("Assassin's Creed: Origins" didn't help either) but I've put in some solid development time over the past week and have made great progress. I hope to have an alpha version ready inside a week. I've been quite satisfied at the progress I've made and getting excited. Installation will be via the Plugin interface and the GUI will be fully in the browser with no telnet sessions. While I say "alpha", it'll be a fairly tested product having been tested on two UNRAID environments plus a VirtualBox environment and against both intel & amd motherboards and different controller cards - but it hasn't been tested against other user's hardware.
  13. 3 points
    This link refers to a patched kernel corresponding to 6.4.0-rc17b that has the Threadripper ugly patch. http://dnld.lime-technology.com.s3.amazonaws.com/next/bzimage If you want to test if this lets GPU passthrough work correctly with Threadripper: First, install unRAID OS 6.4.0-rc17b. Next, from ssh/telnet type something like this: cd /boot mv bzimage bzimage-orig wget http://dnld.lime-technology.com.s3.amazonaws.com/next/bzimage reboot To restore previous kernel: cd /boot mv bzimage-orig bzimage reboot
  14. 3 points
    I removed the rc.preclear status from UD because of issues some people were having in UD. I also feel the same way. I'm beginning to think that the preclear is more trouble than it is worth.
  15. 3 points
    For PFSense if you're using unbound dns resolver just put into custom options and this will work correctly server: private-domain: "unraid.net"
  16. 3 points
    Mainly this was added because there are motherboards that only support UEFI boot. Also, certain h/w is initialized differently which may make it easier to pass through to virtual machines. Jon may have more to say about that later. Yes this is going to be possible, but don't tell anyone about it yet
  17. 3 points
    Still on version 6.3.5 as I need a very stable server. You are now on the 21st version of the release candidate for 6.4. I am following progress closely, however I do not know (and therefore cannot plan) when the stable version of 6.4 will be released. For 6.3 no (security) fixes have been released after 6.3.5. With all the chatter around meltdown I would like to learn the timeline when 6.4 will be released, and if this will take more time, if a 6.3.6 will be released to implement fixes for Meltdown. Regards, Richard
  18. 3 points
    This is the second part of a series of videos where we will take a detailed look at the best 'must have' plugins. This video looks at the Dynamix family of plugins. This video looks at the following plugins, The Trim plugin (and why trim is important). The Cache directories plug, The Active streams plugin, The Sleep plugin, The System temperature plugin, The Date and Time plugin, The System info plugin The System stats plugin
  19. 3 points
    We really need to stop advising users to rebuild on top of a drive that gets kicked from the array. Too high a risk for another disk to drop (due to cabling or other issues) and cause a corrupted rebuild. And this use case is repeating entirely too frequently. The rebuild should be to a fresh disk, and its it falls, the original disk that was kicked should be used as the source of truth. If new files were written to the disk after it was kicked, you can try to repair the rebuilt drive and used to harvest just the newly added files. Such files would need to be tested to see if they are valid.
  20. 3 points
    Yes, I have replaced my Windows workstation with a VM running on my unRaid server. Up and running for 6 months+. The server lives in my unfinished basement, and I was able to run an HDMI cable and USB extender up into my office. Works great and feels just like a bare metal install. Only issue of note has been occasional slow loss of audio sync when watching video (YouTube). Others have seen this also. Pretty easily fixed by reloading the video, but annoying sometimes. Love the setup and wouldn't go back for this minor issue. One seldomly mentioned advantage of running a Windows VM on the unRaid box is that suddenly all of the drives in your array are local to Windows. No network lag. Very nice to be able to quickly copy files! And backing up the Windows VM means copying one file. Quick and easy. Another nicety is being able to upgrade the computer and not have to figure out how to get the Windows install updated for the new hardware. It's all virtualized, and except for maybe updating video drivers if you went for a new video card, the VM should work on the updated server.and hardly know anything had charged. I am working on an upgrade and will soon have a backup server powerful enough to run the VM. So if the primary server ever has issues or is in the middle of an upgrade, I can bring up the VM on the backup server temporarily. Nice to have functional redundancy as well as data backup.
  21. 3 points
    Who knew this place would turn into a haven to solve all your astrological or gem and gold medalist needs? How about simply preventing new users from posting external links or auto-moderating posts from new users with external links? That single setting seems to deter enough of the spambots to make it a win-win on the forums I admin.
  22. 3 points
    Feature request: Instead of one giant tarball, could this app use separate tarballs for each folder in appdata? That way it would be much easier to restore a specific app's data (manually) or even pull a specific file since most of them could be opened with untar guis. Plex is the major culprit with it gargantuan folder.
  23. 3 points
    I have had a discussion with the guy who does the Linux drivers for Hauppage and he wants to push them upstream if possible, but the company don't have it high on their list of priorities. Unless people badger Hauppage then I don't see what will change. I've looked at the Hauppage Linux drivers fairly recently and@BRiT is right, they're not really in a fit state to be included in Unraid. I'm happy if someone wants to take them on to incorporate them into the DVB plugin, but unless they're sorted out by Hauppage, I'm not taking them on, I don't have the time or the inclination to be honest. At least TBS have always been very responsive when I've contacted them, and Digital Devices have been pretty helpful when I've contacted them too... Sent from my LG-H815 using Tapatalk
  24. 3 points
  25. 3 points
    I also had the problem, that Origin dosen't want to download the games on a Network Share. After lots of trying i found the reson why. Origin has a service called "Origin Client Service" which is required to download a Game. This service is executed under the SYSTEM user account, which doesn't know of your Network Share mappings. The easiest way to solve this is to disable the service. Now Origin cannot start the service and runs the Executable as Administrator of your User. To allow the Programs, which run as administrator, to see the Network Share you have to follow these instructions: https://technet.microsoft.com/de-de/library/ee844140(v=ws.10).aspx. You culd also map the Network Share in the SYSTEM user but this is generally not a good idea, because then the SYSTEM user could be atacked throu that share. Also running the service under your user has the drawback that origin would not work in multi-user environments. My solution has the drawback that Origin prompts you with an UAC for the first download after Origin started. Here the detailed steps to realize my solution: 1. type services.msc in to the Search field and open Services 2. Search for "Origin Client Host" in the list and duble click it 3. set the Startup type to disabled 4. Click OK and close the Services window 5. type regedit in to the search field and open the entry regedit 6. Locate and then right-click the registry subkey HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System. 7. Point to New, and then click DWORD Value. 8. Type EnableLinkedConnections, and then press ENTER. 9. Right-click EnableLinkedConnections, and then click Modify. 10. In the Value data box, type 1, and then click OK. 11. Exit Registry Editor, and then restart the computer. 12. Now Origin should be able to to download to the set installation-path even if it is a network share
  26. 3 points
    Here's my rough concept that's a bit overcluttered to show the ideas but I think it could make the basis for a nice logo after some work in refining the elements. I accidentally uploaded a vertically scaled image of the logo. Here is the original, which is too wide, but it looks a little better in some ways.
  27. 2 points
    The forum should have some form of function where x people could make a blocking vote to pause an account from making new posts until moderator or site owner has reviewed the situation. That would better allow spam attacks to be mitigated during off hours where the normal staff isn't available. With a rule that an account must have existed for 12+ months and be in good reputation, it would be hard for an attacker to use the feature for a denial-of-service attack.
  28. 2 points
    It isn't strictly required, but to reduce confusion I'd remove the port information. So: /usr/local/sbin/emhttp &
  29. 2 points
    The removal of "unknown" networks was done to avoid potential conflicts with the automated network generation in unRAID6.4. There is nothing naive or silly about that. Look, you are pissed because it doesn't meet YOUR requirements, but doing manual macvlan configuration isn't for the majority of users and I am convinced that current implemention perfectly suites this majority. However we'll need to find a way to suit the needs for more advanced usage too, perhaps a setting to allow manual networks. For the time being the most practical solution for you is to comment out the deletion of other (unknown) networks in /etc/rc.d/rc.docker. # cleanup non-existing custom networks #for NETWORK in $NETWORKS; do # [[ ! "$ACTIVE " =~ "$NETWORK " ]] && docker network rm $NETWORK 1>/dev/null 2>&1 #done To get that automated on startup you will need to keep a revised rc.docker version on your flash and copy that within your go file before starting emhttp.
  30. 2 points
    unRAID6.4 has a completely revamped GUI implementation. It is using nginx as web server and emhttp has been relegated to a background daemon. This approach not only makes the GUI far more responsive but also GUI hang ups should be a thing from the past.
  31. 2 points
    A plugin to extend the autostart options for docker applications. This plugin will give you the option to explicitly select the order that docker apps will start up in (useful if one app depends upon another to be up and running), and also gives you selectable delays between starts of each app ( to give the first app time to get up and running properly, or to reduce disk thrashing by only trying to load a single app at a time vs loading 10 simultaneously) Each app has a selectable start delay after the previous app in the list starts up (defaults to 5 seconds, but can be set to any value, or no delay at all) Note that any app which this plugin manages will appear on the normal Docker Containers screen as having autostart off You can also combine management of autostart between unRaid itself, and this plugin. Note: This plugin requires unRaid 6.3.0-rc2+ It will not install under any previous version, and CA will not display this plugin as being available on incompatible unRaid versions Install this plugin via CA ( search for Docker autostart)
  32. 2 points
    @Muff Looks like you're forwarding 80 and 81 externally to 80 & 81 internally. You need to forward 80 externally to 81 internally.
  33. 2 points
    This is a browser artifact and happens when browser scaling is set larger than 100%. Different browsers give different results when scaling.
  34. 2 points
    Thanks everyone for all the feedback on the new release so far!! It really helps to know how people are doing with their upgrades and what issues (if any) arise. Please keep it up!
  35. 2 points
    Did you even read the first post? There is a note about exactly that in there under Secure Access...
  36. 2 points
    I just updated my system to 6.4.0 without any issues, it took approx 10-15 minutes Brief description of my system: - Gigabyte H270N-WIFI motherboard, 16GB DDR4 and an Intel Pentium G4560 (3,5 GHz) - array consists of 5x 3TB WD Red HDD's and a 120GB SSD for caching - use Docker containers for MySQL, Apache webservers, Plex and Duplicati (all work fine) - VM are not in use (currently) Update:--> Docker LetsEncrypt raises some issues, which I need to investigate. The log of this docker now reports [cont-init.d] 10-adduser: exited 0. [cont-init.d] 20-config: executing... sed: /etc/php7/php.ini: No such file or directory sed: /etc/php7/php-fpm.conf: No such file or directory sed: /etc/php7/php-fpm.d/www.conf: No such file or directory sed: /etc/php7/php-fpm.d/www.conf: No such file or directory [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] 50-config: executing... 2048 bit DH parameters present SUBDOMAINS entered, processing Sub-domains processed are: -d www.<<removed by me before posting log>> E-mail address entered: <<my email>> Different sub/domains entered than what was used before. Revoking and deleting existing certificate, and an updated one will be created usage: certbot [SUBCOMMAND] [options] [-d DOMAIN] [-d DOMAIN] ... Certbot can obtain and install HTTPS/TLS/SSL certificates. By default, it will attempt to use a webserver both for obtaining and installing the certificate. certbot: error: argument --cert-path: No such file or directory Generating new certificate Saving debug log to /var/log/letsencrypt/letsencrypt.log Plugins selected: Authenticator standalone, Installer None Obtaining a new certificate Performing the following challenges: Client with the currently selected authenticator does not support any combination of challenges that will satisfy the CA. Client with the currently selected authenticator does not support any combination of challenges that will satisfy the CA. IMPORTANT NOTES: - Your account credentials have been saved in your Certbot configuration directory at /etc/letsencrypt. You should make a secure backup of this folder now. This configuration directory will also contain certificates and private keys obtained by Certbot so making regular backups of this folder is ideal. ERROR: Cert does not exist! Please see the validation error above. The issue may be due to incorrect dns or port forwarding settings. Please fix your settings and recreate the container Found some information here, but I will need to investigate some more. https://community.letsencrypt.org/t/solution-client-with-the-currently-selected-authenticator-does-not-support-any-combination-of-challenges-that-will-satisfy-the-ca/49983 Thank you very much
  37. 2 points
    Finally! I want to thank everyone who participated here to help us develop this release. Who won the over/under?
  38. 2 points
    Because the docker internal IP is NATTED from the general network, so the IP that is broadcast from the controller isn't directly reachable by the devices. You have to tell the devices which IP address will allow them to access the docker.
  39. 2 points
    as a quick test I tried it to see vm performance changes. on a 7 thread OS X vm (8thread processor,) before adding " 'pti=off' the vm scored between 363-375 in cinebench. After adding and rebooting, the vm benchmarked at 360-375. This is with the vm running on isolated cores, with an emulator pin set to core 0, sharing it with unRaid. These scores make sense I believe, since unRaid is only minimally responsible for how the vm performs (emulator management which usually uses about 8-25% of a given thread it is pinned to on this machine.) So if my understanding is correct, even if it hits 30% decrease in performance, it shouldn't affect vm's that much and would rather be more dependent on the fix implemented by the vm os. But even in terms of the vm os fix, due to the nature of synthetic benchmarks, the score may also not be affected. OR the added 'pti=off' doesn't do anything. I don't have time to rollback to find out how it compares vs previous RC's. I did not test any other situations in regards to dockers/transfers/etc because I was only on my 2 users/1cpu server at the time.
  40. 2 points
    You should send @limetech some money for the bonus cpu power.
  41. 2 points
    Ok, we believe we have identified the issue causing the spamming and have implemented fixes. Part of these fixes includes changing to recaptcha 2 for human validation during account sign up and adding some manual question / answer work for the user to do. These two things alone should heavily combat the spam issue, but we'll be monitoring closely to ensure all is working as intended.
  42. 2 points
  43. 2 points
    RC18f uploaded Sent from my LG-H815 using Tapatalk
  44. 2 points
    Not necessarily. I am encrypting a UD disk manually now and I will see what it takes to mount. What I need help with is accessing the key to decrypt the drive. I may be able to find it on my own, but help from LT would be appreciated. EDIT: I think I may have figured it out. I've been able to mount an encrypted disk.
  45. 2 points
    Right this is just a noisy message. What's happening is this. In 6.4 we moved from single-threaded emhttp to multi-threaded nginx http server. Used to be on each webgui page load, emhttp would "refresh status" synchronous with each http request. In context of this issue, if the array is Stopped and you hot-plugged or hot-removed a storage device, you only have to click refresh on Main page and the change would be reflected. In moving to nginx we can't be doing a complete "refresh status" on each request or else would be really slow. How it works now is, when array is Stopped, background thread wakes up every second to evaluate the storage device config, checking to see if you added/removed any devices. What you are seeing is the code complaining there is a storage device without any medium and hence reading the size is failing (because there's no device). What we'll do to fix this is filter out "No medium found" and handle that specially. @Bigdady92 not sure if this is what you're seeing. Do you also have a card reader or maybe some kind of external enclosure without a device installed in it?
  46. 2 points
  47. 2 points
    Looks good, keep an eye on the it until you upgrade to a release using 4.14, I recommend scheduling a weekly balance for anyone running kernel 4.13 or older, even on 4.14 it's a good idea to keep an eye on at least initially, it's supposed to be fixed but it's too early to tell if it really is.
  48. 2 points
    Cheap is not what you want for a UPS, the idea is that if there is a power outage or a surge you want the UPS to protect your equipment and you want it to do a good job. I am not sure what brands are common or popular in the EU, but in North America brands such as APC and Cyberpower are common. I would not recommend going with a cheap UPS you will only regret it when something goes wrong.
  49. 2 points
    My tests with only one VM went fine. Be careful to check the results if you want to use the script with multiple VM's. I have set the script to run every night, even though the server will not be running 24x7 in practice. It takes about 1,5 hours to create a zipped backup of my VM plus xml file and always leaves at least one backupfile in the folder. I have added the the script for those interested. Feel free to comment and improve. script
  50. 2 points
    How do I replace/upgrade my single cache device? (unRAID v6.2 and above only) This procedure assumes that there are at least some dockers and/or VMs related files on the cache disk, some of these steps are unnecessary if there aren't. Stop all running Dockers/VMs Settings -> VM Manager: disable VMs and click apply Settings -> Docker: disable Docker and click apply Click on Shares and change to "Yes" all cache shares with "Use cache disk:" set to "Only" or "Prefer" Check that there's enough free space on the array and invoke the mover by clicking "Move Now" on the Main page When the mover finishes check that your cache is empty (any files on the cache root will not be moved as they are not part of any share) Stop array, replace cache device, assign it, start array and format new cache device (if needed), check that it's using the filesystem you want Click on Shares and change to "Prefer" all shares that you want moved back to cache On the Main page click "Move Now" When the mover finishes re-enable Docker and VMs

Copyright © 2005-2017 Lime Technology, Inc. unRAID® is a registered trademark of Lime Technology, Inc.