June 13, 20179 yr 7 minutes ago, Output said: I upgraded but unraid would not boot correctly, I could not putty but use ipmi to console, see attached diag logs. tower-diagnostics-20170613-1611.zip Jun 13 15:11:16 Tower dhcpcd[1711]: br0: using IPv4LL address 169.254.135.108 You're not getting an IP address, check network config, you can boot with the GUI option and use that to configure your network.
June 13, 20179 yr On 6/6/2017 at 3:01 AM, Benson said: How do you get the read/write speeds to display like that? I don't see that anywhere in disk or display settings. EDIT: Nvmd, I found the toggle switch. Edited June 13, 20179 yr by IamSpartacus
June 13, 20179 yr 2 hours ago, johnnie.black said: Jun 13 15:11:16 Tower dhcpcd[1711]: br0: using IPv4LL address 169.254.135.108 You're not getting an IP address, check network config, you can boot with the GUI option and use that to configure your network. Could it be because of LACP setting that I have? I have 2 nics in LACP mode and that works fine in 6.3.5 but not in 6.4rc2 then?
June 14, 20179 yr Author On 6/13/2017 at 10:31 AM, Dephcon said: WebUI seems much more fluid now! Just a warning to anyone using letsencrypt/nginx/etc dockers. The unRAID webui now wont start if you're using port local 443, switch your container to use an alternate local port before upgrading to save yourself a headache. This is fixed in -rc3.
June 14, 20179 yr This is fixed in -rc3.Can you elaborate on this fix? Does it make sure the unraid webgui is fired up before docker service is started? If so, we'll have to notify the docker users who mapped port 443Thanks
June 15, 20179 yr 3 hours ago, aptalca said: Can you elaborate on this fix? Does it make sure the unraid webgui is fired up before docker service is started? If so, we'll have to notify the docker users who mapped port 443 Lots of great discussion in the thread below. The gist: - unraid webgui will no longer load https by default, you'll need to enable it if you want it (so no unexpected conflicts on first boot) - in 6.4 you can easily move your https dockers to another IP address (so it is easy to avoid port conflicts) - unraid webgui will load before docker/vm (so a docker will never prevent it from loading)
June 15, 20179 yr Lots of great discussion in the thread below. The gist: - unraid webgui will no longer load https by default, you'll need to enable it if you want it (so no unexpected conflicts on first boot) - in 6.4 you can easily move your https dockers to another IP address (so it is easy to avoid port conflicts) - unraid webgui will load before docker/vm (so a docker will never prevent it from loading) Excellent, thanks [emoji1]
Archived
This topic is now archived and is closed to further replies.