unRAID OS version 6.5.2-rc2 available


Recommended Posts

Installation and Bug Reporting Instructions

 

This is another security and bug fix release, with yet more cool improvements by @bonienl among which are:

  • Add 'Advanced/Basic View' for  'Main/Boot Device/Flash/Syslinux configuration'.  Very nice.
  • Make the 'SMB extra' text box auto-resize.

 

In addition, github user 'shayne' added support for "Docker Labels".  In his words:

Quote

Docker object labels:
https://docs.docker.com/config/labels-custom-metadata/

More and more containers are taking advantage of container metadata
where environment variables are not necessary.

Traefik is a good example:
https://docs.traefik.io/configuration/backends/docker/#on-containers

 

We are anticipating releasing this to stable in a couple of days.

Version 6.5.2-rc2 2018-05-09

Base distro:

  • Replace lxterminal with sakura version 3.5.0
  • mozilla-firefox: version 60.0 (CVE-2018-5150, CVE-2018-5151, CVE-2018-5152, CVE-2018-5153, CVE-2018-5154, CVE-2018-5155, CVE-2018-5157, CVE-2018-5158, CVE-2018-5159, CVE-2018-5160, CVE-2018-5163, CVE-2018-5164, CVE-2018-5165, CVE-2018-5166, CVE-2018-5167, CVE-2018-5168, CVE-2018-5169, CVE-2018-5172, CVE-2018-5173, CVE-2018-5174, CVE-2018-5175, CVE-2018-5176, CVE-2018-5177, CVE-2018-5180, CVE-2018-5181, CVE-2018-5182)
  • php: version 7.2.5 (CVE-2018-10545, CVE-2018-10546, CVE-2018-10547, CVE-2018-10548, CVE-2018-10549)

Linux kernel:

  • version 4.14.40

Management:

  • webgui: Add class C (/8) network mask
  • webgui: Smart syslinux configuration
  • webgui: Syslinux config: basic and advanced mode
  • webgui: Make SMB extra auto sizeable
  • webgui: Add support for Docker Labels to Docker plugin
  • Like 1
Link to comment
52 minutes ago, bonienl said:

Nobody using unRAID 6.5.2-rc2 ?

 

I can't speak for everybody else... But it's running great here :P

 

One thing I have noticed (whilst I think about it) is I cannot stop Docker running...

 

http://ip_address/Settings/DockerSettings . Selecting Enabled Docker: "No" and hitting apply flashes the browser viewport and flicks "No" back to "Yes"...!

 

Would you like a Diag bundle?

 

This is what happens in my syslog upon pressing Apply in the Docker settings:

 

May 11 22:19:22 Raptor ool www[11976]: /usr/local/emhttp/plugins/dynamix/scripts/emhttpd_update
May 11 22:19:22 Raptor emhttpd: req (7): cmdStatus=apply&csrf_token=****************
May 11 22:19:22 Raptor emhttpd: Starting services...

 

Link to comment
4 minutes ago, nexusmaniac said:

 

I can't speak for everybody else... But it's running great here :P

 

One thing I have noticed (whilst I think about it) is I cannot stop Docker running...

 

http://ip_address/Settings/DockerSettings . Selecting Enabled Docker: "No" and hitting apply flashes the browser viewport and flicks "No" back to "Yes"...!

 

Would you like a Diag bundle?

 

This is what happens in my syslog upon pressing Apply in the Docker settings:

 


May 11 22:19:22 Raptor ool www[11976]: /usr/local/emhttp/plugins/dynamix/scripts/emhttpd_update
May 11 22:19:22 Raptor emhttpd: req (7): cmdStatus=apply&csrf_token=****************
May 11 22:19:22 Raptor emhttpd: Starting services...

 

 

Wrong csrf token usually happens when the browser uses outdated info. What happens when you close and reopen the browser application?

 

Link to comment
1 minute ago, bonienl said:

 

Wrong csrf token usually happens when the browser uses outdated info. What happens when you close and reopen the browser application?

 

 

I thought the same thing but even when reopening Chrome the same behaviour exists...

 

Just opened an incognito tab to be 100% sure :P

Edited by nexusmaniac
Link to comment

Sometimes it helps to completely clear the cache of the browser.

 

Testing it, there is indeed a problem, not only Chrome, but other browsers too.

 

I have opened a bug report, it is not csrf_token related, but seems something with emhttpd.

 

This is a regression error I introduced (docker config file name was not preserved) ?. Made a correction.

Edited by bonienl
  • Like 2
Link to comment

Can happen to the best! I appreciated what you are doing with unRAID webgui. I started using unRAID OS I think in 2010 but moved away for a couple of years. I checked every year what progress was made with unRAID OS. Since Docker has arrived unRAID is becoming really interesting. I must say every release it becomes better. Also so a big thumbs up for the Limetech devs and not to forget the unRAID community and community devs. 

 

 

Edited by MvL
Link to comment

Seeing issues in latest firefox when trying to launch the in browser terminal, as well as using novnc through the webui to connect to a debian VM.

 

Terminal just hangs trying to load, and novnc timesout trying to connect.

 

Edge Browser and Chrome both work fine.

Edited by cybrnook
Link to comment
1 hour ago, cybrnook said:

I am on v60. I also tried clearing cache with Ctrl+f5, then came back and just cleared the entire browser history since the beginning of time.

 

 

Make sure that you have whitelisted your server especially with regard to popup and adblockers.  

Link to comment
58 minutes ago, Frank1940 said:

 

Make sure that you have whitelisted your server especially with regard to popup and adblockers.  

Good call, I will check to see if firefox is using it's tracking blocking thing that comes on by default. But like I was saying, it's only firefox. Chrome and Edge work fine, and I see a ton of CVE's were apparently patched for firefox in this release.

 

I will note that I recently disabled https, so my unraid server is being presented again over standard http.

Edited by cybrnook
Link to comment
On 5/11/2018 at 2:20 PM, nexusmaniac said:
On 5/11/2018 at 1:24 PM, bonienl said:

Nobody using unRAID 6.5.2-rc2 ?

 

I can't speak for everybody else... But it's running great here :P

Working nominal here (three days use), I don't use the built-in encryption, so can't report on any of that.  Still need to look at Docker labels.

Quote

May 12 17:05:29 HYDRA avahi-daemon[6837]: Joining mDNS multicast group on interface veth68486cc.IPv6 with address fe80::d8ae:91ff:fe74:9e94.
May 12 17:05:29 HYDRA avahi-daemon[6837]: New relevant interface veth68486cc.IPv6 for mDNS.
May 12 17:05:29 HYDRA avahi-daemon[6837]: Registering new address record for fe80::d8ae:91ff:fe74:9e94 on veth68486cc.*.
May 12 23:47:16 HYDRA kernel: node[9600]: segfault at 122db33cce40 ip 0000122db33cce40 sp 00007fff1f2e2468 error 14
May 13 00:00:01 HYDRA Plugin Auto Update: Checking for available plugin updates

I did just notice this in my logs, but I also just turned on overclocking for the first time.  Attached are my diagnostics, and I'm going to reboot and turn off over clocking (it was an experiment).  Odd bit my system still stable even with that fault; then again I don't use IPv6 on my network.

 

hydra-diagnostics-20180514-0841.zip

Link to comment
1 hour ago, bonienl said:

The kernel has IPv6 enabled, this results in each interface getting an IPv6 link local address (fe80:*) assigned to it, normal behavior.

Yeah I'd buy that. So that seg fault is regarding IPv6 and therefore not an issue, or just extra lines and doesn't pertain to the seg fault?    Never mind, clearly two different events by the time-stamp. 

 

Edited by Jcloud
Link to comment
On 5/12/2018 at 7:00 AM, bonienl said:

Sometimes it helps to completely clear the cache of the browser.

 

Testing it, there is indeed a problem, not only Chrome, but other browsers too.

 

I have opened a bug report, it is not csrf_token related, but seems something with emhttpd.

 

This is a regression error I introduced (docker config file name was not preserved) ?. Made a correction.

 

Any temp fix for this until new RC is out?

I'm sure this is related, but not mentioned here...

I'm unable to edit the custom network inside the docker settings either.

Trying to do your network isolation (from other thread)

Link to comment
Guest
This topic is now closed to further replies.