Notification Center, QuLog Center and Container Station web interfaces fail via SmartURL/CloudLink – regression, likely after myQNAPcloud Link 2.5.1 update – TS-264

English General
,
1

I did troubleshooting with AI, and got help with the question below. The caveat here is that I’m not 100% sure when this trouble started, but likely recent or sometime during September.

System

  • Model: TS-264
  • Firmware: QTS 5.2.10.3577 (build 20260731), installed 2026-08-10
  • myQNAPcloud Link: automatically updated from 2.4.73 to 2.5.1 on 2026-10-01 23:18
  • Problem first noticed: 2026-10-02

Symptoms when logged in via SmartURL (qlink.to → myQNAPcloud login → .myqnapcloud.com):
- Notification Center hangs on “Loading data, please wait”
- QuLog Center → Event Log / Access Log / Online Users: “A service exception occurred. (403)”
- Container Station: “Connection Lost” after a few seconds, reappears repeatedly after closing it

The underlying services work fine; only their web interfaces fail via the relay:

  • Notification Center keeps sending email notifications as configured
  • QuLog keeps logging normally (logs are complete when viewed via local IP)
  • Containers keep running and are reachable (e.g. Plex works normally)
  • Other web apps such as QTS desktop, QuMagie and Music Station work fine via SmartURL

These apps’ web interfaces have previously worked normally via SmartURL/CloudLink on this NAS. I can’t confirm exactly when they last worked (sometime before or during September), but this is a regression, not a new setup.

When logged in directly via the local IP (https), all web interfaces work normally.

Troubleshooting done

  • The SmartURL address (.myqnapcloud.com) resolves to the CloudLink relay, not to my WAN IP. My DDNS primary domain is correct and matches my public IP (no carrier-grade NAT).
  • Disabling QuFirewall (also updated 2026-10-01 to 2.6.1.0204) does not fix the problem.
  • NAS restarted; tested in several browsers; system time and storage are OK.
  • Other updates in the window since September:
    • myQNAPcloud 1.1.100 (2026-09-02)
    • myQNAPcloud SSL certificate renewed (2026-09-22)
    • File Station 6 6.0.5.7994 (2026-09-24)
    • Download Station 5.10.4.368 (2026-10-01)
  • Similar user report: myQNAPcloud link

Questions

  1. Is this a known issue in myQNAPcloud Link 2.5.1? When is a fix expected?
  2. Please provide myQNAPcloud Link 2.4.73 (x86_64, TS-264) so I can roll back in the meantime and confirm if this is the problem.
  3. If this is not caused by myQNAPcloud Link 2.5.1, could it be related to myQNAPcloud 1.1.100 (installed 2026-09-02) or the SSL certificate renewal (2026-09-22)?
2

Make tripple sure you never ever ever forward ports from WAN to your QNAP though. (malware)

3

Same symptoms here. QNAP TVS-h674. No changes made other than installation of published QNAP updates. Problem persists after a reboot. Looking forward to the availability of a rollback.

4

It never will point to your WAN and should not. As @dolbyman stated, you never want to put your NAS on the WAN. MyQNAPCloudLink is the secure (or more secure) way to do it.

6

It never will point to your WAN and should not. As @dolbyman stated, you never want to put your NAS on the WAN. MyQNAPCloudLink is the secure (or more secure) way to do it.

To clarify: the NAS is not exposed to the WAN. There’s no port forwarding and UPnP is disabled; I only access it via SmartURL/myQNAPcloud Link. The DNS check was just to confirm that my sessions go through the CloudLink relay, which is expected.

7

Do you know between which updates this problem occurred?