TerraMaster Forum

I'm running Linux Mint Debian Edition V6, fully updated, and have just had to switch to a new router (an Archer AX-10000 if that makes any difference).

The router finds the TNAS just fine, and gives me the IP address for the device. The device pings without a problem, it's definitely connected!

The latest version of the desktop app for Ubuntu cannot find the device (is it tied to Ubuntu in some way?), and if I point a browser at 192.168.0.18, it just times out. If I try to add the device manually via the TNAS desktop app, I just get a two-second error message "Addition failed", which is uninformative, to say the least.

I have tried the procedure to remove all the drives and then reboot the device, but this made no difference. The device was working just fine off my old modem/router, but it then had an IP address of 192.168.1.227 (no typo, 0 on the new router but 1 on the old one).

Help, please! How do I access the device that the router can see, and which pings correctly, but the desktop app and the browser cannot find?

BTW, I would have tried an upgrade to v6 of the operating system, but i'm not sure what version I'm currently running, and don't know how I can check when I can't access the device. I know it's 5.something, but not the exact version.

brian666 wrote: ↑12 Sep 2025, 23:14

Hello! Thank you for reaching out to Terramaster!
Since Ubuntu desktop applications can only search for devices with IP addresses in the same network segment, please perform the following checks:
1.Is your Ubuntu system and TNAS connected to the same router?
2.Has a static IP address been configured for your TNAS on the old router? If yes:
First, access the TNAS normally via the old router.
Then, change its IP address to DHCP (dynamic acquisition) mode.
After that, replace the router, restart the TNAS, and check if the device can be searched normally.
3.If no static IP address has been set for your TNAS:
Please refer to Method B in the links guide to enter the boot system. viewtopic.php?t=423
Check if the device can be searched normally at this time.

One point of correction, not that I think it will make any difference - I am running the *Debian*-based version of Linux Mint, not the more popular Ubuntu-based version. The base for my system is Debian 12.

OK, with that out of the way, I have managed to connect to the TNAS, at least I have managed to mount it from the command line.

What I am not able to do is to access the control panel through a web browser. I know my username, but it rejects my password - the same one as I used to mount the TNAS - with an error message which is too fast for me to read, but I am assuming is an "invalid password" or similar.

I have gone through the 'forgot my password' routine, entered my username and the recovery e-mail, clicked the 'send code' button, but the code to change my password never arrives. I know I have the correct username (used to successfully mount the TNAS) and I know I have the correct recovery address (a deliberately wrong address generates an error message).

Can you assist further?

Thanks,

Brian.

brian666 wrote: ↑14 Sep 2025, 17:41 One point of correction, not that I think it will make any difference - I am running the *Debian*-based version of Linux Mint, not the more popular Ubuntu-based version. The base for my system is Debian 12.

OK, with that out of the way, I have managed to connect to the TNAS, at least I have managed to mount it from the command line.

What I am not able to do is to access the control panel through a web browser. I know my username, but it rejects my password - the same one as I used to mount the TNAS - with an error message which is too fast for me to read, but I am assuming is an "invalid password" or similar.

I have gone through the 'forgot my password' routine, entered my username and the recovery e-mail, clicked the 'send code' button, but the code to change my password never arrives. I know I have the correct username (used to successfully mount the TNAS) and I know I have the correct recovery address (a deliberately wrong address generates an error message).

Can you assist further?

Thanks,

Brian.

Hello,
Thank you for your feedback, and we sincerely apologize for any inconvenience caused.
May we ask: are you able to access the TNAS terminal via SSH using your known username and password? If so, please feel free to contact our online support team on the TerraMaster official website (https://www.terra-master.com) to schedule a remote session. Our engineers will then assist you remotely in diagnosing and resolving the issue.

No, the ssh connection is refused, at least on port 22. Is there some other port which I should be using?

brian666 wrote: ↑14 Sep 2025, 18:44 No, the ssh connection is refused, at least on port 22. Is there some other port which I should be using?

The SSH port on your TNAS is 9222. Please try using this port to connect again.

The connection is still refused using port 9222.

brian666 wrote: ↑14 Sep 2025, 20:55 The connection is still refused using port 9222.

Hello,
Thank you for reaching out. Unfortunately, we are currently unable to provide remote technical support for your issue.
As an alternative solution, you may reinstall the system yourself by following the instructions in the link below:
System Reinstallation Guide:
viewtopic.php?t=423
If you have any further questions, feel free to contact us.

Method A) for the reinstallation is not possible as I cannot log in to the desktop, as described upthread.

I have tried method B) once already and TNAS PC still could not find the TNAS. However, I will probably try it again, as there does not appear to be a lot else I can try, unless I am just going to continue with the TNAS as is - the drives are accessible, but the desktop is not. I do not want to run the risk of 'bricking' the TNAS.

brian666 wrote: ↑15 Sep 2025, 01:28 Method A) for the reinstallation is not possible as I cannot log in to the desktop, as described upthread.

I have tried method B) once already and TNAS PC still could not find the TNAS. However, I will probably try it again, as there does not appear to be a lot else I can try, unless I am just going to continue with the TNAS as is - the drives are accessible, but the desktop is not. I do not want to run the risk of 'bricking' the TNAS.

Hello, if you can't find the NAS, it might be an issue with the boot system. After removing all hard drives and starting the NAS, can you hear any beeps? If you only hear one beep instead of three, it is usually a boot system anomaly. You can refer to this post to recreate the boot system: viewtopic.php?t=6433.

By the way, if you want to install TOS 6, you can also directly create a TOS 6 boot system.