On this page
You sign in at dash.clouduxe.com. The page is headed "Sign in to your account"
and asks for Email address and Password.
Signing in
Enter the address you registered with and your password, then press Sign in.
A bad pair returns "Incorrect email or password." The wording is the same whichever of the two was wrong, on purpose.
Sign-in is rate limited to eight attempts per 15 minutes, counted both per IP address and per email address. Past that you get "Too many sign-in attempts. Try again in about N minute(s)", where N is how long is left. A successful sign-in clears the counter on your account.
When your account has two-factor authentication
If you have TOTP two-factor enabled, the password step is followed by a second screen titled "Two-factor authentication", with one field, 6-digit code, and one button, Verify & sign in. Enter the code your authenticator app is showing right now.
Setting 2FA up in the first place is covered in Security and 2FA.
If the code is rejected
You get "That code didn't match, or it just expired. Enter the current 6-digit code." Work through these in order:
- Use the code on screen now, not one you copied a moment ago. Codes roll over on a timer, and one that was valid when you copied it is not valid when you paste it.
- Check the clock on the device running the authenticator. TOTP codes are derived from the current time, so a phone whose clock has drifted generates codes the server will not accept. Turning automatic time back on fixes it.
- Check you are entering the code for the right account if your authenticator holds several.
You get three tries on one prompt. On the fourth you see "That didn't work. Please sign in again to get a new code prompt." and you are dropped back to the password screen. Enter your password again and you get a fresh prompt.
The prompt itself expires about five minutes after the password step. If it has been sitting open longer than that, start again from the password screen.
Use a different account on that screen reloads the sign-in page and discards the prompt.
If you have forgotten your password
Use Forgot password? under the password field. That opens "Reset your password", which asks for your Email address and has one button, Send reset link.
The reply is always the same sentence, whether or not an account exists on that address: "If an account with that email exists, we've sent a password reset link. It may take a minute to arrive."
Reset requests are limited to three per 15 minutes for the same address, and five per 15 minutes from one IP address.
Setting the new password
The emailed link opens "Set a new password". It asks for:
- Email address, prefilled where the link carries it. It must be the address the reset link was issued for. The link alone is not enough, because the address is sent upstream with it.
- New password, at least 8 characters.
- Confirm new password, which must match.
When it saves you are signed in immediately and land on your dashboard.
Two things can go wrong with the link itself. If the page opens without its code it shows "This reset link is missing its code. Open the link from your email again, or request a new one." and renders no form at all. If the code is expired or already used, the page rejects it and asks you to request a new one. In both cases go back to Forgot password? and start over.
When a session expires
A signed-in session lasts up to seven days by default. While you are working the panel renews its upstream token in the background, so an ordinary session does not drop you part way through a task.
When a session does end, the next page you open takes you to the sign-in page carrying a notice: "Your session expired. Sign in to pick up where you left off."
The page you were trying to reach is remembered. Sign in and you land back on it rather than on the dashboard. Only same-site paths are carried this way, so the mechanism cannot be used to bounce you to another site after signing in.
Signing out ends a session immediately. Sign out is the last item in the account menu, behind your name at the bottom of the sidebar. A session can also be ended from another device under Signed-in devices, in which case the next request from the ended device stops working. Both are covered in Security and 2FA.