After restarting the server, the login screen no longer appears as shown below. If you have any knowledge about this issue, I would appreciate your guidance.
Server was restarted
No response when pinging from iPhone
ttps://xxx:443/ → ng
ttps://IP address:443/ → ng
ttp://xxx:8080/ → ng
ttp://IP address:8080/ → ng
↑ I removed the “h” from the beginning of the service protocol (h)ttp because posting links as-is would treat them as links.
*When checking the connection via IP address, it was over LAN; when checking via xxx, it was using the host name resolved by DDNS over WAN/LAN.
*Up until now, I was able to access the server using any of the above URLs.
The following screen appears to be the blue background before the login input, so it seems to reach the OS before login…? However, since ping does not go through, I am at a loss.
Also, if you don’t mind, how long have you been using your current hard drives? We also recommend checking the health status of your drives. Thank you!
Thank you for contacting us.
Currently, I am unable to even SSH into the system, so I am not able to handle QA either.
Also, regarding the HDD, I have only been using it for about a month since purchase, but it is showing errors and I am unable to write to it.
I was able to read from it, so I backed up about half of the data to another device, but after that, I was not even able to connect to it.
In that situation, there is a possibility that there is an issue with the hard drive (硬碟).
We apologize for the inconvenience, but could you please submit a support ticket? Our Support Team will assist you in further identifying and resolving the issue. Thank you very much!
Hi @TAKUWAN, please try turning off the NAS once, slightly pulling out all the drives to set it to a “no drives installed” state, and then turning it back on.
If your NAS has an LED panel, you can check the IP displayed on the panel, or you can use Qfinder to find the IP address.
If you are able to access ttp://IP address/ (Port 8080 is not necessary) in this state, it is highly likely that the cause is on the drive side.
