Authentication Problems
Use this page when a SOCKS5 endpoint rejects a username or password. Never include the password in a ticket, log, screenshot, or test result shared with another person.
Symptom, cause, and action
| Observation | Possible cause | Supported action |
|---|---|---|
| A previously working temporary credential now fails | It expired automatically | An ADMIN generates a new temporary credential and updates the application securely. |
| A temporary credential works on one Gateway but not another | Temporary credentials are scoped to the Gateway that issued them | Use it only with a Pool endpoint on its issuing Gateway, or have an ADMIN choose the appropriate credential workflow. |
| A temporary credential fails on Direct Access | Temporary credentials do not support direct Node access | Use a persistent Customer-scoped credential for direct access. |
| A persistent credential stopped working at its configured time | It expired | An ADMIN creates or selects an active credential appropriate for the application. |
| A persistent credential shows REVOKED | Revocation is permanent | An ADMIN creates a replacement. A revoked credential cannot be reactivated. |
| Authentication fails immediately after creation or rotation | The change may still be propagating, or the application still has the old password | Wait approximately 30 seconds, update the stored value, and open a new connection. |
| An old value appears to work immediately after rotation or revocation | An established connection may still be open | Close it and test a new connection after approximately 30 seconds. Lifecycle changes are enforced for new authentication and do not guarantee immediate closure of existing connections. |
| Status and scope are correct but authentication fails | The username, current password, endpoint, or application secret may be stale | Copy non-secret connection values again and securely update the application with the current credential values. |
Temporary credentials are Gateway-scoped, work with Pools only, expire automatically, and cannot be rotated or revoked early by a customer. Persistent credentials are Customer-scoped, work with Pool and direct Node endpoints, may have an expiry, can be rotated while ACTIVE, and can be permanently revoked.
Checks
- Confirm that the application uses the currently displayed endpoint host and port.
- Identify whether the credential is temporary or persistent; do not reveal its password.
- For a temporary credential, confirm the issuing Gateway, Pool target, and expiry.
- For a persistent credential, an ADMIN checks its current status and optional expiry in Proxy Credentials.
- After creation, rotation, or revocation, allow approximately 30 seconds and test with a new connection.
A VIEWER cannot access Proxy Credentials in the current customer interface. A VIEWER can report the endpoint, target, time, and error to an ADMIN without sharing or requesting the password.
Supported recovery
An ADMIN can create a credential, rotate an ACTIVE persistent credential, or permanently revoke a persistent credential. Store a newly shown password immediately because MyOwnProxy does not display it again. Update the application through its approved secret-management process. See Managing Proxy Credentials for the complete workflows.
Contact Support
Contact MyOwnProxy Support when a new connection still rejects a credential after its type, status, scope, expiry, current values, endpoint, and propagation interval have been checked. Send credential type and customer-visible identifiers only—never the password. See Contacting Support.