nheko icon indicating copy to clipboard operation
nheko copied to clipboard

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

Open tbbkitty opened this issue 1 year ago • 5 comments

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

tbbkitty avatar Dec 08 '23 01:12 tbbkitty

me too

gitter.im

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

zhenruyan avatar Dec 24 '23 17:12 zhenruyan

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 ScreenShot_20240102231533

K4sum1 avatar Jan 03 '24 07:01 K4sum1

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"
}

Just1Number avatar Aug 06 '24 21:08 Just1Number

@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).

deepbluev7 avatar Aug 08 '24 16:08 deepbluev7

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.

Just1Number avatar Aug 10 '24 14:08 Just1Number