An accidental leading or trailing space can make a service address, username or password fail even when the visible letters look right. Some input screens trim whitespace and others preserve it. Compare the copied value with the original instructions before requesting a replacement account.
Find where the extra character entered
Selection from a message bubble can include a space or newline. A browser address field may also normalize text differently from an app login field. Copy one value at a time rather than an entire paragraph containing labels and punctuation.
Treat passwords as exact strings
Do not remove internal spaces or change case merely because a login failed. Those characters may be intentional. The safe correction is removing clearly accidental surrounding whitespace while preserving the supplied value itself.
Avoid repeated blind attempts
Rapid retries with slightly different values can obscure the useful error message or trigger service protections. After a careful comparison, send support the error text and nonsecret account reference. Do not include the password in a public post.
A practical sequence
- Copy the value without its label.
- Check for extra spaces at both ends.
- Retry once after correcting a confirmed copying error.
An example
Copying “Server: https://example.invalid ” as one value can include both the label and a trailing space. The server field needs only the supplied address.
Questions about this topic
Should usernames always be lowercased?
No. Preserve the case supplied for the account.
Can a space be part of a password?
Yes. Do not alter intentional internal characters.
