March 31, 20197 yr Hey, I'm building a new server with the goal of moving drives across when I know it's working. I'm using a trial version on a USB key for now, and the new system has no hard drives/disks. The server boots OK and I can ssh in, but I can't access the Web UI. Does it need a drive in the system for the Web UI to load, or is it a problem elsewhere in the setup? Thanks
March 31, 20197 yr Community Expert Just now, atl-far-east said: Does it need a drive in the system for the Web UI to load No, you just need the boot flashdrive.
March 31, 20197 yr Author Hmm, ok. I'll get there diagnostic logs later today and upload them. Thanks for the quick reply!
March 31, 20197 yr Author Diagnostics here - any idea why Web UI won't start/be accessible? Thanks in advance! flower-diagnostics-20190331-0249.zip
March 31, 20197 yr You've probably got a bad cable, as the NIC is only connecting at 100MB/s Can you hit the UI if you go to it's IP address of 192.168.1.249?
March 31, 20197 yr Author I think I'm temporarily using a 100Mbps cable, but will try find an actual good cable. Can't access UI via that IP but can SSH in fine, so wasn't thinking it was cable. Will give it a go later. Thanks!
March 31, 20197 yr Author Changed cable, same issue. Can SSH in/etc., and ping out from it, but no Web UI. Any ideas? flower-diagnostics-20190331-0337.zip
March 31, 20197 yr Author If it helps, I don't see anything listening on any web ports: root@flower:~# netstat -vatn Active Internet connections (servers and established) Proto Recv-Q Send-Q Local Address Foreign Address State tcp 0 0 0.0.0.0:139 0.0.0.0:* LISTEN tcp 0 0 0.0.0.0:111 0.0.0.0:* LISTEN tcp 0 0 0.0.0.0:21 0.0.0.0:* LISTEN tcp 0 0 0.0.0.0:22 0.0.0.0:* LISTEN tcp 0 0 0.0.0.0:445 0.0.0.0:* LISTEN tcp 0 0 0.0.0.0:44833 0.0.0.0:* LISTEN tcp6 0 0 :::139 :::* LISTEN tcp6 0 0 :::111 :::* LISTEN tcp6 0 0 :::22 :::* LISTEN tcp6 0 0 :::445 :::* LISTEN tcp6 0 0 :::46627 :::* LISTEN tcp6 0 0 fe80::1417:8aff:fe4f:22 fe80::102c:cf39:2:50580 ESTABLISHED ...which makes me think that it's emhttp/nginx not listening, rather than the connection?
March 31, 20197 yr Author Not sure if this is relevant: Mar 31 04:03:04 flower root: Starting Nginx server daemon... Mar 31 04:03:04 flower root: nginx: [emerg] PEM_read_bio_DHparams("/etc/nginx/dhparam.pem") failed (SSL: error:0909006C:PEM routines:get_name:no start line:Expecting: DH PARAMETERS) Mar 31 04:03:04 flower emhttpd: shcmd (22): exit status: 1 Mar 31 04:03:04 flower emhttpd: too many devices Also, given that there are 0 drives and just a USB drive, that last line is confusing?
Archived
This topic is now archived and is closed to further replies.