You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Please use the 👍 reaction to show that you want to have the same feature implemented.
Please don't comment if you have no relevant information to add. It's just extra noise for everyone subscribed to this issue.
Subscribe to receive notifications on status change and new comments.
Feature description
Nextcloud desktop application does not report why checking for an upgrade fails. It would be nice if it would note why it could not check for upgrades. Was it a proxy problem, server down, server not reachable, or any other possible cause.
The text was updated successfully, but these errors were encountered:
For the most part, the answer is: "Any of the above". 😄
It's just a a general "timeout while trying to check for updates".
Other than perhaps the proxy (assuming you mean an HTTP Proxy like in an enterprise environment, not a reverse proxy) there's no way for us to know much more or report much more.
joshtrichards
changed the title
Nextcloud Desktop Clients only says "Could not check for updates, but does not provide why.
Says "Could not check for updates" but does not report why
Aug 12, 2024
This error appear on MacOS clients since v 3.14.1 and is still present on 3.13.3 while it had worked before. Any other kind of internet activity works flawless and firewall rules do not prohibit traffic to NC servers.
How to use GitHub
Feature description
Nextcloud desktop application does not report why checking for an upgrade fails. It would be nice if it would note why it could not check for upgrades. Was it a proxy problem, server down, server not reachable, or any other possible cause.
The text was updated successfully, but these errors were encountered: