I installed latest version of unRAID for testing over last couple of days on a trial license, managed to get everything working fine using the various FAQ's/guides online, arrays built, permissions for shares, was really impressed all straight forwards. 

 

Then, earlier today I shutdown the system, but then when I restarted just now the web gui would not come up.  I tried lots of things, but closest I got to getting it working again was by manually going in via ssh and starting "/usr/local/sbin/emhttp" but web gui still would not come up, if I manually start "/etc/rc.d/rc.nginx start" and "/etc/rc.d/rc.php-fpm start" I got the gui, but with loads of php errors.  Then magically the web gui comes up but with "Registration: Unraid OS Trial - no connection" and wont start array "too many devices".

 

I did notice that there was a curl command on the process list that did not respond (netstat shows SYN_SENT forever to a server keys.lime-technol.....), Is it trying to get a license or some sort of access/activation code, hanging and not giving a warning and/or timing out?

 

Does this normally happen on trials?  When I buy a full code will it still happen?

Edited July 31, 20196 yr by jond2000
typo/ solved

Trial must have access for license but not required for paid license. 

 

I suspect problem with Flash or its port

 

Go to Tools-diagnostics and attach the complete Diagnostics zip file to your next post. 

Can you try running the command ‘df’ from a command line and check that you have /boot mapped (normally to /dev/sda).

Thanks for responses.

I conclude it was down to something network related, internet was up but some sites not accessible, like the key server. I switched routes to my other connection and it came up normally and again after a reboot, its all been working fine since.

I had a look through the diagnostic logs, these don't really show anything as its from a clean boot after the issue.

I think what was happening is that it was sending the request to the key server, not connecting/getting a response and this prevented the trial mechanism from working correctly as it needed authorisation from the server. This hung the start of emhttp, thus did not bring up the gui, when it did eventually time out the gui came up with the no key cannot connect to network during trial error.