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.

[Mascot]

12 minutes ago, Todd Miller said:

Is it possible something is happening at the developers end that only the web UI seems affected for me?

As far as I am aware, that's pretty much what it is. The HexOS UI does not run on your server, it runs on theirs (Eshtek). HexOS is apparently bad at keeping this connection alive/reconnecting when it goes down. So the TrueNAS interface will work fine, since you access it locally, as will every other service you're running on your server. You just lose access to the one thing you paid for, the HexOS interface. 😛

[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 June 18 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 June 18 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

[Insanittyx]

I had the same issue and just choose to reinstall the system in its entirety, however hexos now thinks i am going to add a second server:



@Mobius How can i resolve this?

[Mobius]

18 minutes ago, Insanittyx said:

I had the same issue and just choose to reinstall the system in its entirety, however hexos now thinks i am going to add a second server:



@Mobius How can i resolve this?

when you login to deck before you try to claim your server you see this screen

just hit unclaim server

[Insanittyx]

No, I see this:

[Mobius]

1 minute ago, Insanittyx said:

No, I see this:

turn off your new server and check again

[Insanittyx]

2 minutes ago, Mobius said:

turn off your new server and check again

Same result, except for 'A new server is detected'

[Mobius]

4 minutes ago, Insanittyx said:

Same result, except for 'A new server is detected'

other users have reported deck being a little weird right now because of caching
can you try checking it out with a different browser?

[Insanittyx]

Yes ofcourse! Unfortunatly still the same result.
Different browser (edge instead of chrome) and icognito:

Edited June 27 by Insanittyx

[Mobius]

are there any options when you click the arrow next to the home button up top?

[Insanittyx]

When I click 'Add Server I get the 'Lets get started!' screen.

[Mobius]

8 minutes ago, Insanittyx said:

When I click 'Add Server I get the 'Lets get started!' screen.

im assuming refresh button does nothing either right?

[Insanittyx]

1 minute ago, Mobius said:

im assuming refresh button does nothing either right?

Except for refreshing the page yes.
The 'resetting' state comes from the server:

[Mobius]

i'll reach out to someone and see if they know anything else we can try

[Mobius]

@Insanittyx lets try something else. If you had a vpn active try again after turning it off.
if you didn't have a vpn active try connecting to hexos deck using a device on a different network like your phone (on cellular internet and not wifi)

[Mobius]

@Insanittyx you should be good to go now without any more troubleshooting
just log back into deck and you can claim your new server

[Jmax]

I was troubleshooting and selected disconnect server, with the intent to reconnect. I just get this no license for new server every time. Its the same server, with the same name, same ip, no vpn use here, and nothing was changed other choosing disconnect. how do I fix this?

 

[CrumpetCrusader]

i had same issue

 I was playing around with my Router (GL-Net-Slate). I enabled AdGuard Home and told it to handle client requests. ie be my DNS (I think)

So I think it was looking up Hexos' request and not finding an IP/ blocking its traffic.

I stopped handling client requests, and it works again now.

(not sure if it was related, but I also shifted my NGINX HTTP/HTTPS ports from 80/443 to 30021/30022 and changed the router's port forwarding)

[Isaac.K]

I've been having this same issue off and on for months now but now it seems like a pretty constant thing. I havnt been able to log in for quite some time now so any help would be greatly appreciated.

[Stressed_Out09]

I'm having the same issue.

Though its only been an issue since I've updated my network to a unifi system and setup vlans/new IP aka going from 192.168.50.1 to 10.10.1.1 (and adding vlans from that)

Could this be causing the issue? And if so how do I resolve it? - For context I can see successfull flows out but not really seeing any connections to something obviously HexOS related