• Unraid OS version 6.10.0-rc1 available


    limetech

    6.10.0 Summary of New Features

     

    As always, prior to updating, create a backup of your USB flash device:  "Main/Flash/Flash Device Settings" - click "Flash Backup".

     

    UPC and My Servers Plugin

    The most visible new feature is located in the upper right of the webGUI header.  We call this the User Profile Component, or UPC.  The UPC allows a user to associate their server(s) and license key(s) with their Unraid Community forum account.

     

    Starting with this release, it will be necessary for a new user to either sign-in with existing forum credentials or sign-up, creating a new account via the UPC in order to download a Trial key.  All key purchases and upgrades are also handled exclusively via the UPC.

     

    Signing-in provides these benefits:

    1. No more reliance on email and having to copy/paste key file URLs in order to install a license key - keys are delivered and installed automatically to your server.
    2. Notification of critical security-related updates.  In the event a serious security vulnerability has been discovered and patched, we will send out a notification to all email addresses associated with registered servers.
    3. Ability to install the My Servers plugin (see below).
    4. Posting privilege in a new set of My Servers forum boards.

     

    Once a license key has been provisioned, it is not necessary to remain signed-in, though there is no particular reason to sign-out.  Exception: if you have installed the My Servers plugin, signed-in servers will maintain a websocket connection to a Lime Technology cloud server for the purpose of transmitting real-time status.

     

    My Servers Plugin

    My Servers is what we call our set of cloud-based or cloud-enabled services and features that integrate with your Unraid server(s).  Once installed here are some of the features of My Servers:

    • My Servers Dashboard - when logged into the forum a new My Servers menu item appears. Clicking this brings up a Dashboard which displays a set of tiles representing each signed-in server.  Here you can see real-time status such as whether the server is online or offline, storage utilization and other information.  In addition, links are created to bring up a server webGUI, either locally on the LAN or remotely over the Internet (if Remote Access has been enabled).
    • flash backup - every registered server is provided with a private git repo initially populated with the contents of your USB flash boot device (except for certain files which contain private information such as passwords).  Thereafter, configuration changes are automatically committed.  Through the My Servers webApp it's possible to download a custom zip file that can be fed as input to the USB Flash Creator tool to move your configuration to a new USB flash device.
    • License key download - Again, through the My Servers webApp you can download your license key directly.

     

    My Servers is an optional add-on, installed through Community Apps or via direct plugin URL.  Detailed instructions can be found here.

     

    Security Changes

    • It is now mandatory to define a root password.  We also created a division in the Users page to distinguish root from other user names.  The root UserEdit page includes a text box for pasting SSH authorized keys.
    • For new configurations, the flash share default export setting is No.
    • For all new user shares, the default export setting is No.
    • For new configurations, SMBv1 is disabled by default.
    • For new configurations, telnet, ssh, and ftp are disabled by default.
    • We removed certain strings from Diagnostics such as passwords found in the 'go' file.

     

    Virtualization

    Both libvirt and qemu have been updated.  In addition qemu has been compiled with OpenGL support.

     

    The built-in FireFox browser available in GUI-mode boot is built as an AppImage and located in the bzfirmware compressed file system image.  This saves approximately 60MB of RAM.

     

    The Wireguard plugin has been integrated into webGUI, that is, no need for the plugin.  If you had the plugin installed previously, it will be uninstalled and moved to the "Plugins/Plugin File Install Errors" page. No action is needed unless you want to press the Delete button to remove it from that page. Your WireGuard tunnels and settings will be preserved.

     

    Simplified installation of the Community Apps plugin.  The webGUI automatically includes the Apps menu item, and if CA is not already installed, the page offers an Install button.  No need to hunt for the plugin link.

     

    Let's Encrypt SSL provisioning change.  In previous releases code that provisions (allocates and downloads) a LE SSL certificate would first test if DNS Rebinding Protection was enforced on the user's LAN; and, if so, would not provision the certificate.  Since there are other uses for a LE certificate we changed the code so that provision would always proceed.  Next, we changed the logic behind the Auto selection of "Use SSL/TLS" setting on the Management Access page.  Now it is only possible to select Auto if both a LE certificate has been provisioned and DNS Rebinding Protection is not enforced.  This is a subtle change but permits certain My Servers features such as Remote Access.

     

    Linux Kernel

    Upgrade to Linux 5.13.8 kernel which includes so-called Sequoia vulnerability mitigation.

     

    In-tree GPU drivers are now loaded by default if corresponding hardware is detected:

    • amdgpu
    • ast
    • i915
    • radeon

     

    These drivers are required mostly for motherboard on-board graphics used in GUI boot mode.  Loading of a driver can be prohibited by creating the appropriate file named after the driver:

    echo "blacklist i915" > /boot/config/modprobe.d/i915.conf

    Alternately, the device can be isolated from Linux entirely via the System Devices page.  Note that in Unraid OS 6.9 releases the in-tree GPU drivers are blacklisted by default and to enabling loading a driver you need to create an empty "conf" file.  After upgrading to Unraid OS 6.10 you may delete those files, or leave them as-is.  This change was made to greatly improve the Desktop GUI experience for new users.

     

    Added support for Intel GVT-g, which lets you split your Intel i915 iGPU into multiple virtual GPUs and pass them through to multiple VMs, using @ich777's Intel-GVT-g plugin.

     

    Added support for gnif/vendor-reset.  This simplifies @ich777's AMD Vendor Reset plugin which permits users to get their AMD video cards to reset properly.

     

    Base Packages

    Virtually the entire base package set has been updated.

     

    Other improvements available in 6.10, which are maybe not so obvious to spot from the release notes and some of these improvements are internal and not really visible:

     

     

    Event driven model to obtain server information and update the webGUI in real-time

    • The advantage of this model is its scalability. Multiple browsers can be opened simultaneously to the webGUI without much impact
    • In addition stale browser sessions won't create any CSRF errors anymore
    • People who keep their browser open 24/7 will find the webGUI stays responsive at all times

     

    Docker labels

    • Docker labels are added to allow people using Docker compose to make use of icons and GUI access
    • Look at a Docker 'run' command output to see exactly what labels are used

     

    Docker custom networks

    • A new setting for custom networks is available. Originally custom networks are created using the macvlan mode, and this mode is kept when upgrading to version 6.10
    • The new ipvlan mode is introduced to battle the crashes some people experience when using macvlan mode. If that is your case, change to ipvlan mode and test. Changing of mode does not require to reconfigure anything on Docker level, internally everything is being taken care off.

     

    Docker bridge network (docker0)

    • docker0 now supports IPv6. This is implemented by assigning docker0 a private IPv6 subnet (fd17::/64), similar to what is done for IPv4 and use network translation to communicate with the outside world
    • Containers connected to the bridge network now have both IPv4 and IPv6 connectivity (of course the system must have IPv6 configured in the network configuration)
    • In addition several enhancements are made in the IPv6 implementation to better deal with the use (or no-use) of IPv6

     

    Plugins page

    • The plugins page now loads information in two steps. First the list of plugins is created and next the more time consuming plugin status field is retrieved in the background. The result is a faster loading plugins page, especially when you have a lot of plugins installed

     

    Dashboard graphs

    • The dashboard has now two graphs available. The CPU graph is displayed by default, while the NETWORK graph is a new option under Interface (see the 'General Info' selection)
    • The CPU graph may be hidden as well in case it is not desired
    • Both graphs have a configurable time-line, which is by default 30 seconds and can be changed independently for each graph to see a longer or shorter history.
    • Graphs are updated in real-time and are useful to observe the behavior of the server under different circumstances

     

    Other Changes

    • We switched to a better-maintained version of the WSD server component called wsdd2 in an effort to eliminate instances where the wsd daemon would start consuming 100% of a CPU core.
    • Fixed issue where you couldn't create a docker image on a share name that contains a space.
    • Fixed issue where 'mover' would not move to a pool name that contains a space.
    • Fixed issue in User Share file system where permissions were not being honored.
    • We increased the font size in Terminal.
    • Many other small bug fixes and improvements.

     

    Credits

    Special thanks to all our beta testers and especially:

    @bonienl for his continued refinement and updating of the Dynamix webGUI.

    @Squid for continued refinement of Community Apps and associated feed.

    @dlandon for continued refinement of Unassigned Devices plugin and patience as we change things under the hood.

    @ich777 for assistance and passing on knowledge of Linux kernel config changes to support third party drivers and other kernel-related functionality via plugins.

    @SimonF for refinements to System Devices page and other webGUI improvements.  We intend to merge your mover progress changes during this RC series.

     


     

    Version 6.10.0-rc1 2021-08-07

     

    Base distro:

    • aaa_base: version 15.0
    • aaa_glibc-solibs: version 2.33
    • aaa_libraries: version 15.0
    • acl: version 2.3.1
    • acpid: version 2.0.32
    • adwaita-icon-theme: version 40.1.1
    • apcupsd: version 3.14.14
    • appres: version 1.0.5
    • at: version 3.2.2
    • at-spi2-atk: version 2.38.0
    • at-spi2-core: version 2.40.3
    • atk: version 2.36.0
    • attr: version 2.5.1
    • avahi: version 0.8
    • bash: version 5.1.008
    • beep: version 1.3
    • bin: version 11.1
    • bind: version 9.16.19
    • bluez-firmware: version 1.2
    • bridge-utils: version 1.7.1
    • brotli: version 1.0.9
    • btrfs-progs: version 5.13.1
    • bzip2: version 1.0.8
    • ca-certificates: version 20210526
    • cairo: version 1.16.0
    • celt051: version 0.5.1.3
    • cifs-utils: version 6.13
    • coreutils: version 8.32
    • cpio: version 2.13
    • cpufrequtils: version 008
    • cracklib: version 2.9.7
    • cryptsetup: version 2.3.6
    • curl: version 7.78.0
    • cyrus-sasl: version 2.1.27
    • db48: version 4.8.30
    • dbus: version 1.12.20
    • dbus-glib: version 0.112
    • dcron: version 4.5
    • dejavu-fonts-ttf: version 2.37
    • devs: version 2.3.1
    • dhcpcd: version 8.1.9
    • diffutils: version 3.8
    • dmidecode: version 3.3
    • dnsmasq: version 2.85
    • docker: version 20.10.6
    • dosfstools: version 4.2
    • e2fsprogs: version 1.46.3
    • ebtables: version 2.0.11
    • editres: version 1.0.7
    • eject: version 2.1.5
    • elogind: version 246.10
    • elvis: version 2.2_0
    • encodings: version 1.0.5
    • etc: version 15.0
    • ethtool: version 5.13
    • eudev: version 3.2.10
    • file: version 5.40
    • findutils: version 4.8.0
    • flex: version 2.6.4
    • floppy: version 5.5
    • fluxbox: version 1.3.7
    • fontconfig: version 2.13.92
    • freeglut: version 3.2.1
    • freetype: version 2.11.0
    • fribidi: version 1.0.10
    • fuse3: version 3.10.4
    • gawk: version 5.1.0
    • gd: version 2.3.2
    • gdbm: version 1.20
    • gdk-pixbuf2: version 2.42.6
    • genpower: version 1.0.5
    • getty-ps: version 2.1.0b
    • git: version 2.32.0
    • glew: version 2.2.0
    • glib2: version 2.68.3
    • glibc: version 2.33
    • glibc-zoneinfo: version 2021a
    • glu: version 9.0.2
    • gmp: version 6.2.1
    • gnutls: version 3.6.16
    • gptfdisk: version 1.0.8
    • graphite2: version 1.3.14
    • grep: version 3.6
    • gtk+3: version 3.24.30
    • gzip: version 1.10
    • harfbuzz: version 2.8.2
    • haveged: version 1.9.14
    • hdparm: version 9.62
    • hicolor-icon-theme: version 0.17
    • hostname: version 3.23
    • htop: version 3.0.5
    • hwloc: version 2.2.0
    • icu4c: version 69.1
    • imlib2: version 1.7.1
    • inetd: version 1.79s
    • infozip: version 6.0
    • inih: version 53
    • inotify-tools: version 3.20.11.0
    • iproute2: version 5.13.0
    • iptables: version 1.8.7
    • iputils: version 20210722
    • irqbalance: version 1.7.0
    • jansson: version 2.13.1
    • jemalloc: version 5.2.1
    • jq: version 1.6
    • json-c: version 0.15_20200726
    • keyutils: version 1.6.3
    • kmod: version 29
    • krb5: version 1.19.2
    • lbzip2: version 2.5
    • less: version 590
    • libICE: version 1.0.10
    • libSM: version 1.2.3
    • libX11: version 1.7.2
    • libXau: version 1.0.9
    • libXaw: version 1.0.14
    • libXcomposite: version 0.4.5
    • libXcursor: version 1.2.0
    • libXdamage: version 1.1.5
    • libXdmcp: version 1.1.3
    • libXevie: version 1.0.3
    • libXext: version 1.3.4
    • libXfixes: version 6.0.0
    • libXfont: version 1.5.2
    • libXfont2: version 2.0.5
    • libXfontcache: version 1.0.5
    • libXft: version 2.3.4
    • libXi: version 1.7.10
    • libXinerama: version 1.1.4
    • libXmu: version 1.1.3
    • libXpm: version 3.5.13
    • libXrandr: version 1.5.2
    • libXrender: version 0.9.10
    • libXres: version 1.2.1
    • libXt: version 1.2.1
    • libXtst: version 1.2.3
    • libXxf86dga: version 1.1.5
    • libXxf86misc: version 1.0.4
    • libXxf86vm: version 1.1.4
    • libaio: version 0.3.112
    • libarchive: version 3.5.1
    • libcap-ng: version 0.8.2
    • libcgroup: version 0.41
    • libdaemon: version 0.14
    • libdmx: version 1.1.4
    • libdrm: version 2.4.107
    • libedit: version 20210714_3.1
    • libepoxy: version 1.5.8
    • libestr: version 0.1.9
    • libevdev: version 1.11.0
    • libevent: version 2.1.12
    • libfastjson: version 0.99.9
    • libffi: version 3.3
    • libfontenc: version 1.1.4
    • libgcrypt: version 1.9.3
    • libglvnd: version 1.3.3
    • libgpg-error: version 1.42
    • libgudev: version 236
    • libidn: version 1.38
    • libjpeg-turbo: version 2.1.0
    • liblogging: version 1.0.6
    • libmnl: version 1.0.4
    • libnetfilter_conntrack: version 1.0.8
    • libnfnetlink: version 1.0.1
    • libnftnl: version 1.2.0
    • libnl3: version 3.5.0
    • libpcap: version 1.10.1
    • libpciaccess: version 0.16
    • libpng: version 1.6.37
    • libpsl: version 0.21.1
    • libpthread-stubs: version 0.4
    • libseccomp: version 2.5.1
    • libssh: version 0.9.5
    • libssh2: version 1.9.0
    • libtasn1: version 4.17.0
    • libtiff: version 4.3.0
    • libtiff: version 4.3.0
    • libtirpc: version 1.3.2
    • libunistring: version 0.9.10
    • libunwind: version 1.5.0
    • libusb: version 1.0.24
    • libusb-compat: version 0.1.7
    • libuv: version 1.41.0
    • libvirt: version 7.3.0
    • libvirt-php: version 0.5.5
    • libwebp: version 1.2.0
    • libwebsockets: version 4.2.0
    • libx86: version 1.1
    • libxcb: version 1.14
    • libxkbcommon: version 1.3.0
    • libxkbfile: version 1.1.0
    • libxml2: version 2.9.12
    • libxshmfence: version 1.3
    • libxslt: version 1.1.34
    • libzip: version 1.8.0
    • listres: version 1.0.4
    • lm_sensors: version 3.6.0
    • lmdb: version 0.9.29
    • logrotate: version 3.18.1
    • lshw: version B.02.19.2
    • lsof: version 4.94.0
    • lsscsi: version 0.32
    • lvm2: version 2.03.12
    • lz4: version 1.9.3
    • lzip: version 1.22
    • lzo: version 2.10
    • mc: version 4.8.26
    • miniupnpc: version 2.1
    • mkfontscale: version 1.2.1
    • mpfr: version 4.1.0
    • mtdev: version 1.1.6
    • nano: version 5.8
    • ncompress: version 5.0
    • ncurses: version 6.2_20201219
    • net-tools: version 20181103_0eebece
    • nettle: version 3.7.3
    • network-scripts: version 15.0
    • nfs-utils: version 2.5.4
    • nghttp2: version 1.44.0
    • nginx: version 1.19.9
    • nss-mdns: version 0.14.1
    • ntfs-3g: version 2017.3.23
    • ntp: version 4.2.8p15
    • numactl: version 2.0.13
    • oniguruma: version 6.9.7
    • openssh: version 8.6p1
    • openssl: version 1.1.1k
    • openssl-solibs: version 1.1.1k
    • p11-kit: version 0.24.0
    • pam: version 1.5.1
    • pango: version 1.48.7
    • patch: version 2.7.6
    • pciutils: version 3.7.0
    • pcre: version 8.45
    • pcre2: version 10.37
    • php: version 7.4.18
    • pixman: version 0.40.0
    • pkgtools: version 15.0
    • procps-ng: version 3.3.17
    • pv: version 1.6.6
    • qemu: version 6.0.0
    • qrencode: version 4.1.1
    • reiserfsprogs: version 3.6.27
    • rpcbind: version 1.2.5
    • rsync: version 3.2.3
    • rsyslog: version 8.2102.0
    • sakura: version 3.5.0
    • samba: version 4.12.15
    • sdparm: version 1.12
    • sed: version 4.8
    • sessreg: version 1.1.2
    • setxkbmap: version 1.3.2
    • sg3_utils: version 1.46
    • shadow: version 4.8.1
    • shared-mime-info: version 2.1
    • slim: version 1.3.6
    • smartmontools: version 7.2
    • spice: version 0.15.0
    • sqlite: version 3.36.0
    • ssmtp: version 2.64
    • startup-notification: version 0.12
    • sudo: version 1.9.7p2
    • sysfsutils: version 2.1.0
    • sysvinit: version 2.99
    • sysvinit-scripts: version 15.0
    • talloc: version 2.3.2
    • tar: version 1.34
    • tcp_wrappers: version 7.6
    • tdb: version 1.4.5
    • telnet: version 0.17
    • tevent: version 0.11.0
    • traceroute: version 2.1.0
    • transset: version 1.0.2
    • tree: version 1.8.0
    • ttyd: version 20210507
    • usbredir: version 0.8.0
    • usbutils: version 013
    • utempter: version 1.2.0
    • util-linux: version 2.37.1
    • vbetool: version 1.2.2
    • vsftpd: version 3.0.5
    • vte3: version 0.50.2
    • wayland: version 1.19.0
    • wget: version 1.21.1
    • which: version 2.21
    • wireguard-tools: version 1.0.20210424
    • wsdd2: version 1.8.3.2
    • xauth: version 1.1
    • xcb-util: version 0.4.0
    • xclock: version 1.0.9
    • xdpyinfo: version 1.3.2
    • xdriinfo: version 1.0.6
    • xev: version 1.2.4
    • xf86-input-evdev: version 2.10.6
    • xf86-input-keyboard: version 1.9.0
    • xf86-input-mouse: version 1.9.3
    • xf86-input-synaptics: version 1.9.1
    • xf86-video-ast: version 1.1.5
    • xf86-video-mga: version 2.0.0
    • xf86-video-vesa: version 2.5.0
    • xfsprogs: version 5.12.0
    • xhost: version 1.0.8
    • xinit: version 1.4.1
    • xkbcomp: version 1.4.5
    • xkbevd: version 1.1.4
    • xkbutils: version 1.0.4
    • xkeyboard-config: version 2.33
    • xkill: version 1.0.5
    • xload: version 1.1.3
    • xlsatoms: version 1.1.3
    • xlsclients: version 1.1.4
    • xmessage: version 1.0.5
    • xmodmap: version 1.0.10
    • xorg-server: version 1.20.13
    • xprop: version 1.2.5
    • xrandr: version 1.5.1
    • xrdb: version 1.2.0
    • xrefresh: version 1.0.6
    • xset: version 1.2.4
    • xsetroot: version 1.1.2
    • xsm: version 1.0.4
    • xterm: version 368
    • xtrans: version 1.4.0
    • xwd: version 1.0.8
    • xwininfo: version 1.1.5
    • xwud: version 1.0.5
    • xxHash: version 0.8.0
    • xz: version 5.2.5
    • yajl: version 2.1.0
    • zlib: version 1.2.11
    • zstd: version 1.5.0

    Linux kernel:

    • version 5.13.8 (CVE-2021-33909 CVE-2021-33910)
    • CONFIG_USB4: Unified support for USB4 and Thunderbolt
    • CONFIG_USB4_NET: Networking over USB4 and Thunderbolt cables
    • CONFIG_DRM_I915_GVT: Enable Intel GVT-g graphics virtualization host support
    • CONFIG_DRM_I915_GVT_KVMGT: Enable KVM/VFIO support for Intel GVT-g
    • CONFIG_VFIO_MDEV: Mediated device driver framework
    • CONFIG_VFIO_MDEV_DEVICE: VFIO driver for Mediated devices
    • CONFIG_FTRACE: Tracers
    • CONFIG_FUNCTION_TRACER: Kernel Function Tracer
    • CONFIG_KPROBES: Kprobes
    • CONFIG_DEBUG_KERNEL: Kernel debugging
    • CONFIG_KALLSYMS_ALL: Include all symbols in kallsyms
    • CONFIG_X86_X32: removed
    • md_unraid: version 2.9.18

    Management:

    • emhttp new defaults:
      - root password required
      - newly created shares not exported by default
      - predefined 'flash' share not exported by default
      - ftp, ssh, telnet: disabled by default
      - NetBIOS disabled by default
      - WSD enabled (and using newer 'wsdd2' package)
      - Enhanced macOS interoperability enabled
    • mover: fix bug not moving shares with embedded spaces
    • shfs: fix bug where permissions being ingored ('default_permissions' was missing in mount command)
    • webgui: support simultanious LAN SSL with self-signed cert and DNS-based SSL with Lets Encrypt cert
    • webgui: Suppress non-relevant IPv6 routes in routing table
    • webgui: Fixed smart temperature settings sometimes not possible
    • webgui: Add internal container reference
    • webgui: Diagnostics: Remove lines from go containing passwords etc
    • webgui: Better translation of docker container variables
    • webgui: Fix monitor false positives
    • webgui: Allow ruleset for local rules in rsyslog.conf
    • webgui: Include links in email and Discord agent notifications
    • webgui: Allow all notification agents to send links
    • webgui: Validate WebGUI ports before applying
    • webgui: Add vmxnet3 and e1000 into available NICs for VMs
    • webgui: Error checking etc on ports for syslog server
    • webgui: Check for flash offline / quick check on if it is corrupted
    • webgui: Only allow png files to be uploaded as user image
    • webgui: Diagnostics: Revamp anonymization
    • webgui: Add WireGuard GUI
    • webgui: Update DashStats.page
    • webgui: Bug fix in DashStats
    • webgui: Fix corruption check after a New Config is issued
    • webgui: Update alert text
    • webgui: Translation support (Unraid.net)
    • webgui: WireGuard: preset peer DNS server with "Remote tunneled access"
    • webgui: Plugins page loading improvements
    • webgui: Docker page loading improvements
    • webgui: Make WireGuard trademark visible on "full" page
    • webgui: Replace polling scripts with event driven Nchan interface
    • webgui: Improved format of stale and error plugin pages
    • webgui: Docker: Add crypto as a category
    • webgui: Dashboard: add CPU and NETWORK chart
    • webgui: Docker: compress too long author names
    • webgui: Convert notify polling to Nchan
    • webgui: Docker: process bash ANSI colors in web log display
    • webgui: dockerMan: remove HTML from descriptions
    • webgui: SSH authorized keys UI
    • webgui: Device_list replace .png icon with font icon
    • webgui: Compress too long share names in dropdown menus
    • webgui: Show management access and shares access groups for users
    • webgui: Added "User 'root'" reference on Management Access page
    • webgui: Show warning when javascript is disabled
    • webgui: Force creation of root password
    • webgui: Edit/Add Container: Fix browser console error
    • webgui: WireGuard: warn when directly connected with public IP
    • webgui: Fix network bonding display
    • webgui: Add tracking after system shutdown
    • webgui: Added notify when plugin fails to install
    • webgui: Add Apps link to install CA
    • webgui: Diagnostics: Add share summary
    • webgui: Suppress IPv6 anycast addresses in routing table
    • webgui: Diagnostics: Add share summary
    • webgui: Diagnostics: Include current plugin versions
    • webgui: Diagnostics: add DHCP log
    • webgui: Diagnostics fix plugin deprecated max version error
    • webgui: Docker: Support CA tag
    • webgui: Delete DockerRepositories.page
    • webgui: dockerMan Security: Remove HTML tags from Config elements
    • webgui: When viewing source, identify which .page file is responsible
    • webgui: System devices additions
    • webgui: Create syslog entry when user logs out
    • webgui: privatize host in diagnostics
    • webgui: Create favicon.ico
    • webgui: Update Credits.page
    • Like 22



    User Feedback

    Recommended Comments



    6 hours ago, ljm42 said:

     

    Interesting. I see my system is reporting this for each vfio binding as well:
      Error: unable to adjust group ownership of /dev/vfio/xx


    My devices are being passed through to VMs just fine though, so I don't think this is the issue.

     

    Nothing else stands out to me in the diagnostics, hopefully someone else will see something.

     

    thanks; hopefully someone can assist soon.. or ill have to rollback. I need the vms :)

     

    image.png.168d1990fbe3db2f5e726d852381ac49.png

    jj-diagnostics-20210808-1624.zip

    Link to comment
    1 hour ago, Squid said:

    Try this.  Settings - Docker.  Enable Docker - No.  Delete the image.  REBOOT.  Settings - Docker - Ensure the size is between 10 and 20 then re-enable.

     

    If that fails, create a new topic in General Support as it's outside the realm of what this thread is all about.

    An update if anyone experiences anything similar:

     

    I put the flash disk into my fedora laptop and backed up all files. Formatted the flash disk, remade it using the downloadable zip from the home page for 9.6.2 then copied all of my configuration files from the backup I made. Luckily, when all of this started I also made a backup of the original docker.img file. After booting the newly made Unraid disk, I upgraded to 6.10rc1 successfully. Then I restored the original docker.img and everything is back like nothing ever happened.

     

    Thanks for your help. Thanks for all the hard work on this new update, Limetech staff. :)

    Link to comment
    34 minutes ago, loukaniko85 said:

     

    thanks; hopefully someone can assist soon.. or ill have to rollback. I need the vms :)

     

    image.png.168d1990fbe3db2f5e726d852381ac49.png

    jj-diagnostics-20210808-1624.zip 128.27 kB · 2 downloads

    Try deselecting the nvme you're passing through in Tools - System Devices, Apply then reselect it and apply followed by a reboot.

     

    @ljm42, vfio-pci.cfg shows it being bound, but the OS is still loading the nvme driver for it.

    Link to comment
    22 minutes ago, Squid said:

    Try deselecting the nvme you're passing through in Tools - System Devices, Apply then reselect it and apply followed by a reboot.

     

    @ljm42, vfio-pci.cfg shows it being bound, but the OS is still loading the nvme driver for it.

     

    sadly no, same issue; though i do have 2 nvmes; 1 passthrough and 1 cache.. perhaps that is why it is showing as being loaded. Also, am having same error on other vms, which do not have the nvme passthrough..

     

    - seems to only occur with gpu passthrough. nvme passes, usb controller passes..

    Edited by loukaniko85
    Link to comment
    20 hours ago, johnwhicker said:

    Someone please help me understand this?  What if I don't wanna associate my keys  and my home installs with my unraid forum account?  I really like my privacy honestly and what is is my home have no business being associated with any cloud or external servers.  This is a very slippery slope and I just don't like it.  Is there an option to continue be offline just the way I am right now? I just don't want to be part of this new ecosystem unraid is creating.  I trust my privacy and I trust no one, I am sorry.....  And there’s absolutely no reason why you can’t support both ways of activating / running unraid. I should not be forced to connect with you if I have a valid key.

    I also do not like where this is heading. One of the reasons I chose unraid is because how I can keep it local. The less I put out to the open world, the better. If this is the way forward, I will be staying on 6.9 until I can find and implement a solution that lets me off the cloud as much as possible.

    • Like 1
    • Thanks 2
    Link to comment
    1 hour ago, loukaniko85 said:

     

    sadly no, same issue; though i do have 2 nvmes; 1 passthrough and 1 cache.. perhaps that is why it is showing as being loaded. Also, am having same error on other vms, which do not have the nvme passthrough..

     

    - seems to only occur with gpu passthrough. nvme passes, usb controller passes..

     

    I disabled csm and now vms can turn on without that error - though no display and vm log show

     

    2021-08-09T02:16:33.519687Z qemu-system-x86_64: vfio_region_write(0000:2e:00.0:region1+0xbd1df, 0x0,1) failed: Device or resource busy
    2021-08-09T02:16:33.519692Z qemu-system-x86_64: vfio_region_write(0000:2e:00.0:region1+0xbd1e0, 0x0,1) failed: Device or resource busy
    2021-08-09T02:16:33.519703Z qemu-system-x86_64: vfio_region_write(0000:2e:00.0:region1+0xbd1e1, 0x0,1) failed: Device or resource busy
    2021-08-09T02:16:33.519714Z qemu-system-x86_64: vfio_region_write(0000:2e:00.0:region1+0xbd1e2, 0x0,1) failed: Device or resource busy
    2021-08-09T02:16:33.519720Z qemu-system-x86_64: vfio_region_write(0000:2e:00.0:region1+0xbd1e3, 0x0,1) failed: Device or resource busy
    2021-08-09T02:16:33.519726Z qemu-system-x86_64: vfio_region_write(0000:2e:00.0:region1+0xbd1e4, 0x0,1) failed: Device or resource busy
    2021-08-09T02:16:33.519732Z qemu-system-x86_64: vfio_region_write(0000:2e:00.0:region1+0xbd1e5, 0x0,1) failed: Device or resource busy
    2021-08-09T02:16:33.519738Z qemu-system-x86_64: vfio_region_write(0000:2e:00.0:region1+0xbd1e6, 0x0,1) failed: Device or resource busy
    2021-08-09T02:16:33.519743Z qemu-system-x86_64: vfio_region_write(0000:2e:00.0:region1+0xbd1e7, 0x0,1) failed: Device or resource busy
    2021-08-09T02:16:33.519748Z qemu-system-x86_64: vfio_region_write(0000:2e:00.0:region1+0xbd1e8, 0x0,1) failed: Device or resource busy
    2021-08-09T02:16:33.519753Z qemu-system-x86_64: vfio_region_write(0000:2e:00.0:region1+0xbd1e9, 0x0,1) failed: Device or resource busy
    2021-08-09T02:16:33.519758Z qemu-system-x86_64: vfio_region_write(0000:2e:00.0:region1+0xbd1ea, 0x0,1) failed: Device or resource busy
    2021-08-09T02:16:33.519763Z qemu-system-x86_64: vfio_region_write(0000:2e:00.0:region1+0xbd1eb, 0x0,1) failed: Device or resource busy
    2021-08-09T02:16:33.519768Z qemu-system-x86_64: vfio_region_write(0000:2e:00.0:region1+0xbd1ec, 0x0,1) failed: Device or resource busy
    2021-08-09T02:16:33.519773Z qemu-system-x86_64: vfio_region_write(0000:2e:00.0:region1+0xbd1ed, 0x0,1) failed: Device or resource busy
    2021-08-09T02:16:33.519779Z qemu-system-x86_64: vfio_region_write(0000:2e:00.0:region1+0xbd1ee, 0x0,1) failed: Device or resource busy
    2021-08-09T02:16:33.519784Z qemu-system-x86_64: vfio_region_write(0000:2e:00.0:region1+0xbd1ef, 0x0,1) failed: Device or resource busy
    2021-08-09T02:16:33.519789Z qemu-system-x86_64: vfio_region_write(0000:2e:00.0:region1+0xbd1f0, 0x0,1) failed: Device or resource busy
    2021-08-09T02:16:33.519795Z qemu-system-x86_64: vfio_region_write(0000:2e:00.0:region1+0xbd1f1, 0x0,1) failed: Device or resource busy
    2021-08-09T02:16:33.519800Z qemu-system-x86_64: vfio_region_write(0000:2e:00.0:region1+0xbd1f2, 0x0,1) failed: Device or resource busy
    2021-08-09T02:16:33.519805Z qemu-system-x86_64: vfio_region_write(0000:2e:00.0:region1+0xbd1f3, 0x0,1) failed: Device or resource busy
    2021-08-09T02:16:33.519810Z qemu-system-x86_64: vfio_region_write(0000:2e:00.0:region1+0xbd1f4, 0x0,1) failed: Device or resource busy
    2021-08-09T02:16:33.519815Z qemu-system-x86_64: vfio_region_write(0000:2e:00.0:region1+0xbd1f5, 0x0,1) failed: Device or resource busy
    2021-08-09T02:16:33.519820Z qemu-system-x86_64: vfio_region_write(0000:2e:00.0:region1+0xbd1f6, 0x0,1) failed: Device or resource busy
    2021-08-09T02:16:33.519825Z qemu-system-x86_64: vfio_region_write(0000:2e:00.0:region1+0xbd1f7, 0x0,1) failed: Device or resource busy
    2021-08-09T02:16:33.519831Z qemu-system-x86_64: vfio_region_write(0000:2e:00.0:region1+0xbd1f8, 0x0,1) failed: Device or resource busy
    2021-08-09T02:16:33.519836Z qemu-system-x86_64: vfio_region_write(0000:2e:00.0:region1+0xbd1f9, 0x0,1) failed: Device or resource busy
    2021-08-09T02:16:33.519841Z qemu-system-x86_64: vfio_region_write(0000:2e:00.0:region1+0xbd1fa, 0x0,1) failed: Device or resource busy
    2021-08-09T02:16:33.519846Z qemu-system-x86_64: vfio_region_write(0000:2e:00.0:region1+0xbd1fb, 0x0,1) failed: Device or resource busy
    2021-08-09T02:16:33.519851Z qemu-system-x86_64: vfio_region_write(0000:2e:00.0:region1+0xbd1fc, 0x0,1) failed: Device or resource busy
    2021-08-09T02:16:33.519856Z qemu-system-x86_64: vfio_region_write(0000:2e:00.0:region1+0xbd1fd, 0x0,1) failed: Device or resource busy
    2021-08-09T02:16:33.519861Z qemu-system-x86_64: vfio_region_write(0000:2e:00.0:region1+0xbd1fe, 0x0,1) failed: Device or resource busy
    2021-08-09T02:16:33.519866Z qemu-system-x86_64: vfio_region_write(0000:2e:00.0:region1+0xbd1ff, 0x0,1) failed: Device or resource busy
    2021-08-09T02:16:33.519871Z qemu-system-x86_64: vfio_region_write(0000:2e:00.0:region1+0xbd200, 0x0,1) failed: Device or resource busy
    2021-08-09T02:16:33.519876Z qemu-system-x86_64: vfio_region_write(0000:2e:00.0:region1+0xbd201, 0x0,1) failed: Device or resource busy
    2021-08-09T02:16:33.519882Z qemu-system-x86_64: vfio_region_write(0000:2e:00.0:region1+0xbd202, 0x0,1) failed: Device or resource busy
    2021-08-09T02:16:33.519887Z qemu-system-x86_64: vfio_region_write(0000:2e:00.0:region1+0xbd203, 0x0,1) failed: Device or resource busy
    2021-08-09T02:16:33.519892Z qemu-system-x86_64: vfio_region_write(0000:2e:00.0:region1+0xbd204, 0x0,1) failed: Device or resource busy
    2021-08-09T02:16:33.519897Z qemu-system-x86_64: vfio_region_write(0000:2e:00.0:region1+0xbd205, 0x0,1) failed: Device or resource busy

    Link to comment
    1 hour ago, LTM said:

    I also do not like where this is heading. One of the reasons I chose unraid is because how I can keep it local. The less I put out to the open world, the better. If this is the way forward, I will be staying on 6.9 until I can find and implement a solution that lets me off the cloud as much as possible.

     

    Where do you think this is "heading"?  Any "cloud" services and features we offer are, and will continue to be completely "opt in" with the default being "opt out".

    • Like 4
    Link to comment
    2 hours ago, loukaniko85 said:

     

    I disabled csm and now vms can turn on without that error - though no display and vm log show

     

    2021-08-09T02:16:33.519687Z qemu-system-x86_64: vfio_region_write(0000:2e:00.0:region1+0xbd1df, 0x0,1) failed: Device or resource busy
    2021-08-09T02:16:33.519692Z qemu-system-x86_64: vfio_region_write(0000:2e:00.0:region1+0xbd1e0, 0x0,1) failed: Device or resource busy
    2021-08-09T02:16:33.519703Z qemu-system-x86_64: vfio_region_write(0000:2e:00.0:region1+0xbd1e1, 0x0,1) failed: Device or resource busy
    2021-08-09T02:16:33.519714Z qemu-system-x86_64: vfio_region_write(0000:2e:00.0:region1+0xbd1e2, 0x0,1) failed: Device or resource busy
    2021-08-09T02:16:33.519720Z qemu-system-x86_64: vfio_region_write(0000:2e:00.0:region1+0xbd1e3, 0x0,1) failed: Device or resource busy
    2021-08-09T02:16:33.519726Z qemu-system-x86_64: vfio_region_write(0000:2e:00.0:region1+0xbd1e4, 0x0,1) failed: Device or resource busy
    2021-08-09T02:16:33.519732Z qemu-system-x86_64: vfio_region_write(0000:2e:00.0:region1+0xbd1e5, 0x0,1) failed: Device or resource busy
    2021-08-09T02:16:33.519738Z qemu-system-x86_64: vfio_region_write(0000:2e:00.0:region1+0xbd1e6, 0x0,1) failed: Device or resource busy
    2021-08-09T02:16:33.519743Z qemu-system-x86_64: vfio_region_write(0000:2e:00.0:region1+0xbd1e7, 0x0,1) failed: Device or resource busy
    2021-08-09T02:16:33.519748Z qemu-system-x86_64: vfio_region_write(0000:2e:00.0:region1+0xbd1e8, 0x0,1) failed: Device or resource busy
    2021-08-09T02:16:33.519753Z qemu-system-x86_64: vfio_region_write(0000:2e:00.0:region1+0xbd1e9, 0x0,1) failed: Device or resource busy
    2021-08-09T02:16:33.519758Z qemu-system-x86_64: vfio_region_write(0000:2e:00.0:region1+0xbd1ea, 0x0,1) failed: Device or resource busy
    2021-08-09T02:16:33.519763Z qemu-system-x86_64: vfio_region_write(0000:2e:00.0:region1+0xbd1eb, 0x0,1) failed: Device or resource busy
    2021-08-09T02:16:33.519768Z qemu-system-x86_64: vfio_region_write(0000:2e:00.0:region1+0xbd1ec, 0x0,1) failed: Device or resource busy
    2021-08-09T02:16:33.519773Z qemu-system-x86_64: vfio_region_write(0000:2e:00.0:region1+0xbd1ed, 0x0,1) failed: Device or resource busy
    2021-08-09T02:16:33.519779Z qemu-system-x86_64: vfio_region_write(0000:2e:00.0:region1+0xbd1ee, 0x0,1) failed: Device or resource busy
    2021-08-09T02:16:33.519784Z qemu-system-x86_64: vfio_region_write(0000:2e:00.0:region1+0xbd1ef, 0x0,1) failed: Device or resource busy
    2021-08-09T02:16:33.519789Z qemu-system-x86_64: vfio_region_write(0000:2e:00.0:region1+0xbd1f0, 0x0,1) failed: Device or resource busy
    2021-08-09T02:16:33.519795Z qemu-system-x86_64: vfio_region_write(0000:2e:00.0:region1+0xbd1f1, 0x0,1) failed: Device or resource busy
    2021-08-09T02:16:33.519800Z qemu-system-x86_64: vfio_region_write(0000:2e:00.0:region1+0xbd1f2, 0x0,1) failed: Device or resource busy
    2021-08-09T02:16:33.519805Z qemu-system-x86_64: vfio_region_write(0000:2e:00.0:region1+0xbd1f3, 0x0,1) failed: Device or resource busy
    2021-08-09T02:16:33.519810Z qemu-system-x86_64: vfio_region_write(0000:2e:00.0:region1+0xbd1f4, 0x0,1) failed: Device or resource busy
    2021-08-09T02:16:33.519815Z qemu-system-x86_64: vfio_region_write(0000:2e:00.0:region1+0xbd1f5, 0x0,1) failed: Device or resource busy
    2021-08-09T02:16:33.519820Z qemu-system-x86_64: vfio_region_write(0000:2e:00.0:region1+0xbd1f6, 0x0,1) failed: Device or resource busy
    2021-08-09T02:16:33.519825Z qemu-system-x86_64: vfio_region_write(0000:2e:00.0:region1+0xbd1f7, 0x0,1) failed: Device or resource busy
    2021-08-09T02:16:33.519831Z qemu-system-x86_64: vfio_region_write(0000:2e:00.0:region1+0xbd1f8, 0x0,1) failed: Device or resource busy
    2021-08-09T02:16:33.519836Z qemu-system-x86_64: vfio_region_write(0000:2e:00.0:region1+0xbd1f9, 0x0,1) failed: Device or resource busy
    2021-08-09T02:16:33.519841Z qemu-system-x86_64: vfio_region_write(0000:2e:00.0:region1+0xbd1fa, 0x0,1) failed: Device or resource busy
    2021-08-09T02:16:33.519846Z qemu-system-x86_64: vfio_region_write(0000:2e:00.0:region1+0xbd1fb, 0x0,1) failed: Device or resource busy
    2021-08-09T02:16:33.519851Z qemu-system-x86_64: vfio_region_write(0000:2e:00.0:region1+0xbd1fc, 0x0,1) failed: Device or resource busy
    2021-08-09T02:16:33.519856Z qemu-system-x86_64: vfio_region_write(0000:2e:00.0:region1+0xbd1fd, 0x0,1) failed: Device or resource busy
    2021-08-09T02:16:33.519861Z qemu-system-x86_64: vfio_region_write(0000:2e:00.0:region1+0xbd1fe, 0x0,1) failed: Device or resource busy
    2021-08-09T02:16:33.519866Z qemu-system-x86_64: vfio_region_write(0000:2e:00.0:region1+0xbd1ff, 0x0,1) failed: Device or resource busy
    2021-08-09T02:16:33.519871Z qemu-system-x86_64: vfio_region_write(0000:2e:00.0:region1+0xbd200, 0x0,1) failed: Device or resource busy
    2021-08-09T02:16:33.519876Z qemu-system-x86_64: vfio_region_write(0000:2e:00.0:region1+0xbd201, 0x0,1) failed: Device or resource busy
    2021-08-09T02:16:33.519882Z qemu-system-x86_64: vfio_region_write(0000:2e:00.0:region1+0xbd202, 0x0,1) failed: Device or resource busy
    2021-08-09T02:16:33.519887Z qemu-system-x86_64: vfio_region_write(0000:2e:00.0:region1+0xbd203, 0x0,1) failed: Device or resource busy
    2021-08-09T02:16:33.519892Z qemu-system-x86_64: vfio_region_write(0000:2e:00.0:region1+0xbd204, 0x0,1) failed: Device or resource busy
    2021-08-09T02:16:33.519897Z qemu-system-x86_64: vfio_region_write(0000:2e:00.0:region1+0xbd205, 0x0,1) failed: Device or resource busy

    enabled custom CSM in my bios

     

    Launch Storage OpROM Policy - UEFI only

    Launch Video OpROM Policy - Legacy only

     

    All working :) thanks gents.

    • Like 1
    Link to comment
    4 hours ago, limetech said:

     

    Where do you think this is "heading"?  Any "cloud" services and features we offer are, and will continue to be completely "opt in" with the default being "opt out".

    "Starting with this release, it will be necessary for a new user to either sign-in with existing forum credentials or sign-up, creating a new account via the UPC in order to download a Trial key.  All key purchases and upgrades are also handled exclusively via the UPC."

     

    I do also think this needs more clarification for current users who don't want to sign or associate their servers with

    UPC regarding key management. How it will be handled in the future etc...

     

     

    • Like 2
    • Thanks 2
    Link to comment
    45 minutes ago, perrycox said:

    I do also think this needs more clarification for current users who don't want to sign or associate their servers with

    UPC regarding key management. How it will be handled in the future etc...

    I don't see why this is a privacy concern in any way...

    The process is super simple and I also used it a few days ago to replace my key and it is way easier to replace your key that way.

    Btw you had to register with a mail account anyways and this process was more complicated in the past from my perspective.

     

    From my perspective this is a super simple way to get your trail key, buy or even replace it.

     

    Also please note that there is nothing that communicates constantly with the Forums or better speaking the so much hated "Cloud".

     

    If you want to have access to your server and manage it from the Forums so that the stats are displayed in the "My Servers" section on the Forums you have to install the My Servers plugin from the CA App, if you don't want this then don't install it. ;)

     

    Just my 2cents. :)

    • Like 2
    • Thanks 1
    Link to comment
    40 minutes ago, perrycox said:

    "Starting with this release, it will be necessary for a new user to either sign-in with existing forum credentials or sign-up, creating a new account via the UPC in order to download a Trial key.  All key purchases and upgrades are also handled exclusively via the UPC."

     

    I do also think this needs more clarification for current users who don't want to sign or associate their servers with

    UPC regarding key management. How it will be handled in the future etc...

     

     


    Have to agree it’s not 100% clear.

     

    Is the following correct?

     

    Existing users with key files upgrading to 6.10 can ignore (disable!?) any pop-ups/indicators asking to sign in to anything and the server will behave just like it does on 6.9 (i.e. it will not mess about tying to adjust hostnames or whatever).

     

    Users new to UnRAID or users who want to buy another key need to sign in once, grab a key and then sign out and then the behaviour will be like it was for 6.9?

     

    As a few others have stated I also have zero use for any of this connected stuff but if it’s just for an easier method of obtaining keys then that’s fine.

    Edited by Interstellar
    • Thanks 1
    Link to comment
    13 minutes ago, Interstellar said:

    sign out

    Why?

    Please read the comment above yours. ;)

     

    You don't have to enable backups,... :)

     

    From my perspective this is a really convenient way to register trail, buy or even replace your key.

    • Like 1
    Link to comment
    8 hours ago, limetech said:

    Security Changes

    It is now mandatory to define a root password.  We also created a division in the Users page to distinguish root from other user names.  The root UserEdit page includes a text box for pasting SSH authorized keys.

    For new configurations, the flash share default export setting is No.

    For all new user shares, the default export setting is No.

    For new configurations, SMBv1 is disabled by default.

    For new configurations, telnet, ssh, and ftp are disabled by default.

    We removed certain strings from Diagnostics such as passwords found in the 'go' file.

     

    👍 

     

    8 hours ago, limetech said:

    Starting with this release, it will be necessary for a new user to either sign-in with existing forum credentials or sign-up, creating a new account via the UPC in order to download a Trial key.  All key purchases and upgrades are also handled exclusively via the UPC.

     

    Signing-in provides these benefits:

    No more reliance on email and having to copy/paste key file URLs in order to install a license key - keys are delivered and installed automatically to your server.

    Notification of critical security-related updates.  In the event a serious security vulnerability has been discovered and patched, we will send out a notification to all email addresses associated with registered servers.

    Ability to install the My Servers plugin (see below).

    Posting privilege in a new set of My Servers forum boards.

     

    I don't understand this part. Is it still possible to use a paid license without internet access or not? And why is it needed to have an account for security-related notifications? Why don't you simply use the e-mail address which was used to buy the license (or the newsletter)?! So I'm forced to use My Servers if I want to receive security notifications?!

     

     

    And how is it possible to pull data from my server if I did not open any ports? You explained it through a reverse-proxy relay. This means a registered server has a 24/7 connection to the relay?!

     

     

    Qnap and Ubiquiti proved that it is a bad idea to use such services and having a random DDNS url with a random port is only security through obscurity. This is why I don't plan to use My Servers.

     

    • Like 1
    • Thanks 2
    Link to comment
    45 minutes ago, ich777 said:

    Why?

    Please read the comment above yours. ;)

     

    You don't have to enable backups,... :)

     

    From my perspective this is a really convenient way to register trail, buy or even replace your key.


    I can equally say “Why not?”

     

    I can’t see any benefit to staying signed in (security notifications if that serious could be emailed…)

     

    More critically, is upgrading going to mess with hostnames etc or not?

    Edited by Interstellar
    • Thanks 1
    Link to comment

    then may just log out, dont install the extra plugin, whatever ... all i see here its optional ?

     

    and about new users, when i remember i had to give a email anyway, server needed to be online anyway, etc ...

     

    weird discussion about a nice feature which is optional, my 2 cents about this.

    • Like 2
    Link to comment

    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.

     

    Link to comment
    12 hours ago, limetech said:

    The "new defaults" only have to do with new configurations, they are not changed by updating to this release with one exception.  The issue I see in diags is that your 'config/share.cfg' file is simply absent.  Not sure what could have happened to it.  Do you see that file in your flash backup?

    no - this file doesn't exist, not on my running Server and not in older Backups.. 🙂

     

    Link to comment

    @Mik3 its in the release notes ... and btw im also from europe ;) this is really a fun when i think about it that pretty sure almost all here using a smartphone, facebook, ... ;) 

     

    image.thumb.png.5e42ca98fbb4e10111d67de9c7f3a839.png

    • Like 1
    Link to comment
    8 minutes ago, peter76 said:

    no - this file doesn't exist, not on my running Server and not in older Backups.. 🙂

     

    It's a bug where the default settings are incorrect when that file is missing (and the file is allowed to be missing).  The fix is to simply enable User Shares in Settings - Global Share Settings

    • Like 1
    Link to comment
    8 hours ago, limetech said:

    Where do you think this is "heading"?  Any "cloud" services and features we offer are, and will continue to be completely "opt in" with the default being "opt out".

    I think that it's heading in the way that we will be required to log in to this new control panel to be able to use our license. Even just once, that is a concern for me. 

     

    Even in the initial post, its stated that it's "necessary", but optional. What is wrong allowing your customers to do it the current way?

     

    But in the bigger picture, there is a lack of communication about what data is sent and/or received while the accounts are connected. Is it just the key? Server status? How many files you have stored? What kind of files you have stored? Computer specs? Your network map? More? All of these things are easily doable.

     

    3 hours ago, ich777 said:

    I don't see why this is a privacy concern in any way...

    The process is super simple and I also used it a few days ago to replace my key and it is way easier to replace your key that way.

    Btw you had to register with a mail account anyways and this process was more complicated in the past from my perspective.

     

    From my perspective this is a super simple way to get your trail key, buy or even replace it.

     

    Also please note that there is nothing that communicates constantly with the Forums or better speaking the so much hated "Cloud".

     

    If you want to have access to your server and manage it from the Forums so that the stats are displayed in the "My Servers" section on the Forums you have to install the My Servers plugin from the CA App, if you don't want this then don't install it. ;)

     

    Just my 2cents. :)

    It's a privacy concern for people that don't want a constant connection to Limetech. It can allow them to collect data without you knowing. And who knows what data they would collect because none of it is explained.

     

    Also, what if Limetech gets hacked? They now have access to everyone's server. If SSH is enabled, that itself could cause absolute destruction of your server. That, in itself, is a VERY good reason why I don't want any kind of connection to my server. Also, have a read if the links in the quote below. The Qnap one happened only a month or 2 ago.

     

    Convenience is one thing, but security is another.

     

    2 hours ago, mgutt said:

    Qnap and Ubiquiti proved that it is a bad idea to use such services and having a random DDNS url with a random port is only security through obscurity. This is why I don't plan to use My Servers.

     

    • Like 1
    Link to comment
    2 minutes ago, LTM said:

    Also, have a read if the links in the quote below. The Qnap one happened only a month or 2 ago.

     

    again i dont understand, then just dont use the feature, dont open the ssl port for your server and it wont be reachable from the url from outside ;) ...

     

    image.png.a51a08420a3b98dcafabf2f99a63e02f.png

     

    and im logged in ... and once used the plugin for the flash backup (cause i personally like the idea).

     

    image.png.1ab2cb2f89a5941491604dca7743d39a.png

     

    its still only optional as described in my point of view ;)

    • Like 2
    Link to comment
    13 minutes ago, LTM said:

    It's a privacy concern for people that don't want a constant connection to Limetech. It can allow them to collect data without you knowing. And who knows what data they would collect because none of it is explained.

     

    Also, what if Limetech gets hacked? They now have access to everyone's server. If SSH is enabled, that itself could cause absolute destruction of your server. That, in itself, is a VERY good reason why I don't want any kind of connection to my server. Also, have a read if the links in the quote below. The Qnap one happened only a month or 2 ago.

    I think you don't read my comment entirely/correctly, if you don't install the My Servers plugin no constant connection to Limetech is opened.

    Without the My Servers plugin nothing is collected, it is only used for the Key management.

     

    Don't enable SSH access or remote access or better speaking don't install the My Servers plugin in the first place on your server and nobody won't be able to connect even if they got hacked, I don't understand the concern here...

     

    @alturismo posted a screenshot a few posts above. :)

    It also states that you can logout and never need to log in back again.

    Link to comment
    22 minutes ago, ich777 said:

    Without the My Servers plugin nothing is collected, it is only used for the Key management.

     

    I think the main problem is that the release notes only describe what happens if a user likes to try out Unraid and buys the license afterwards. For me as a license owner it's still unclear what I need to do. Do I need to login if I update to Unraid 6.10 and if yes, why? Does it change something to the license key file?!

     

     

    Link to comment
    16 minutes ago, mgutt said:

    Do I need to login if I update to Unraid 6.10 and if yes, why?

    No, but I would recommend it because your Keyfile is then bound to your Forum account, of course you can log out after that if you have any concerns about privacy and if you ever have to replace it you simply log in again and click on replace and everything is done automatically, of course you then also can log out again after you've replaced the key.

     

    16 minutes ago, mgutt said:

    Does it change something to the license key file?!

    No.

    Link to comment
    37 minutes ago, ich777 said:

    don't install the My Servers plugin

     

    In fact I did sign out and remove the My Servers plugin RC from my 6.9.2 systems this morning, because all my Unraid servers did not work out of sudden. Connecting the unraid.net URL of these servers ended in DNS ERR_NAME_NOT_RESOLVED. I'm back to local IP connections now and I will keep it that way. My 6 license keys are stored in /config on all sticks and I hope it will work that way in 6.10 and beyond.

     

    1 hour ago, alturismo said:

    when i think about it that pretty sure almost all here using a smartphone, facebook, ...

     

    It's a descision that users make. If they want Facebook but not Google (or whatever) - it's their personal descision then. IMHO it's no valid argument to say "If you 'trust' Facebook you must 'trust' Google as well" .

     

    • Thanks 1
    Link to comment



    Guest
    This is now closed for further comments

  • Status Definitions

     

    Open = Under consideration.

     

    Solved = The issue has been resolved.

     

    Solved version = The issue has been resolved in the indicated release version.

     

    Closed = Feedback or opinion better posted on our forum for discussion. Also for reports we cannot reproduce or need more information. In this case just add a comment and we will review it again.

     

    Retest = Please retest in latest release.


    Priority Definitions

     

    Minor = Something not working correctly.

     

    Urgent = Server crash, data loss, or other showstopper.

     

    Annoyance = Doesn't affect functionality but should be fixed.

     

    Other = Announcement or other non-issue.