Jump to content
HexOS 1.0 ×
Guide for users having trouble updating Immich ×
  • 5

Deck will not connect to hexOS

thault

Asked by thault,

 Share

Question

thault Newbie

thault

Posted
Posted

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.

  • Like 5
  • Answers 63
  • Created
  • Last Reply

Top Posters For This Question

Popular Days

Top Posters For This Question

Popular Days

Popular Posts

Mobius
Mobius

Hello,   It seems the after the update some systems on reboot are reaching out to our server so it doesn't know your there. Try the following.   Login to TrueNAS interface. Le

thault
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 o

Mobius
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 followi

Posted Images

63 answers to this question

Recommended Posts

  • 6
Mobius Veteran

Mobius

Posted
Posted
17 hours ago, celliott113 said:

Having the same issue where this is a fresh install of HexOS, however https://deck.hexos.com/add-new-server/detecting cannot detect the server.

  • I can ping the server
  • I'm on the same network as the server
  • The server has internet access
  • The server has been rebooted like 20 times
  • mDNS is enabled on HexOS and the UniFi network
  • Tried both Brave and Chrome browser standard and incognito

Since it was a fresh install, I figured maybe the version was bad so I changed from v25.04 to v25.10 but to no avail...Idk what else to try other than just managing it from the TrueNAS console directly since I can access the web GUI directly just fine.

Screenshot 2026-01-12 214205.png

Screenshot 2026-01-12 214532.png

Hello,

 

It seems the after the update some systems on reboot are reaching out to our server so it doesn't know your there. Try the following.

 

Login to TrueNAS interface.

Left side select "system".

Then after screen refreshes select "shell" from the list.

Paste in the following command. Can't use normal short cuts Will need to use Shift + Insert Key for pasting.

sudo python /usr/lib/python3/dist-packages/middlewared/scripts/vendor_service.py

 

If that works within about 1 min you should be able to go to deck.hexos.com and see your server or claim it.

  • Like 1
  • Thanks 6
  • 1
avazquezm Newbie

avazquezm

Posted
Posted

Hi! Having this same issue since just today, as far as I can tell. Been using HexOS pretty much since a few days after it launched.

Just like others, I can interact with the NAS just fine in any other way, like accessing the TrueNAS Scale interface directly, or accessing an SMB Share, it's just deck.hexos.com seemingly not connecting to it.

Please advise on how to fix it, if a solution has been identified by now. Thanks in advance.

ss.png

  • 1
Turbocat777 Rookie

Turbocat777

Posted
Posted (edited)
On 1/13/2026 at 4:14 PM, Mobius said:

Hello,

 

It seems the after the update some systems on reboot are reaching out to our server so it doesn't know your there. Try the following.

 

Login to TrueNAS interface.

Left side select "system".

Then after screen refreshes select "shell" from the list.

Paste in the following command. Can't use normal short cuts Will need to use Shift + Insert Key for pasting.

sudo python /usr/lib/python3/dist-packages/middlewared/scripts/vendor_service.py

 

If that works within about 1 min you should be able to go to deck.hexos.com and see your server or claim it.

 

Hello, I just did the update and had the same issue, This did fix it for me and i'm able to get back in and everything is working "fine".

The only issues I have now is one pc couldn't access my SMB shares anymore and I had to remap using the IP address 
-this is kinda solved the problem.
 

But now i'm getting HexOS email notifications ~every 15min for the same error.

"Failed to check for alert SyslogNg: [Errno 24] Too many open files"

(logging into TrueNAS doesn't show any errors)

Edited by Turbocat777
  • 1
Raptor2213 Newbie

Raptor2213

Posted
Posted (edited)
On 1/13/2026 at 3:14 PM, Mobius said:

Hello,

 

It seems the after the update some systems on reboot are reaching out to our server so it doesn't know your there. Try the following.

 

Login to TrueNAS interface.

Left side select "system".

Then after screen refreshes select "shell" from the list.

Paste in the following command. Can't use normal short cuts Will need to use Shift + Insert Key for pasting.

sudo python /usr/lib/python3/dist-packages/middlewared/scripts/vendor_service.py

 

If that works within about 1 min you should be able to go to deck.hexos.com and see your server or claim it.

Having the same issue.  Entering the above command just returns: 
Failed to start transient service unit: Unit websocat.service was already loaded or has a fragment file.

Fresh install.  I'm looking at the web GUI and can ping the server.  Attempted to connect via Firefox 148.0.2 and Chrome 138.0.7204.184.

Edited by Raptor2213
  • 1
gulyman Newbie

gulyman

Posted
Posted
On 3/13/2026 at 5:53 PM, Raptor2213 said:

Having the same issue.  Entering the above command just returns: 
Failed to start transient service unit: Unit websocat.service was already loaded or has a fragment file.

Fresh install.  I'm looking at the web GUI and can ping the server.  Attempted to connect via Firefox 148.0.2 and Chrome 138.0.7204.184.

I get this same error when trying to run vendor_service.py.

  • 1
h04x Newbie

h04x

Posted
Posted

Having the same issue 

On 3/19/2026 at 2:58 AM, gulyman said:

I get this same error when trying to run vendor_service.py.

 

On 3/14/2026 at 12:53 AM, Raptor2213 said:

Having the same issue.  Entering the above command just returns: 
Failed to start transient service unit: Unit websocat.service was already loaded or has a fragment file.

Fresh install.  I'm looking at the web GUI and can ping the server.  Attempted to connect via Firefox 148.0.2 and Chrome 138.0.7204.184.

Same issue, completely fresh install. 

  • 1
Isaac.K Newbie

Isaac.K

Posted
Posted

Still having this issue. Shell command also produced the same error as others. Basically haven't be able to use the Hex-OS interface since i bought it haha. 

Great value right there.

  • 0
Fieldsend Newbie

Fieldsend

Posted
Posted

I've also got this issue, I don't want to touch anything as it's currently working well otherwise. Would be keen to know if anyone's found a solution.  

  • 0
Fieldsend Newbie

Fieldsend

Posted
Posted
23 hours ago, Mobius said:

Just confirming your issues are post claiming server with hexos?

Mine was - claimed some time ago. It now says it's not available but I can still go through TrueNAS.

  • 0
WVSTEALTH Newbie

WVSTEALTH

Posted
Posted

Same here, claimed my server in december last year however for since like February/March I've been unable to connect to the server using the hexos dashboard. Server is up and running, I can see it in the network, I can connect to it using truenas interface, I just can't get hexos to connect to it for some reason...

  • 0
WVSTEALTH Newbie

WVSTEALTH

Posted
Posted
20 minutes ago, Mobius said:

what parts are in your servers?
is there anything you setup in the truenas interface? (ex. storage pool was made in truenas)

Fairly basic server setup with a N100 CPU (AOOStar WTR PRO with 4x 4tb HDDs <ST4000DM004-2U9104>)
Really haven't done much in truenas other than debugging an issue I had with plex so it should be mostly the same as hexOs set it up originally.

  • 0
Sonic Proficient

Sonic

Posted
Posted

Several other users have also a WTR Pro (Intel and AMD version) and are able to run HexOs without any issue. So the hardware is not the problem.

Did you run by any change a TrueNas update?

  • 0
WVSTEALTH Newbie

WVSTEALTH

Posted
Posted

I'm still on 24.10.2. According to Truenas I currently have 2 boot environments, 24.10.2 which was created 23/03/2025 and 24.10.0 which was created in 19/12/2024. Guessing that was when it was updated but can't say for sure if it was me or hexos doing it.

  • 0
Sonic Proficient

Sonic

Posted
Posted

There was no TrueNas update via HexOs yet. I suspect that you did run the TrueNas update via TrueNas. I think this the reason that you are unable to Connect to the HexOs deck.

  • 0
Bulbous_assassin Newbie

Bulbous_assassin

Posted
Posted

I'm afraid I just started to get the same issue, connecting via truenas interface works and I'm running  on version 24.10.0.

System is running as a ZFS 2 with mirrored boot ssd all set up from truenas interface, however I've been connecting fine via the command deck for days without issue since any changes have been made.

  • 0
smib Newbie

smib

Posted
Posted

Add another to the pile.

I have not had to log into the deck for quite a while, but found it unable to connect today. Shares, Plex, and TrueNAS ui are working fine, TrueNAS is version 24.10.0.

Please sign in to comment

You will be able to leave a comment after signing in



Sign In Now
 Share
Go to question listing
×
×
  • Create New...