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

AutoDiscovery not working correctly after update #3039

Closed
CptWonderful opened this issue Oct 13, 2019 · 3 comments
Closed

AutoDiscovery not working correctly after update #3039

CptWonderful opened this issue Oct 13, 2019 · 3 comments

Comments

@CptWonderful
Copy link

CptWonderful commented Oct 13, 2019

Hey guys,

after one of the last upgrades my AutoDiscovery is not working anymore (accounts which were setup before seem to be working).

https://testconnectivity.microsoft.com has the following output:

testconnectivity_output

Autodiscover Log in the webinterface:

Autodiscover_log

When I'm trying to add it via outlook android client, it works, but no emails are synched. Furthermore the additional settings are missing after the setup - Differs from the behavior before the update.
IMAP is working fine.

Any other logs I can provide?

@andryyy
Copy link
Contributor

andryyy commented Oct 13, 2019

Autodiscover.php has not been touched since 9f0be1d on 11 Oct 2018.

MS Connectivity tester never worked with SOGo.

So no, the update did not break anything regarding autodiscover.

Please don't delete the whole issue template next time.

The realm https://domain.de:443/autodiscover/blabla is also not valid. The correct realm is autodiscover.domain.de/autodiscover/blabla. :)

It returtned "WWW-Authenticate: Basic realm="Zugriff verweigert"" etc. ... that's not a string we return, too.

I don't know if you are using a reverse proxy etc., but I think you should join the Telegram group for this kind of support.

@andryyy
Copy link
Contributor

andryyy commented Oct 13, 2019

For some crazy reason it actually works today. :|

image

@stale
Copy link

stale bot commented Dec 12, 2019

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the dunno label Dec 12, 2019
@stale stale bot closed this as completed Dec 19, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants