Login problems

Login problems can come from several different layers: the account itself, the browser session, email-based recovery, application configuration, authentication integrations, or the server/database environment.

Start by identifying which account you are trying to access. A DotwebApps.com customer account is different from a user or administrator login inside a purchased DotwebApps software product.

Basic login checks #

1. Confirm that you are using the correct product or website.
2. Verify the intended username or email address.
3. Carefully re-enter the password rather than relying on an old saved value.
4. If the product provides a password-reset or account-recovery function, use that documented recovery method.
5. If a recovery email is expected, check spam or junk folders.
6. Try a private/incognito browser session where appropriate to rule out a stale session or cookie issue.
7. If needed, clear only the site-specific browser state for the affected site rather than deleting unrelated browser data.
8. Confirm that the application itself otherwise loads normally.
9. Check whether the issue affects only one user or multiple users.

Possible causes #

Broad causes may include:

• an incorrect username or email address
• an incorrect password
• an account that has not yet been created or made available
• a password-reset problem
• stale browser session or cookie data
• application configuration problems
• email-delivery problems affecting recovery messages
• an authentication integration issue
• a server or database problem preventing login

The exact login and recovery workflow can vary by DotwebApps product, so follow that product’s documentation rather than assuming a universal admin URL or recovery path.

If password-reset email does not arrive #

Confirm that the expected email address is correct and check spam/junk folders. If the application reports an email-delivery error, the problem may be related to SMTP, sender configuration, hosting, or the mail provider rather than the login credentials themselves.

Do not repeatedly change unrelated settings merely because a recovery email is delayed or missing.

Protect your credentials #

DotwebApps support should never need your password.

Do not send:

• your password
• database passwords
• private keys
• API secrets
• payment-card details
• unrelated customer information

If the account requires investigation, provide only the minimum account, product, or order information needed to identify the issue.

When to contact support #

If the account remains inaccessible after the safe checks above, contact DotwebApps support with the product or site involved, the account/email identifier needed to locate the account, the exact error message with secrets removed, the browser/device if relevant, and the troubleshooting steps already attempted.