Page 6 of 8
Re: TOS 6.0.770 (X86) is Released for Update
Posted: 27 Aug 2025, 07:23
by jpeckinp
Was having issues with remote connection. First time found it was my Adguard blocking it. I had a reboot last week and nothing would bring it back up. I was under the impression the the TNAS ID should never change. The number I've had since day one always worked. It was coming up telling the ID was already in use. So I tried a new number and now it works. Am I wrong that the ID should always be the same?
Re: TOS 6.0.770 (X86) is Released for Update
Posted: 27 Aug 2025, 09:17
by TMeric
jpeckinp wrote: ↑27 Aug 2025, 07:23
Was having issues with remote connection. First time found it was my Adguard blocking it. I had a reboot last week and nothing would bring it back up. I was under the impression the the TNAS ID should never change. The number I've had since day one always worked. It was coming up telling the ID was already in use. So I tried a new number and now it works. Am I wrong that the ID should always be the same?
Yes, you are correct. The TNAS ID is bound to the device ID, and each NAS has a unique device ID. A previously bound TNAS ID will only be released if your NAS has been assigned a different TNAS ID. Therefore, the situation you encountered is indeed unusual, as your TNAS ID has never changed, and no other TNAS ID has been used on your NAS.
Re: TOS 6.0.770 (X86) is Released for Update
Posted: 28 Aug 2025, 01:38
by jpeckinp
TMeric wrote: ↑27 Aug 2025, 09:17
jpeckinp wrote: ↑27 Aug 2025, 07:23
Was having issues with remote connection. First time found it was my Adguard blocking it. I had a reboot last week and nothing would bring it back up. I was under the impression the the TNAS ID should never change. The number I've had since day one always worked. It was coming up telling the ID was already in use. So I tried a new number and now it works. Am I wrong that the ID should always be the same?
Yes, you are correct. The TNAS ID is bound to the device ID, and each NAS has a unique device ID. A previously bound TNAS ID will only be released if your NAS has been assigned a different TNAS ID. Therefore, the situation you encountered is indeed unusual, as your TNAS ID has never changed, and no other TNAS ID has been used on your NAS.
I literally just typed in one different number at the end. Was xxxxx8 now xxxxx5. I tried going back to the original and still got the in use error.
Re: TOS 6.0.770 (X86) is Released for Update
Posted: 29 Aug 2025, 17:15
by Arendatr
Not worked Docker manager
Re: TOS 6.0.770 (X86) is Released for Update
Posted: 30 Aug 2025, 05:27
by TMzethar
Arendatr wrote: ↑29 Aug 2025, 17:15
Not worked Docker manager
Please ensure that Docker Engine has been installed and enabled.
Re: TOS 6.0.770 (X86) is Released for Update
Posted: 01 Sep 2025, 02:53
by Arendatr
TMzethar wrote: ↑30 Aug 2025, 05:27
Arendatr wrote: ↑29 Aug 2025, 17:15
Not worked Docker manager
Please ensure that Docker Engine has been installed and enabled.
Yes, Docker Manager and Docker Engine has been installed and enabled. Not worked after upgrade to .770.
Re: TOS 6.0.770 (X86) is Released for Update
Posted: 01 Sep 2025, 08:06
by drakey83
I didn't update until my NAS told me that there was an update available, this was after the update was halted because of this problem, but I am still seeing this "WAN Disconnected" error on my NAS F4-424. Any fix for this?

Re: TOS 6.0.770 (X86) is Released for Update
Posted: 01 Sep 2025, 19:15
by TMzethar
If you remember, your question should be related to this. Have you tried the solution provided by outkastm?
viewtopic.php?p=44003#p44003
Re: TOS 6.0.770 (X86) is Released for Update
Posted: 01 Sep 2025, 19:20
by TMzethar
Please contact the official website's Live Chat to schedule a remote troubleshooting session. Please attach the link to this forum post.
Re: TOS 6.0.770 (X86) is Released for Update
Posted: 01 Sep 2025, 23:26
by drakey83
I had already tried that step but it was still not working. I was however able to get it to work correctly now by uninstalling and reinstalling Tailscale.