404 Error on new 6.6.1-1 Hub if DHCP is Disabled

Possible resolution:

This resolution is for NEW DEPLOYMENTS ONLY and will result in the loss of any existing data on the hub!!  It should be implemented before an external database is joined to the hub.

Console or SSH into the hub as ssconsole, select option 'N' and confirm all relevant network settings are saved -  especially DNS Resolvable Hostname (IP or DNS is acceptable) and Management IP Address.

SSH into the hub as friend/ec2-user/azureuser using Putty or Windows 10 OpenSSH and run the following commands to re-initialize the local database.  Copy one line at a time and hit shift+right-click OR shift+insert key to paste your clipboard into the SSH session. 

Run root shell:

sudo bash

Stop application services:

systemctl stop lwl-backend lwl-backend-priv lwl-smx lwl-inventoryd lwl-applianced lwl-cidd

Drop database elements. Errors for roles/databases not existing can be safely ignored:

echo 'drop database portal; drop database mentok_run; drop role reports; drop role impadminsu; drop role impadmin; drop role vcops;' | su - postgres -c 'psql template1'

Re-initialize database:

/opt/tnt/db/preset.sh

Remove activation certificate:

rm -f /opt/tnt/var/backend/.activated /opt/tnt/var/backend/activation.crt

Start application services:

systemctl start lwl-backend lwl-backend-priv lwl-smx lwl-inventoryd lwl-applianced lwl-cidd

If an external database appliance is to be used, SSH or console into it as ssconsole and copy the data from the hub using the D, C option in the menu.  Then join the DB to the hub using D, J option.  The hub should reboot after the process is complete.

Wait 5 minutes after the hub services start and check your Web UI again by visiting the hub IP address or hostname in your browser.