NAS Codex › QNAP › Can't connect to your QNAP NAS remotely through myQNAPcloud: what QNAP says to check
Can't connect to your QNAP NAS remotely through myQNAPcloud: what QNAP says to check
Your QNAP NAS works on the local network, but the mobile apps or utilities cannot reach it over the internet through myQNAPcloud. QNAP says myQNAPcloud Link is required for remote access, and its FAQs give a short order of checks: update, re-enable, check the status, then run the built-in diagnostics. QNAP also explains what errors on the myQNAPcloud Web Connectivity screen mean. This page covers both.
Written against: myQNAPcloud and myQNAPcloud Link on QTS and QuTS hero (QNAP FAQs last modified 2022-08-11, 2024-06-05 and 2026-04-29). Last Updated: November 2026. Vendor menus and wording change between versions; if yours differ, follow the vendor page linked under Sources.
Before anything else: if the data on this NAS is not backed up somewhere else, copy it off first. Do not continue with any step on this page until you have.
Fast Answer
Update your QNAP mobile apps from the App Store or Google Play, and update myQNAPcloud Link in the NAS's App Center. Then go to myQNAPcloud > myQNAPcloud Link, disable it and enable it again, and check that the status shows Normal. If it shows Abnormal, or shows Normal but you still cannot connect, open the option menu at the upper right of myQNAPcloud, choose Diagnostics and click Run, then follow the on-screen instructions.
Step 1: update the apps and myQNAPcloud Link
QNAP's troubleshooting FAQ says myQNAPcloud Link is required for remote access to a QNAP NAS, and that the first thing to try is updating:
- On your phone, update your QNAP mobile apps to the latest versions from the App Store (iOS) or Google Play (Android).
- On the NAS, open App Center, find myQNAPcloud Link and update it to the latest version.
A second QNAP FAQ explains why updating matters. It says some users found that their mobile apps or utilities could no longer reach the NAS through myQNAPcloud Link after February 29, 2024, because QNAP enhanced its device connection mechanisms and the software must be updated on both the server side and the client side. Its fix is to update myQNAPcloud Link, the QNAP mobile apps and the QNAP Utilities to their latest versions. QNAP notes that this needs myQNAPcloud Link 2.4.52 or later, which in turn requires QTS 4.3.3 or later.
Step 2: enable myQNAPcloud Link again
- On the NAS, go to myQNAPcloud > myQNAPcloud Link.
- Disable myQNAPcloud Link, then enable it again.
- Check its status. QNAP says it displays Normal if the service is working correctly; you can then try connecting from your mobile device again.
Step 3: run the diagnostic test
QNAP recommends the diagnostic test if the myQNAPcloud Link status is Abnormal, or if it is Normal but you still cannot connect remotely:
- In myQNAPcloud, open the option menu at the upper-right corner.
- Select Diagnostics. When the Diagnostics tool appears, click Run.
- The tool scans the system and checks the requirements for myQNAPcloud Link. Follow its on-screen instructions.
If the connection still fails after following the diagnostics, QNAP says to contact QNAP Technical Support.
Errors on the Web Connectivity screen
myQNAPcloud also has a Web Connectivity screen. QNAP's FAQ on errors there says they mean the NAS cannot be managed directly through port forwarding, and that the current setting blocks anonymous attacks from the internet. QNAP's suggested alternatives for remote access are:
- myQNAPcloud Link, which reaches the NAS without port forwarding (Steps 1 to 3 above).
- QVPN with a non-default VPN port, which QNAP describes as an encrypted connection after VPN authentication, and a more secure method.
If you do need direct access through port forwarding, QNAP highly recommends changing the default system port number, and gives these checks:
- Check that port forwarding is configured properly on your router. You may need to restart the router and the NAS after changing these settings.
- Check which ports on the router are open to the internet after setup.
- Make sure the router is connected directly to the internet and does not use another NAT router as its gateway. QNAP says you can check this by confirming that the router's WAN IP address matches the DDNS IPv4 address listed in myQNAPcloud.
- Ask your network administrator or internet provider to confirm the ports are not blocked.
Summary of QNAP's order
- Update the mobile apps, QNAP Utilities and myQNAPcloud Link (2.4.52 or later needs QTS 4.3.3 or later).
- Disable and re-enable myQNAPcloud Link, and check for Normal status.
- Abnormal, or Normal but still failing: myQNAPcloud > Diagnostics > Run.
- Web Connectivity errors: use myQNAPcloud Link or QVPN; for port forwarding, change the default port and check the router.
When to stop and get help
Opening ports is the riskier route: QNAP's FAQ says the Web Connectivity errors reflect a setting that blocks anonymous attacks from the internet, and recommends myQNAPcloud Link or QVPN on a non-default port, with the default system port changed if you do forward ports. If the NAS cannot be found even on the local network, see Qfinder Pro can't find your QNAP NAS.
Questions
Why can't my QNAP apps connect to the NAS remotely?
QNAP says myQNAPcloud Link is required for remote access. Update the mobile apps and myQNAPcloud Link, disable and re-enable myQNAPcloud Link, and check its status is Normal. If not, run Diagnostics in myQNAPcloud.
My QNAP apps stopped connecting after February 29, 2024. Why?
QNAP says it enhanced its device connection mechanisms, so myQNAPcloud Link, the mobile apps and QNAP Utilities all need updating. myQNAPcloud Link 2.4.52 or later is required, which needs QTS 4.3.3 or later.
What do errors on the myQNAPcloud Web Connectivity screen mean?
QNAP says they mean the NAS cannot be managed directly through port forwarding, because the current setting blocks anonymous attacks from the internet. It suggests myQNAPcloud Link or QVPN on a non-default port instead.
Sources
Every fact on this page comes from the vendor documents below, opened on 2026-11-17.