SOLVED Web interface not accessible after migration

[INCSlayer]

I just migrated to truenas scale via the update train switch and I am now getting the error that:
The web interface could not be access and that I need to check network configuration..
however the interface is up and I can from the console ping out.
also since this was a migration I can SSH to the machine so I know the network is in itself functional on the machine.

The guide mentions that "When TrueNAS SCALE boots, you might need to use the Shell to configure networking interfaces to enable GUI accessibility."
but the link is only to the graphical interface so its not very helpful to resolve this.
Am i just missing some very simple step?
I have tried resetting the network interface and network settings. (including setting it as DHCP just to verify if it gets and IP that way which it does and the CLI based networking systems still work.

 

[Samuel Tai]

What does the console menu show?

 

[INCSlayer]

this is how it looks:

 

[Samuel Tai]

Hmm. From SSH, can you run midclt call system.general.config | jq, and report the output? I'm especially interested in the ui_address field. Likewise midclt call network.general.summary | jq.

 

[INCSlayer]

Code:

root@Gammelman[~]# midclt call system.general.config | jq
{
  "id": 1,
  "language": "en",
  "kbdmap": "swedish.iso",
  "birthday": {
    "$date": 1603520705376
  },
  "timezone": "Europe/Stockholm",
  "wizardshown": true,
  "crash_reporting": true,
  "usage_collection": true,
  "ui_address": [
    "0.0.0.0"
  ],
  "ui_v6address": [
    "::"
  ],
  "ui_port": 80,
  "ui_httpsport": 443,
  "ui_httpsredirect": false,
  "ui_x_frame_options": "SAMEORIGIN",
  "ui_httpsprotocols": [
    "TLSv1.2",
    "TLSv1.3"
  ],
  "ui_consolemsg": true,

i truncated it a bit since i it does also have a bunch of certificates i dont want to show

Code:

root@Gammelman[~]# midclt call network.general.summary | jq
{
  "ips": {
    "eno1": {
      "IPV4": [
        "192.168.0.4/24"
      ],
      "IPV6": [
        "fe80::ec4:7aff:fe7c:56dc/64"
      ]
    }
  },
  "default_routes": [
    "192.168.0.1"
  ],
  "nameservers": [
    "1.1.1.1",
    "8.8.8.8",
    "192.168.0.1"
  ]
}

 

[Samuel Tai]

Try midclt call system.general.update '{ "ui_address": [ "192.168.0.4" ] }' and then service middleware restart and service nginx restart.

 

[INCSlayer]

midclt call system.general.update '{ "ui_address": [ "192.168.0.4" ] }'
did not help
However
service nginx restart
led me to see that nginx was complaining about my certificate.
i have fixed that and restarted nginx and now the webserver has kicked in and it is working.