Snowflake proxy (browser extension) isn't working for me anymore - "websocket-relay timed out connecting"

I was using the Brave Snowflake proxy extension (on Windows 11; Poland) and it was working normally for a few days. Then it just started disconnecting (turning purple) 1-3 seconds after any connection started, indicated by the icon turning green.

As I said, this wasn’t happening at first. After it started, I tried checking if the problem would occur on a completely different computer - Windows 11, Firefox. I even connected it to the mobile internet via the hotspot on my phone (with the same ISP though). It still had the exact same issue.

I checked the logs and the first connection always resulted in some trouble with ICE and TURN. However, logs from each new connection were first saying “WebRTC DataChannel opened!”, indicating something actually went right, but then saying “websocket-relay timed out connecting” and more errors.

I’m going to attach the screenshots with the first connection and the next 2 connections. What’s wrong with it?

I’m seeing the same kind of thing except I see Timed out waiting for client to open data channel (2371 times today) but I’m running a standalone unrestricted Snowflake proxy.

2025/08/05 03:58:24 Received Offer From Broker:
v=0
o=- 9058226039021454447 1754366303 IN IP4 0.0.0.0
s=-
t=0 0
a=msid-semantic:WMS*
a=fingerprint:sha-256 67:6A:A6:46:5C:D2:9B:C9:7A:98:F4:8C:EC:B7:F2:03:B9:AA:60:63:35:25:1D:40:05:0C:2F:37:F4:BD:9E:01
a=extmap-allow-mixed
a=group:BUNDLE 0
m=application 9 UDP/DTLS/SCTP webrtc-datachannel
c=IN IP4 0.0.0.0
a=setup:actpass
a=mid:0
a=sendrecv
a=sctp-port:5000
a=max-message-size:1073741823
a=ice-ufrag:KZNSbdfsctSdQQZk
a=ice-pwd:sdBtddnOCYVqutizlBVMjeIhSztLesyY
a=candidate:503074901 1 udp 1694498815 n.207.20.n 23167 typ srflx raddr 0.0.0.0 rport 39698 ufrag KZNSbdfsctSdQQZk
……many more like this…..
a=end-of-candidates

2025/08/05 03:58:24 Generating answer…
2025/08/05 03:58:24 Answer:

I’m also receiving: error dialing relay: wss://02.snowflake.torproject.net/?client_ip=n.15.38.n = dial tcp 141.212.118.18:443: i/o timeout
Have received 3796 today

I have not seen that many 141.212.118.18:443: i/o timeout before.

I suspect this is happening to many others but people are not looking at logs or do not produce them.

Something must be wrong with 02.snowflake.

I’ve been seeing these Timed out waiting for client to open data channel for quite some time now. They go up then go down.

Do you think it’s a global issue with Snowflake then? That would be weird because I haven’t seen any official announcements about the problems.

Should I try asking other people in my area, but with different ISPs to try running the browser extension proxy and see how it goes? Or does it not make much sense?

It does make sense. The more info the better. Would be interesting to see data from other people and different ISPs.

The error dialing relay: wss://02.snowflake has to be a problem with that server. We have no control and it’s only recent. I keep all my logs and it’s only recently that tons of them are happening now. 3949 in today’s log (really yesterday’s data) and 2391 for Timed out waiting for client to open data channel. The highest I’ve seen yet. That just could be the censors getting better at blocking user. I looked at the IPs and mostly RU by far.

The snowflake-02 bridge is down. I believe this is the source of the problem.

We are working on recovering the bridge: snowflake-02 bridge is down (#40475) · Issues · The Tor Project / Anti-censorship / Pluggable Transports / Snowflake · GitLab

3 Likes

This is good to know that it is being worked on. Thanks for the response.

I don’t know if it’s still useful but I just want to let know that I asked 2 other people (both with different ISPs, and one person from a different country) to check if the snowflake would work and both were getting the same errors.

A “snowflake bridge” is just like a hidden bridge / Tor entry node, where a user connects after passing through my proxy, right?

Is there anything else I do about that (maybe reconfigure snowflake to connect with a different bridge, if it exists) or just wait until it’s fixed?

Thanks in advance for response.

Looks like this problem is fixed.

It is now 2025/08/13 19:58:53 UTC and my last occurrence was at 2025/08/13 14:28:10 UTC