Trouble logging into cloud dev environment backoffice
Hi everyone,
I'm working on migrating my locally-built Umbraco site to Umbraco Cloud. After encountering some database migration challenges, I deleted and recreated the dev environment.
Now I can't login to the cloud development backoffice. I'm getting this error:
Sorry, but we're having trouble signing you in.
We track these errors automatically, but if the problem persists feel free to contact us. In the meantime, please try again.
Correlation ID: 70b999e8-9cb4-4717-96b4-4fd338f1144b
Timestamp: 2024-12-24 00:45:10Z
AADB2C90272: The idtokenhint parameter has not been specified in the request. Please provide token and try again.
Any suggestions on how to resolve this login issue would be greatly appreciated.
Having no better idea, I made the questionable decision to simply delete and recreate the dev environment again. Much to my surprise - it actually worked!
I would delete the original post, but then it might be better to leave it in case anybody ever encounters this issue in the future.
Trouble logging into cloud dev environment backoffice
Hi everyone,
I'm working on migrating my locally-built Umbraco site to Umbraco Cloud. After encountering some database migration challenges, I deleted and recreated the dev environment.
Now I can't login to the cloud development backoffice. I'm getting this error:
Sorry, but we're having trouble signing you in. We track these errors automatically, but if the problem persists feel free to contact us. In the meantime, please try again. Correlation ID: 70b999e8-9cb4-4717-96b4-4fd338f1144b Timestamp: 2024-12-24 00:45:10Z AADB2C90272: The idtokenhint parameter has not been specified in the request. Please provide token and try again.
Any suggestions on how to resolve this login issue would be greatly appreciated.
Thanks in advance!
Having no better idea, I made the questionable decision to simply delete and recreate the dev environment again. Much to my surprise - it actually worked! I would delete the original post, but then it might be better to leave it in case anybody ever encounters this issue in the future.
is working on a reply...