element-hq / element-hq/element-web

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

Open
#32,001 4 comments 0 reactions 0 assignees View on GitHub
A-Electron O-Frequent O-Occasional S-Major T-Defect X-Needs-Info Z-Upstream
Dominant language
TypeScript
Stars
13.5k
Forks
2.8k
PR merge metrics
PR metrics pending

Description

### 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

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.