Can't Log In to TrekMail Webmail?

Most webmail sign-in problems come from a wrong mailbox password, an incomplete email address, the wrong webmail host, or an old browser session. Work through this checklist before opening a support ticket.

Check 1: Use the mailbox password, not the Dashboard password

This is the single most common cause. TrekMail has two different passwords:

• Dashboard password: used to sign in to the account Dashboard, where domains, billing, and mailboxes are managed.
• Mailbox password: used to sign in to webmail and email apps. Each mailbox has its own password.

They are completely separate. If you've been trying your dashboard password in webmail, that's why authentication is failing.

If you do not know the mailbox password, see Forgot Your TrekMail Password? for the recovery options.

Check 2: Enter the full mailbox address

Enter the full address, such as alice@yourcompany.com. Do not enter only alice or alice@.

Some browsers' password managers store an incomplete value if you originally entered it without the domain. Clear the saved entry, re-type the full address, save again.

Check 3: Re-enter the address and password

Delete the saved entry and type it again. Check that the address belongs to the mailbox and that the password manager has not filled an old password. A browser or phone can continue offering a saved password after an admin reset.

Check 4: Use the right webmail address

If webmail tells you "This webmail address belongs to a different organization", the mailbox belongs to a different branded service. Open the webmail address supplied by your provider. The message deliberately does not name the organisation.

The standard webmail entry point is https://trekmail.net/webmail/login. If your provider uses White Label Lite, use the active Webmail host shown by that provider. The branded dashboard host and branded webmail host are separate addresses.

If the branded URL gives you a certificate error or "this site can't be reached":

• Do not ignore the certificate warning. Contact your provider so they can check the branded host. Providers can use White Label DNS Troubleshooting.
• You can also try the standard TrekMail webmail login if your provider has instructed you to use it.

Check 5: Check the mailbox status with the account owner

Two cases where a known-correct password still won't let you in:

• Mailbox sign-in is suspended. The account owner can check the mailbox status in the Dashboard and restore access if appropriate.
• The account needs attention. Billing, abuse, or deliverability issues can affect access. The account owner should review the Dashboard notices and, where relevant, Fixing Failed Payments.

Some sign-in messages are intentionally generic so the page does not reveal whether a mailbox exists. Ask the account owner to check the status instead of repeatedly guessing the password.

Check 6: Stop after repeated failed attempts

Repeated failed attempts can trigger a CAPTCHA or a temporary sign-in block. This protects mailbox accounts from guessing attempts.

Complete a CAPTCHA if it is shown. Some branded hosts may not show a CAPTCHA, but the temporary sign-in limit still protects the form. If you see "Too many attempts," stop retrying and try again after the temporary block expires.

If you do not remember the password, use self-service password reset rather than guessing.

Check 7: Try a clean browser session

Particularly common after a password change, an admin reset, or switching between accounts:

• Clear cookies and saved site data for the webmail address you are using.
• Reload the login page without using an old saved bookmark.
• Try a private/incognito window. If login succeeds there but fails in the main window, it's cache.
• Try a different browser as a confirmation test.

Two-factor authentication (2FA) problems

If your mailbox has 2FA enabled, you'll see a code prompt after entering your password. Here's how to handle issues at that step.

Symptom: 6-digit code rejected even though it looks correct

Authenticator codes are time-based. An incorrect phone clock can make a current-looking code fail.

Fix:

• iPhone: Settings → General → Date & Time → Set Automatically ON.
• Android: Settings → System → Date & Time → Use network-provided time ON.

After enabling automatic time, generate a new code and try again.

Symptom: Lost phone, deleted authenticator app

Use one of your recovery codes, which are single-use backup codes from 2FA setup. After signing in, update the mailbox security settings for the new device and generate fresh recovery codes if needed.

Symptom: Lost recovery codes AND lost authenticator

Contact the account owner or support. Include the mailbox address and enough non-secret information to help identify the account. Do not send a password, recovery code, or full payment details.

Symptom: Not being asked for a code, but 2FA is supposed to be on

The current session may still be valid. Sign out and start a new session to confirm whether 2FA is active.

Symptom: Authenticator app shows codes but webmail says the secret is invalid

Make sure the authenticator entry was created from the QR code for this mailbox. If it was not, ask the account owner to help reset mailbox 2FA before setting it up again.

Error messages decoded

Still stuck

Open a support ticket from the Support page and include:

• The mailbox address you're trying to log into.
• The exact URL you're hitting (trekmail.net/webmail/login vs branded).
• The exact error message you see (or a screenshot).
• Whether the dashboard login at trekmail.net/login works for you (this confirms whether the broader account is healthy).
• What you've already tried from this list.

Do not include a password, recovery code, or access token in the ticket.