bug: Models doesnt download

[x0tiago0-source]

Version: v2.0.35

Describe the Bug

Models don't download

Steps to Reproduce

1. Go the page models
2. Select a Model to donwload and click on download
3. The progress tab appears but the download doesnt start

Screenshots / Logs

app.log

Operating System

• MacOS
• [ X] Windows
• Linux

[Vect0rM]

Thank you for the report, and especially for attaching app.log — the answer was in it, and we would not have found it from the screenshots alone.

The downloads are not starting because every request is being sent through a proxy that refuses the connection:

[app_lib::core::downloads::helpers][INFO] Using proxy http://192.168.1.218:1234 for URL https://huggingface.co/...
[app_lib::core::downloads::helpers][WARN] Preflight HEAD ... failed: tcp connect error: ... (os error 10061)

os error 10061 is Windows for "the target machine actively refused it". That address comes from Settings → HTTPS Proxy. Port 1234 is LM Studio's default local-server port, so our guess is that it was entered there as a server address rather than a proxy. Immediate fix on your side: open Settings → HTTPS Proxy and either turn the proxy off, or correct the address. Downloads should start straight away.

That is your half. The other half is ours, and it is the real bug here: the app gave you no way to find that out.

• The progress card sat at 0%. When the preflight request cannot reach the host, the download reports an unknown total size, and the percentage was computed as 0/0 — NaN, which rendered as an empty bar for the whole attempt.
• Nothing was reported for over a minute. Both retry ladders (five attempts each, backing off 1→16s) ran in complete silence, so a refused connection looked exactly like a download that had not started yet.
• When it finally gave up, the message was the generic "Download Failed", auto-dismissed in a few seconds, and never mentioned the proxy.
• Internally we had also been misfiling it: any error containing os error was classified as a disk fault, so a pure network refusal was recorded as a disk problem and fell through to that generic message.

All four are fixed in the next release. The card now says "Connecting…" and then "Connection failed, retrying (2/5)…" instead of a frozen "Preparing"; the percentage is guarded; a connection failure is classified as network (or proxy) rather than disk; and when a proxy is configured you get a 30-second message naming the proxy address with an Open proxy settings button.

We also added a Test connection button next to the proxy URL in Settings, which actually sends a request through the proxy and tells you whether it is reachable, refusing, or rejecting your credentials. Nothing in the app had ever talked to the address typed there — it was only checked for valid syntax.

Your #289 has the same root cause; there is a separate note on it.

We truly appreciate your help in making Atomic Chat better!