I had reassigned the http and https ports long ago and have never had an issue in accessing the home page.
Today, I cannot access the home page from my LAN. I can ping the IP address and I can use Samba to access the shared folders from other devices on the network.
If I use the IP address without the port number, I get a resonse:
"Your TNAS device is operating normally. You need to configure the network parameters correctly to access the system page."
When I add the port number, it just times out.
Is there any way to get back so I can manage the NAS?
Can't Access Homepage from LAN - TOS 5
Re: Can't Access Homepage from LAN - TOS 5
What is your TNAS model and TOS version?
If you can log into the terminal, you can check the CPU/RAM usage as well as view process information.
Please post the process info here if you can.
You can also try restarting the TNAS, which may resolve the anomaly that is occurring.
If you can log into the terminal, you can check the CPU/RAM usage as well as view process information.
Please post the process info here if you can.
You can also try restarting the TNAS, which may resolve the anomaly that is occurring.
To contact our team, please send email to following addresses, remember to replace (at) with @:
Technical team: support(at)terra-master.com (for technical support)
Service team: service(at)terra-master.com (for purchasing, return, replacement, RMA service)
Technical team: support(at)terra-master.com (for technical support)
Service team: service(at)terra-master.com (for purchasing, return, replacement, RMA service)
Re: Can't Access Homepage from LAN - TOS 5
It's an F2-221 running 5.1.41
Yesterday, I tried rebooting via forced power cycle which didn't alleviate the inability to get to the web page.
I didn't attempt logging in via the terminal. Not sure I would be able to since I have most protocols disabled in the config.
Today, it powered up normally via it's scheduled power-up schedule and is behaving normally. I have logged in via the web page and can run the functions that I have needed.
I was prepared to offload all its data via Samba to another server and rebuild the system drive but have held off while observing the behavior and running a full backup just in case.
Yesterday, I tried rebooting via forced power cycle which didn't alleviate the inability to get to the web page.
I didn't attempt logging in via the terminal. Not sure I would be able to since I have most protocols disabled in the config.
Today, it powered up normally via it's scheduled power-up schedule and is behaving normally. I have logged in via the web page and can run the functions that I have needed.
I was prepared to offload all its data via Samba to another server and rebuild the system drive but have held off while observing the behavior and running a full backup just in case.