Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

OneDrive cannot be accessed anymore #281

Closed
Angel0fDarkness opened this issue May 19, 2021 · 21 comments
Closed

OneDrive cannot be accessed anymore #281

Angel0fDarkness opened this issue May 19, 2021 · 21 comments
Labels

Comments

@Angel0fDarkness
Copy link

I have updated to v2.0 today and afterwards was unable to connect to OneDrive again.
It opens the authentication website, asks for permissions and correctly shows the success page at the end "Received verification code. You may now close this window."
But in KeePass, an error window pops up:
KeeAnywhere_Onedrive_error
If the blackened IDs are important, I could share them in private.

Best Regards,
Tobias

@Kyrodan
Copy link
Owner

Kyrodan commented May 19, 2021

I cannot find an issue with that. Is it maybe a temporary thing?
Can you delete your OneDrive Account and recreate it?
Do you use a proxy?

@Kyrodan
Copy link
Owner

Kyrodan commented May 19, 2021

I cannot find an issue with that. Is it maybe a temporary thing?

Okay, immediately after writing I can see the same problem now. Will work on it.

@Angel0fDarkness
Copy link
Author

I have tried with "Check" first, but afterwards completely deleted and reset the account.
Currently I am working behind a VPN but without proxy, could try it without VPN in the evening..

Thanks :)

@flotux2
Copy link

flotux2 commented May 19, 2021

I'm getting the same error message when trying to re-authenticate after upgrading to the new version 2.0.0.

I also removed my OneDrive account from KeeAnywhere and re-added it. But I still get the same error message. :-(

@Kyrodan
Copy link
Owner

Kyrodan commented May 19, 2021

This is weired. Yesterday I checked everything and everything was fine :-/

@Kyrodan
Copy link
Owner

Kyrodan commented May 19, 2021

@Angel0fDarkness @flotux2
Could you please try this build, I did a small change which works for me now:
KeeAnywhere-2.0.1.plgx.zip

@Kyrodan Kyrodan added the bug label May 19, 2021
@StevenTN615
Copy link

I just updated the plugin to 2.0.0 and also received the same error. Tried your 2.0.1 plugin and it connected.

@Snoobz
Copy link

Snoobz commented May 19, 2021

Hello, the new version 2.0.1 is not working for me! After I login into my OneDrive account, it redirects my Mozilla browser to this URL : http://127.0.0.1:49215/

Which is obviously not right. Any help please? I had to revert back to 1.6.0

Thanks.

@flotux2
Copy link

flotux2 commented May 19, 2021

With version 2.0.1 re-authentication of OneDrive failed. After removing and adding the OneDrive account access now works again!

grafik

I could use my Google Drive account directly without the need to re-authenticate.
I could use my Dropbox account after re-authentication. I didn't need to remove and re-add it!

@daecarne
Copy link

Hi! same here. I was get the same error when I updated to 2.0.0 version. I just updated to 2.0.1 version and it's fine now. Anyway, I needed to remove my onedrive account before and re-added after.

@Snoobz
Copy link

Snoobz commented May 19, 2021

Well, this is weird but I solved my problem...
I reinstalled the 2.0.1 version, removed my OneDrive account, re-added it after the loggin process my browser still got redirected to this weird URL : http://127.0.0.1:49215/

Then going back to KeePass I clicked on the "Check" button and it said "Connection succeeded".

I don't know if you can "solve" this weird redirection after the loggin process (I don't know why it looks like I'm the only one facing this issue) but anyway it works now.

Thanks for the quick update.

@Angel0fDarkness
Copy link
Author

@Kyrodan
I have just tested the same on my other PC, similar problem appeared with 2.0.0.
With 2.0.1 it was fixed and I could re-connect to OneDrive.

However, on this PC I am seeing a error when the page is loaded after OneDrive authentication (still in the browser) where I would expect to see the success message "Received verification code. You may now close this window.".

@Snoobz
I think this redirect is perfectly fine and the way this authentication works.

@lsaudon
Copy link

lsaudon commented May 19, 2021

2.0.1 fix for me.

@Uwe11
Copy link

Uwe11 commented May 19, 2021

same here. No connection with 2.0.0, but works again with 2.0.1
Thnaks for quick reaction!

@SoerenEilenberger
Copy link

Hi, I just came here after I had the same problem and then tried 2.0.1. Unfortunately, it claims it's a different account now instead of the "code line error message". I am sure I am using the right account. I am using a second factor with MSAuth-App on my OneDrive, maybe this leads to it?

@SoerenEilenberger
Copy link

It does work to create the account from scratch again.

@Kyrodan
Copy link
Owner

Kyrodan commented May 20, 2021

... it redirects my Mozilla browser to this URL : http://127.0.0.1:49215/
Which is obviously not right. Any help please?

This is correct. I should add a migration guide for Version 2.x to documentation to clarify this.

@Kyrodan
Copy link
Owner

Kyrodan commented May 20, 2021

@Angel0fDarkness

However, on this PC I am seeing a error when the page is loaded after OneDrive authentication (still in the browser) where I would expect to see the success message "Received verification code. You may now close this window.".

What is the exact message? Or do you have a screenshot of that?

@Angel0fDarkness
Copy link
Author

I cannot reproduce it on my laptop, it is working fine here.
Yesterday, it was showing the "Page could not be loaded" general error in Firefox as if the page wouldn't exist.
But authentication of the OneDrive account worked in both cases.

@gbaroni-csw
Copy link

For me, with OneDrive, version 2.0.1 worked by deleting the account and recreating it from scratch.

@Kyrodan
Copy link
Owner

Kyrodan commented May 21, 2021

I released v2.0.2 a few minutes ago, that should fix this issue.
Please read "notworthy" in changelog.
So this can be closed now?

If problems are still present in v2.0.2 then please open a new issue, this is a liitle bit confusing now (due to the many comments)

@Kyrodan Kyrodan closed this as completed May 21, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

10 participants