Klaus iOS Troubleshooting
What to check, in order, for sign-in, device discovery, offline, and reconnection problems.
The sign-in page won't open, or third-party sign-in fails
First confirm that Safari can open https://klaus-ai.cn normally, then switch between Wi-Fi and cellular and try again. Google and GitHub sign-in require access to the corresponding services; if your network blocks or interrupts the authentication page, sign in with your Klaus email and password instead.
A system clock that is clearly wrong also causes HTTPS certificate validation to fail — turn on automatic date and time in iOS settings first. If the app does not return automatically after authentication completes, close the authentication page and start over once; do not keep stacking multiple sign-in windows.
Signed in, but no desktop devices appear
Check the following in order:
- Are your phone and computer signed in to the same Klaus account — not merely the same model subscription?
- Is the desktop app running and online?
- Is "Settings → Remote Control → Allow remote control of this device" enabled on the desktop?
- Tap "Reconnect All Devices" or refresh the device list on your iPhone.
If the desktop app just switched accounts, wait for the old connection to end first, then confirm the toggle is still enabled.
A device shows offline or keeps reconnecting
Confirm the computer has not gone to sleep, quit Klaus, or lost its network connection. Then tap "Reconnect" for that computer in the device list on your phone. If it still does not recover, turn remote control off and back on in the desktop app so the device registers again.
A VPN, proxy, or corporate network may interrupt long-lived connections. Test with cellular and with regular Wi-Fi separately to determine whether the problem is on the phone's network or the computer's; the two devices do not need to be on the same local network.
A message was sent but nothing continues
First check whether the currently selected device is still online, and whether the session is waiting on a permission confirmation. When the desktop is locked, asleep, or closed, the history already displayed does not disappear, but new messages cannot execute. Send the message again once the connection is restored; if you are unsure whether the previous one arrived, look at the end of the session first to avoid assigning the same task twice.
If you still cannot pinpoint the problem, generate a debug report from the session menu of a session you can manage, then contact support at support@klaus-ai.cn.