http & https ports not listening

[quarkeddev]

Hello, 

 

Having an issue where my web gui is no longer accessible on http port 80 or https on 443. I am still able to access the server via SSH. Have edited the /config/ident.cfg file and made sure had following settings configured: 

USE_SSL="auto"
PORT="80"
PORTSSL="443"
 

Rebooted and same issue. 

 

Then took a look at what ports are currently listening on the server and sure enough looks like http and https are not listening: 

~# lsof -i -P -n | grep LISTEN
rpcbind   1664  rpc    7u  IPv4    245      0t0  TCP *:111 (LISTEN)
rpcbind   1664  rpc    9u  IPv6    247      0t0  TCP *:111 (LISTEN)
rpc.statd 1669  rpc    8u  IPv4  10834      0t0  TCP *:41387 (LISTEN)
rpc.statd 1669  rpc   11u  IPv6  10838      0t0  TCP *:55851 (LISTEN)
smbd      1734 root   29u  IPv6   1436      0t0  TCP *:445 (LISTEN)
smbd      1734 root   30u  IPv6   1437      0t0  TCP *:139 (LISTEN)
smbd      1734 root   31u  IPv4   1438      0t0  TCP *:445 (LISTEN)
smbd      1734 root   32u  IPv4   1439      0t0  TCP *:139 (LISTEN)
sshd      1803 root    3u  IPv4  13523      0t0  TCP *:22 (LISTEN)
sshd      1803 root    4u  IPv6  13525      0t0  TCP *:22 (LISTEN)
inetd     1810 root    5u  IPv4  12817      0t0  TCP *:21 (LISTEN)
 

Has anyone run into this issue or know how to help. Any assistance would be appreciated. 

 

Thanks

[quarkeddev]

Have regained access to the webgui, but only after installing unraid on my flash disk. I should make note this is a trial period for me, so not to concerned about my key just yet. 

 

Looking to now just get my data back and accessible through unraid. I have a copy of all of the old config files from my flash disk before unraid was installed again.  I have not started the array with the new install yet, as I don't want to loose the data on my hard drives from the previous array.  Is there any way I can restore my array back to how it was before the loose of web access occurred and still have all my data intact?

 

 

For what ever it is worth I have attached a copy of my diagnostic files during the presence of the issue where I cannot gain access to the webGUI. 

tower-diagnostics-20191105-2011.zip

[JonathanM]

Do you know for certain which drives where assigned to which slots? If so, just assign them as they were, you can either let parity rebuild or select the option that parity is already valid and do a check.

 

If you aren't sure which drive was assigned where, assign them all as data drives, and start the array. As long as you don't assign anything to the parity slot(s), nothing will be overwritten.

[quarkeddev]

I do know what order the drives were in. In fact while getting the diag file to post here, I was messing around with the config and basically restored my old flash disk config without the license key file (trail.key). Booted it up and sure enough I regained access to webGUI. For what ever reason the trail.key file appears to be my issue, and is causing my webGUI access to die. 

 

Gonna contact support at this time and see if they can help me out with the key