Account recovery request #6228
Comments
|
Hi @swryan, Please contact support@pypi.org with an email address that you would like your account to be associated with and please reference this link (#6228). We will proceed from there. Thanks! |
|
Hi @swryan, I have updated the primary email address on the test.pypi account. Your 2FA has been reset and a password reset has been issued. You should be able to regain access to your account after completing the password reset. Let us know if you have any more issues. Thanks. |
|
wilco thanks!
…On Wed, May 21, 2025 at 4:31 PM thespibrain ***@***.***> wrote:
*Thespi-Brain* left a comment (pypi/support#6228)
<#6228 (comment)>
Hi @swryan <https://github.com/swryan>,
I have updated the primary email address on the test.pypi account. Your
2FA has been reset and a password reset has been issued. You should be able
to regain access to your account after completing the password reset. Let
us know if you have any more issues. Thanks.
—
Reply to this email directly, view it on GitHub
<#6228 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAGXGFSO676YP4HOVPWZF3D27TPCTAVCNFSM6AAAAAB4KL5DF6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDQOJZGE2TSNBRGE>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
|
I was unable to reset the password, it says the e-mail is unverified:
**[TestPyPI] Password reset requested for unverified email**
```
Someone, perhaps you, has made a password reset request for a PyPI account
associated with this email address.
However, the email used to make this request is not verified. Your email
address must be verified before you can use it to reset your password.
If you have another verified email address associated with your PyPI
account, try that instead.
If you cannot use another verified email, follow account recovery steps
<https://test.pypi.org/help/#account-recovery> for your PyPI account.
Read more about verified emails.
<https://test.pypi.org/help/#verified-email>
If you did not make this request, you can safely ignore this email.
```
…On Wed, May 21, 2025 at 4:31 PM thespibrain ***@***.***> wrote:
*Thespi-Brain* left a comment (pypi/support#6228)
<#6228 (comment)>
Hi @swryan <https://github.com/swryan>,
I have updated the primary email address on the test.pypi account. Your
2FA has been reset and a password reset has been issued. You should be able
to regain access to your account after completing the password reset. Let
us know if you have any more issues. Thanks.
—
Reply to this email directly, view it on GitHub
<#6228 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAGXGFSO676YP4HOVPWZF3D27TPCTAVCNFSM6AAAAAB4KL5DF6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDQOJZGE2TSNBRGE>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
|
@Thespi-Brain see above.. the e-mail address has been changed but it cannot be used to reset the password since it is not verified, therefore we are still unable to access the account. Are you able to flag the e-mail address as verified, or provide some other mechanism to recover the account? If nothing else, maybe this TestPyPi account can be deleted and we can recreate it? I'm guessing this would leave orphan projects that would also need to be deleted... Do you need me to open a new issue since this one has been closed? |
|
Hi @swryan, I did some more troubleshooting and you should be able to log in an reset your password. Thanks for your patience. |
|
Success! Thank you very much... Recovery codes generated and 2FA configured. I appreciate your help with this @Thespi-Brain |
Uh oh!
There was an error while loading. Please reload this page.
PyPI Username
openmdao
Reason for request
Note this is for the
openmdaoaccount on the Test PyPI instance.. Everything is fine on the production service.Lost access to email address associated with the Test PyPI account (not even sure what it was). If we could get that account reset to use the same e-mails as the production PyPI account that would be great.
Recovery Codes
Code of Conduct
Acknowledgement
The text was updated successfully, but these errors were encountered: