How to fix QNAP NAS web GUI interface timing out or never loading

The Problem

You’re trying to connect to your NAS’s web interface but it’s just spinning forever and not actually loading. 

The Cause

The cause can be a number of things, but it boils down to an issue with the http service or proxy service on the QNAP. 

Sometimes a configuration problem will cause the service to behave badly. A firmware update may cause a mismatch between the config file and the service being run.

The Fix

I’m assuming at this point that you’ve tried rebooting the NAS and that hasn’t resolved the issue. Here are some other things you can try.

Reset the Admin account config

1: Download, install and run WinSCP

2: In WinSCP, set the option to show hidden files (keyboard shortcut Ctrl-Alt-H or Click Options > Preferences > Panels and ensure that “Show hidden files” is checked, then click OK )

3: Connect to the IP of your QNAP NAS as Admin

4: Click Open Directory and enter: /etc/config/.qos_config/users/admin/

5: Download the config and .qtoken files to your local machine as a backup

6: Delete the config and .qtoken files on the QNAP

7: Click Commands > Open Terminal

8: Type “reboot” and click execute to reboot the NAS

Note it may take a long time for the NAS to reboot. Leave it to do what it needs to do for at least half an hour. Periodically attempt to reconnect to WinSCP / the Web page, or use QFinder to determine when the QNAP is back online.

Restart the HTTP server / amend configuration

If the above does not work, you may have a different problem, not currently covered in this guide. It’s worth restarting the http service and confirming both start OK. Note all commands here are case sensitive. Slashes (\) and backslashes (/) are also not interchangeable as they are in a Windows environment.

1: Download and run Putty

2: Connect to your QNAP via SSH and log in as Admin

3: Type cd /etc/init.d/

4: Type ls -1 | grep 'http' to list all the http shell scripts, you should see both “” (Web Server) and “” (Apache Proxy)

5: Type ./ restart to restart Qthttpd, confirm that shutdown and start both return OK.

6: Type ./ restart to restart thttpd, confirm that shutdown and start both return OK

If the apache proxy does not start:

1: Type /sbin/getcfg SYSTEM "Web Access Port", you should see “8080” being displayed. If it does not,

2: Type /sbin/setcfg SYSTEM "Web Access Port" 8080 to set the access port to 8080 as should be default

3: Type /etc/init.d/ restart to restart the thttpd service and apache proxy

2 thoughts on “How to fix QNAP NAS web GUI interface timing out or never loading”

  1. Thanks for this. What if I’m unable to access the system even via SSH?
    My TS-253D boots and is responsive for a time, but then drops the web interface, and then drops off DNS, while still maintaining shares, activity and is available via the Android app.
    It’s fully up to date.
    Any ideas?

Leave a Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.