On this page
Everything that protects your Clouduxe account lives on one page: your password, two-factor authentication, the devices currently signed in, and a log of recent sign-in attempts.
Changing your password
The Change password card takes Current password, New password and Confirm new password, then Update password.
The rule the panel enforces is 8 characters. Anything shorter is refused with "New password must be at least 8 characters." The card recommends at least 12 characters and a password you use nowhere else, which is worth following, but 8 is the point where the form stops objecting.
If you cannot supply the current password, you cannot change it here. Use Forgot password? on the sign-in page instead, covered on Signing in.
Two-factor authentication
With 2FA on, every sign-in asks for a 6-digit code from an authenticator app on top of your password. The Two-factor authentication card shows Off or Enabled and carries the control either way.
Clouduxe 2FA is authenticator-app only. There are no codes by SMS, no email codes, and no printable recovery codes.
Setting it up
Choose Enable 2FA
The Enable two-factor authentication dialog opens and fetches a fresh secret for your account. Nothing is enabled yet: 2FA turns on only when you enter a code at the end.
Enter the secret into your app by hand, rather than scanning
Under the QR image the dialog shows Or enter this secret manually with a string of letters and numbers beneath it. That string is the secret. In Google Authenticator, 1Password, Authy, or any other TOTP app, choose the option to add an account by entering a setup key, give it a name such as Clouduxe, paste the secret, and leave the type as time-based.
Prefer this over scanning. The QR image is not drawn by your browser: the panel builds the enrolment link, which contains the secret, and hands it to quickchart.io, an outside image service, to render the picture. Typing the secret in yourself keeps it between the panel and your app.
Save a copy of the secret
Store it with the credential itself in your password manager, or write it down and keep it somewhere physically safe. This is the only backup you get.
Enter the current code
Your app now shows a rotating 6-digit number. Type it into 6-digit code and choose Enable 2FA. The field takes 6 digits and nothing else, and a code that has already rolled over is rejected, so use the one on screen at the moment you submit.
The card then reads Enabled, and the next sign-in asks for a code. Signing in covers that prompt, including what happens when a code is refused.
Turning it off, or moving to a new phone
The Disable button opens Confirm disable, which asks for a current code in the Authenticator code field before Disable 2FA will work. A working app is required to switch 2FA off, which is the whole point, and also the reason to move to a new device deliberately: disable 2FA while the old app still produces codes, then enable it again from the new one, setting the new device up from the secret shown during that second enrolment.
Signed-in devices
The Signed-in devices card lists each device with a session in the panel: the browser and operating system, the IP address it was last seen from, and when that was. The one you are reading this on carries a This device badge.
- Sign out on any other row ends that device's session in the panel immediately. Your password is unchanged, so you can sign back in on that device whenever you want.
- Sign out all other devices does the same to every row except the current one. With only one other device the button reads Sign out the other device.
- You cannot sign the current device out from this list. Use Sign out in the user menu at the bottom of the sidebar.
Two limits worth knowing. This list covers sessions in the panel, so it is the right control for "someone else is in my account" and the wrong one for anything outside it. And a device that signed in long enough ago may not appear here at all: older sessions predate this list and cannot be ended from it. Signing in again on that device replaces its session with one you can see and sign out.
Recent sign-in activity
The Recent sign-in activity card shows the last 10 sign-in attempts on your account, each with a Successful or Failed badge, the device, the location and the IP address. This comes from the billing system rather than from the panel, so it includes attempts made anywhere your Clouduxe login is used, not only here. Where the billing system has no location or no address for an attempt, the row reads Unknown location and the IP is left out.
If a successful sign-in appears that you cannot account for, change your password, sign the other devices out, and turn 2FA on if it is off.