Why this matters
Wrong protocol, username or account scope can resemble a wrong password.
Step by step
- Record the client error and compare hostname, protocol and username with the verified instructions.
- Check credentials privately or use the supported reset process; avoid repeated guesses that may lock the account.
- A successful connection should show only the paths that the user is authorised to access.
Keep the result of the final check and any unresolved question with your project records.
Availability depends on the product, permissions and management agreement. Use the existing support conversation for the same issue.
