Why is my Security Center stuck on the loading screen after installation?
Applicable Products
QTS, QuTS hero, Security Center 3.1.0 or later
Symptom
After launching Security Center, the interface remains stuck on the loading screen and does not complete the initialization process.
Root Cause
This issue occurs if the InnerWebAccessPort setting in the system configuration file has been changed from the default port 58080 to an unsupported port like 48080. Security Center relies on the default port for internal communication and will not start correctly if this port is altered.
This change might occur due to manual modification by the user or third-party software but is not currently validated by Security Center, which leads to silent failure.
Solution
Log in to the NAS using SSH as an administrator.
Check current port configuration:
ps | grep thttpAbnormal:
/usr/local/sbin/_thttpd_ -p 48080Normal:
/usr/local/sbin/_thttpd_ -p 58080
Edit the configuration file:
vi /etc/config/uLinux.confRemove or comment out this line:
InnerWebAccessPort = 48080Restart web and security services:
/etc/init.d/Qthttpd.sh restart /etc/init.d/stunnel.sh restart /etc/init.d/thttpd.sh restart
5. Restart Security Center.
Security Center should now load properly using port 58080
Further Reading
Security Center Quick Start Guide
How do I adjust threshold settings in Security Center to reduce frequent alerts?