Most problems fall into one of a handful of shapes. Each one below says what the symptom actually means, which is usually the fastest route to the fix.
This means nothing answered. Your credentials were never tried, so the problem is the address, the port, or the network - never the password.
192.168.1.20 does not exist on mobile data. Join the Wi-Fi, or use QuickConnect, a domain or a VPN.| Message | What it means | Fix |
|---|---|---|
| Invalid credentials | The NAS answered and refused the sign-in. Address and port are right. | Check the username and password. Check whether the account uses 2FA - the toggle has to be on. Check DSM's auto-block list under Control Panel › Security › Account in case failed attempts have blocked your address. |
| Certificate error | HTTPS is on and certificate verification is also on, against a self-signed certificate. | Turn Verify SSL Certificate off. Most DiskStations present a self-signed certificate; the connection stays encrypted either way. |
| 2FA required | The account uses two-factor authentication and the toggle is off. | Turn on Two-Factor Authentication (2FA) in the NAS's configuration and reconnect. |
| 2FA codes rejected | Usually a clock, not a code. | Codes are derived from the current time. Check the phone's clock and the NAS's - the NAS's time source is on the home screen's quick-stats row. |
| Was working, now asks to sign in | Stored credentials became unreadable - it can happen after restoring the app onto a new phone. | The app clears what it cannot read and asks you to sign in again. Re-enter the password once. |
John Smith.There are exactly three reasons, and they have different fixes.
One setting fixes this: Tunnel camera live view through DSM port, in the NAS's configuration.
If the log reports a connection timeout while the rest of the app works fine, the thing not answering is the Log Center service on the NAS, not your connection.
Android and iOS decide when a widget may refresh, and both ration it hard to save battery. No app can force one - which is why each widget prints the time its numbers were taken instead of a promise.
The assistant needs an on-device model, and the tab is hidden entirely on hardware that does not have one - a control that cannot work is worse than no control.
Bugs and feature requests go in the public tracker, where they get a number and a thread rather than disappearing into an inbox.
Report a bug or request a feature