Autodiscovery failed. Unknown error while requesting .well-known.

[tbbkitty]

Describe the bug

When I use my own homeserver I get errors trying to sign in. .well-known works fine as I am federated. I am also unable to manually set the address and get "Unknown error", other homeservers work fine.

To Reproduce

Try to log in

What happened?

No response

Expected behavior

No response

Screenshots

No response

Version

0.11.3

Operating system

No response

Installation method

No response

Qt version

No response

C++ compiler

No response

Desktop Environment

No response

Did you use profiles?

• [ ] Profiles used?

Relevant log output

No response

Backtrace

No response

[zhenruyan]

me too

gitter.im

Autodiscovery failed. Unknown error while requesting .well-known.

[K4sum1]

I have this issue too. I moved my nheko install to another PC and tried copying appdata and whatever to keep the same session, but that didn't work either.

Edit: It fixed itself

[Just1Number]

In the last weeks I started getting this error, too. Possibly after updating to 0.12.0.

[2024-08-06 23:22:52.084] [net] [debug] hostname: chat.jwolf.me
[2024-08-06 23:23:22.294] [net] [error] Autodiscovery failed. Unknown error when requesting .well-known. (connection: Could not connect to server)

my .well-known seems to be fine, unless I'm missing something:

$ curl https://chat.jwolf.me/.well-known/matrix/server
{
    "m.server": "matrix.chat.jwolf.me:8448"
}

[deepbluev7]

@Just1Number, you sent your server .well-known, but Nheko is a client. But your server lookup works fine on my system, so probably you have other problems contacting that server. Which exact version of Nheko are you using (i.e. platform, how was it built, etc).

[Just1Number]

Arch Linux, Version 0.12.0, installed from the official arch repo. The issue persisted after a full reinstall. I now tried the flatpak version from flathub and it works without an issue. Seems to be a packaging issue.

[phreed]

I also get this error.

[2024-10-30 10:26:55.776] [net] [error] Autodiscovery failed. Unknown error when requesting .well-known. (connection: Could not resolve hostname)
[2024-10-30 10:26:56.478] [net] [error] Autodiscovery failed. Unknown error when requesting .well-known. (connection: SSL peer certificate or SSH remote key was not OK)

Which looks like my certificates are not ok. I am using nginx as my reverse proxy whose matrix config is in /etc/nginx/conf.d/matrix.conf.

However, when I verify the certificate from the command line it looks ok.

openssl verify /home/mcp/synapse/certs/matrix.mcp.mil/mil.mcp.coa.pem

/home/mcp/synapse/certs/matrix.mcp.mil/mil.mcp.coa.pem: OK

And the following also works:

curl https://mcp.mil/.well-known/matrix/client

{"m.homeserver": {"base_url": "https://matrix.mcp.mil"}}

However, when I make the request from firefox it claims

Your connection is not private
Attackers might be trying to steal your information from mcp.mil (for example, passwords, messages, or credit cards). [Learn more](chrome-error://chromewebdata/#)
NET::ERR_CERT_AUTHORITY_INVALID".

And only proceeds when I accept the risk.