[Bug]: Unable to Login

### ⚠️ Before submitting, please verify the following: ⚠️

- [x] This is a **bug**, not a question or a configuration issue.
- [x] This issue is **not** already reported on Github (I've searched it).
- [x] Nextcloud Server and Desktop Client are **up to date**. See [Server Maintenance and Release Schedule](https://github.com/nextcloud/server/wiki/Maintenance-and-Release-Schedule) and [Desktop Releases](https://nextcloud.com/install/#install-clients) for supported versions.
- [x] I agree to follow Nextcloud's [Code of Conduct](https://nextcloud.com/contribute/code-of-conduct/)

### Bug description

Cannot login to server from Desktop app

### Steps to reproduce

• Select account, click Log in, absolutely nothing happens.
• Under Settings it says "Signed out from [Server] as [Name].
• If I click Log in, it says No Nextcloud connection configured.
• After a few moments it changes back to Signed out from [Server] as [Name].

### Expected behavior

Login to the Nextcloud server, ask for username and password, or display some sort of error.

### Which files are affected by this bug

all files

### Operating system

Windows

### Which version of the operating system you are running.

Windows 11

### Package

Official Linux AppImage

### Nextcloud Server version

31.0.6

### Nextcloud Desktop Client version

4.0

### Is this bug present after an update or on a fresh install?

Updated to a major version (ex. 3.16.3 to 3.17.0)

### Are you using the Nextcloud Server Encryption module?

Encryption is Enabled

### Are you using an external user-backend?

- [ ] Default internal user-backend
- [ ] LDAP/ Active Directory
- [ ] SSO - SAML
- [ ] Other

### Nextcloud Server logs

```shell

```

### Additional info

Looking at the web UI it hasn't synced for 2 months. Delving into the Desktop logs I can see the self-signed certificate is rejected. Now I see issue mentioned 8654. Disabled HTST and the client works as expected.

The end user had no idea it stopped syncing let alone stopped connecting. Finding or reading APPDATA logs and deleting cache outside the app is going to be beyond their capability.