Element does not proxy calls to element.io and other things

[nunuvin]

Steps to reproduce

1. Where are you starting? What can you see? Block all outbound but the proxy, element will fail to login on boot.
   proxy is 2 step:
   --proxy-server=socks5://127.0.0.1:1080 --no-update
   then I have a proxy program running on 1080 port which redirects to the actual proxy ip

Outcome

What did you expect?

I expected element to load even if everything is offline but not connect me to the server. But if outbound calls are blocked by network, even with proxy given, you do not get anywhere. This makes it really easy to block element.

I am unable to view the logs locally which is also a problem as it seems /rageshake and other features aim at sending logs online not make them easy to locally debug...

What happened instead?

blocking outbound except proxy basically bricks the element making it extremely easy to block. Furthermore it makes element dependent on 3rd party stuff...

Operating system

Windows

Application version

Element version: 1.12.6 Crypto version: Rust SDK 0.14.0 (c3b7918), Vodozemac 0.9.0

How did you install the app?

I think official site

Homeserver

non public matrix synapse

Will you send logs?

Yes

[t3chguy]

The proxy-server argument isn't added by us but Electron/Chromium and we cannot control what is and what is not proxied via it.

[nunuvin]

I see thats a bummer. When element launches it does require getting packages from the element.io is there a way to bypass that, so I can just do the calls to my selfhosted server without reaching out to other locations?

[t3chguy]

The URIs are all configurable in config.json - you can also disable auto-update (packages.element.io) via parameter --no-update