During migration, the website sends a OTP code. The account I am using is a Legacy account. When it sends the post request to the api to check if a OTP can be sent it returns a 403. Not sure exactly why, I tested using various Site-Referrer status (strict, origin) and across Firefox, Chrome, Safari, IE, Private mode, and on Mac and windows to no solution.
[media]Attachments
Comments 3
I do remember the email. My email is also currently a Microsoft account that had another legacy account migrated to Mojang account, and then had that account's email switched to the same email that is used for the account I'm having the issue with above. I can provide the account names if it's helpful. However, I guess this falls under an account issue now. I don't have financial records from over a decade ago so the accounts a wash. Thanks for the quick response, I was a little confused why it suggested invalid username on an email otp, but it makes sense now.
When sending an OTP for legacy accounts you need to provide the e-mail for the account. If the provided e-mail doesn't match the registered e-mail you get the response above.
If you don't remember the e-mail you need to contact Minecraft Support