Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

BROKEN app after clicking the Pop-up to UPDATE app. "Connectivity to the server has been lost." #22330

Closed
jittygitty opened this issue May 24, 2022 · 3 comments
Labels

Comments

@jittygitty
Copy link

Steps to reproduce

  1. Where are you starting? What can you see?
    Connectivity to the server has been lost.
    Started right after clicked pop-up to UPDATE app.
    Currently it says:
    Element version: 1.10.13
    Olm version: 3.2.8

  2. What do you click?
    Messages Fail to send with red circle with exclamation mark, and message displayed in red:
    "Connectivity to the server has been lost."

Outcome

What did you expect?

To have it work as it did before the update, preferably BETTER because I clicked on UPDATE because already it was buggy in some ways, like I click on voice or video call in a DM direct-message 2 person chat and nothing would happen. Seems like it may have been that only one participant was Admin and only admin could initiate, but no helpful errors were given, just nothing happened on clicking voice call or video.

What happened instead?

But before update at least messaging was working fine. After clicking update, nothing works.

Operating system

Windows 10

Application version

No response

How did you install the app?

No response

Homeserver

No response

Will you send logs?

Yes

@jittygitty
Copy link
Author

jittygitty commented May 25, 2022

I discovered the issue, it seems like the "background update" employed by Element Desktop does not play well with Application Firewalls and so upon re-installation it did not initiate re-quest to re-authorize network access.

@t3chguy
Copy link
Member

t3chguy commented May 25, 2022

it did not initiate re-quest to re-authorize network access

Software doesn't "request" network access, it just makes a request and firewalls can choose to allow, block, or ask. In your case it seems like the firewall defaulted to block.

Related #14788

@dbkr
Copy link
Member

dbkr commented May 25, 2022

I think the related bug covers everything here, so I'm going to close this one in favour of #14788.

@dbkr dbkr closed this as completed May 25, 2022
@turt2live turt2live closed this as not planned Won't fix, can't repro, duplicate, stale May 27, 2022
@element-hq element-hq locked as resolved and limited conversation to collaborators May 27, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

4 participants