Deck will not connect to hexOS

[thault]

The deck shows my hexOS server as unavailable and won't connect. I can see the server is online, shares are up and running, and I can log into the trueNAS web ui directly. 

I did have tailscale on at first, but I have turned that off and tried everything short of restarting hexOS.

[Todd Miller]

Hmm.  It sounds Mascot like you have the measure of this issue.  I wonder if this will be solved or at least lessened with the local UI?

Edited 4 hours ago by Todd Miller

[Mobius]

I don't think this issue has to do with deck up time since https://status.hexos.com/ shows 100% up time for deck and api.

I have reached out to the hexos team again to follow up with them on this issue.

[Todd Miller]

35 minutes ago, Mobius said:

I don't think this issue has to do with deck up time since https://status.hexos.com/ shows 100% up time for deck and api.

I have reached out to the hexos team again to follow up with them on this issue.

I only disagree with that statement because the web UI is all that loses connection.  All other connections stay active.  Has the team given you different specific direction?  And to be more specific, I can access the HexOS URL.  I just get an unavailable error through that URL.

Edited 3 hours ago by Todd Miller
incomplete thought

[Mascot]

23 minutes ago, Mobius said:

I don't think this issue has to do with deck up time since https://status.hexos.com/ shows 100% up time for deck and api.

It's not the uptime of the website UI I'm thinking of, that's clearly fine considering it's there to tell us the server is unreachable. The issue is the uptime of the connection between our HexOS installations and whatever the backend is. It doesn't mean the backend is down, but for whatever reason that connection dies and is not re-established even though there's no connectivity issue as far as the HexOS installation is concerned.

37 minutes ago, Todd Miller said:

Hmm.  It sounds Mascot like you have the measure of this issue.  I wonder if this will be solved or at least lessened with the local UI?

I would hope it would be solved, but it's hard to tell. Based on some comments I've seen it looks like architecturally what we might end up with isn't a local interface in the traditional sense, but a container running what is currently running on deck.hexos. If that is the case there'd still be a connection happening, even if between services on the local machine, and we've only removed the internet from the mix. So if the issue isn't "unable to reconnect after internet blip", but rather that something at either end is buggy and crashing or dropping the connection regardless of network connectivity, it could persist. We'll just have to wait and see. Considering the TrueNAS interface remains available, this isn't much an issue for me, but I do find it a bit puzzling that the root cause appears to still be unknown after all this time.

[Mobius]

28 minutes ago, Todd Miller said:

Has the team given you different specific direction?

I wasn't updated on the outcome of this issue after i previously escalated it. 
I do however know that a member of the team setup a meeting with a few of the individuals with this issue.

[Mobius]

Seems like the hexos team has been looking into this issue and there should be a post on it very soon.

For now can you try to update the underlying truenas os to 24.10.22 and then try the following
 

• Login via TrueNAS UI and navigate to the Network page.
• Observe the value for the interface IP address as well as the Global Configuration Nameserver and Gateway.
  • The interface should show the IP address that DHCP assigned.
  • Nameserver should show an IP address with “(DHCP)” next to it; most likely matching the gateway.
• Click “Settings” on Global Configuration and observe the values specified for DNS 1.
  • Even though the value was dynamically assigned, it appears as a fixed value within the Global Configuration Settings pane.
  • Editing the pane and clicking “Save” will change the DNS 1 entry from “DHCP” to static.
  • Editing the pane and deleting the DNS 1 entry and clicking save will return the DNS 1 entry to “DHCP”, but only if the interface IP is also set to DHCP.  If the Interface IP’s DHCP checkbox is unchecked and you edit global configuration deleting the DNS 1 entry and clicking save, it will leave DNS 1 blank and no name server will be specified.
• Click “Edit” on the Interface and observe that no values are specified for the DHCP IP address in the form.
  • Uncheck “DHCP” checkbox.
  • Click “Add” under the “Aliases” section to add a manually specified IP address.
  • Click “Save”
  • Observe the Nameserver still showing “(DHCP)”.
  • Click “Test Changes”.
  • Renavigate your browser to the new manually specified IP to load the TrueNAS UI.
  • Go to the Network page.
  • Observe the Global Configuration section showing no value under Nameservers.
  • Click “Settings” on Global Configuration and observe no value under DNS 1.

 

If it doesnt work please let me know