This is an interesting one that I would thought I would share in case anyone else runs into it ever. I have a TrueNAS MINI-3.0-X+ appliance running EletricEel that I have added to a IX Systems hosted cloud instance of TrueCommand. The appliance went down due to an extended power outage for the first time since it was joined to TrueCommand. The appliance came back up with no issue except for the web gui. I looked through the middlewared log and saw that nginx was having an issue starting with the following error:
middlewared.plugins.service_.services.base.systemd_unit():171 - nginx reload failed with code 1: ‘nginx.service is not active, cannot reload.\n’
So I just rebooted the TrueNAS but the same issue persisted and I could not access the web gui. So I ran systemctl status nginx and saw that nginx could not start due to the following:
Can not bind to “IPofTrueCommandInterface”:443 failed (99: Cannot assign requested address)
“IPofTrueCommandInterface” of course = the IP the TrueNAS appliance is assigned when joining it to the TrueCommand wireguard VPN.
I than went into the nginx config file in etc/nginx and commented out the line listing: listen “IPofTrueCommandInterface”:443
Then I tried to start nginx with “systemctl restart nginx” and nginx started without issue and I was again able to access the web gui.
I have since removed the comment # from that line and restarted nginx again and it again stated without issue.
So in the end I’m not really sure why this happened but I none the less fixed it. Maybe I could have just issued the “systemctl restart nginx” after I rebooted and it would have worked too. Maybe during the boot process the TrueCommand interface didnt come up fast enough and nginx tried to start before that interface was up?