![]() ![]() ![]() For now, it works again, I will report back if I am able to gather some more information. After reading this thread, I just checked, and the old app password indeed works again after disabling TOTP, and also after re-enabling TOTP (I guess only for some time, however). What helps (for some time), is creating a new app password. TBSync/Thunderbird keeps asking about the password and cannot connect with the app password anymore. At some point, often after (re-)booting things stop working-although, I think it might happen after a certain amount of time. I will get back to you, as soon as I see the error again.īasically, what happens: With TOTP activated and a new app password created, everything works fine at first. I am pretty sure, I have also seen the errors reported above, in #404 (comment). This is my setup in Linux now, however, the same thing also happens under Windows. App passwords work for DAVDroid, but not very long with TBSync (currently 2.12) and the Provider for CalDAV & CardDAV addon (currently 1.12) in Thunderbird 68.12 (under Archlinux). Thunderbird Master password to protect Start Thunderbird and click in the menu bar on Extras. ![]() This is rarely an option, which makes it difficult for us to help beyond asking you to try different things.Same here! Currently, I am running Nextcloud 19.0.3, but the issue was there for some time now. For us to help you overcome this, we would need to have valid credentials to login to your Exchange server (which could be a test account). The ExQuilla logs will have entries like " INFO html error " and little else of value. Unfortunately if authentication fails, there is little that we can do to help you. Choose "Microsoft Exchange Web Services Connectivity Tests/ Synchronization, Notification, Availability, and Automatic Replies" and make sure that you can connect using the username and password that you expect. You can also confirm that the username and password works with Exchange Web Services using Microsoft's connectivity test site (). In almost all cases, the same information should also allow ExQuilla to connect successfully. If you can get that, it means that you have successfully connected to the Exchange Server. It should ask you for a name and password, and if successful show you a page of XML-language information that starts with: One test that you can do of these pieces of information, independent of ExQuilla, is enter the EWS URL into a browser. Try clearing the password there and restarting Thunderbird, which will force a new request to enter a password. You may view your existing username and password in the password manager (Tools/Options/Security/Passwords/Saved Passwords) under the entry for your EWS URL. 10:30:42 DEBUG contentType: application/xml status: 200 statusText: OK authCount: 0 10:30:42 DEBUG transferComplete to URL: 10:30:42 DEBUG httpSoapTransportCompletion handleEvent type load username rkent%40mesquilla%2Ecom Here is an example from my log file of a successful connection with EWS URL "", username and blank domain: 10:30:42 DEBUG asyncCall uri user domain null If your account used to work, there may still be entries in your ExQuilla log file that shows the EWS URL, username, and domain that was used for a successful login. If the username resembles an email address, then usually the domain is blank. The first three items may be viewed in the account settings (Tools/Account Settings/(your Exchange account)/Microsoft Exchange Server). If ExQuilla is claiming that your password is incorrect, there are a few things that you can do to test it.Īuthentication in ExQuilla relies on four pieces of information being correct: 1) your EWS URL, 2) your user name, 3) your domain, and 4) your password. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |