Not sure if this belongs here as a question or as a bug report, but going to post it here first.
I recently tried updating to the 26 beta version and ended up with a non-bootable system. Instead of troubleshooting the issue I just decided to go back to 25.10 by doing a fresh install and importing the configuration file that is downloaded once the system was bootable again.
Everything seemed to work just fine except I realized TrueNAS connect is now showing Connection Failed… only option is to retry connection which still fails. I was not able to find an option in the web interface to reset the connection or disconnect from TrueNAS Connect or anything like that.
Going to Claude for assistance, I find the midclt call tn_connect.config and related options. Specifically Claude recommended running midclt call tn_connect.update '{"enabled": false}' followed by running tn_connect.get_registration_uri and tn_connect.generate_claim_token. Before running commands from an LLM I wanted to double check with the community to see if this is indeed the correct way to go about this. Am I missing the option in the web interface to do this or is the shell commands the correct way to do this?
yeah after a config import Connect getting stuck on Connection Failed is pretty common in my experience. the GUI retry button doesnt actually drop the old claim. i would probably do the midclt tn_connect.update ‘{“enabled”: false}’ first, then generate a new claim token, rather than jumping straight to get_registration_uri. might also check if the old system is still listed in the TrueNAS Connect dashboard and remove it there, otherwise the new box keeps bouncing off the old pairing.
Could you please confirm if your system still shows up on the TrueNAS Connect Dashboard page? It will be offline, but just confirm if the card for the system is still present on the Dashboard.
Got it, I think you have found a user experience point that we can improve
In the TrueNAS Connect web interface, find the old entry for this system and unregister it. This is the step that actually unblocks you. Until it is gone, nothing you do on the NAS will help.
On the NAS, go to the TrueNAS Connect settings and turn the service off. That clears the stale registration that came across in your config.
Turn it back on, and it will walk you through the claim and registration exactly like a first time setup.
Ultimately this is due to how we use the system’s UUID as an identifier, which is restored as part of the config file restoration process to the same UUID the system had before the reset. So after config restoration the system is reaching out to TrueNAS Connect and we are responding with “You are already registered”.
Thanks for bringing this to our attention we will look at ways to improve this process.
