Traffic grind to a halt after update to snowflake-proxy 2.13.1 (0d925e7f*)

Support
1

I noticed a new version was available with updates to the main snowflake.go source, after upgrading via git the traffic is down to virtually zero,it may have to do with something broken in the recent change. Running snowflake standalone, this happens on 2 separate installs. They both run unrestricted, one on the open internet (on a vps) and another behind the NAT but with an UDP port range forwarded.

Starting snowflake-proxy 2.13.1 (0d925e7f*)

2026/06/02 17:53:31 Using geoip file /usr/share/tor/geoip with checksum 4bdff9c5c91eb87685fb637e8cbcb1f5b0cab970
2026/06/02 17:53:31 Loaded 372677 entries into table
2026/06/02 17:53:31 Using geoip file /usr/share/tor/geoip6 with checksum 265f349d046819240b0a930ba50b2a4274c2b362
2026/06/02 17:53:31 Loaded 286480 entries into table
2026/06/02 15:53:31 Proxy starting
2026/06/02 15:53:32 NAT type: unrestricted
2026/06/02 16:53:31 In the last 1h0m0s, there were 4 completed successful connections. Traffic Relayed ↓ 54035 KB (15.01 KB/s), ↑ 8833 KB (2.45 KB/s).
2026/06/02 17:53:31 In the last 1h0m0s, there were 2 completed successful connections. Traffic Relayed ↓ 2456 KB (0.68 KB/s), ↑ 1225 KB (0.34 KB/s).
2026/06/02 18:53:31 In the last 1h0m0s, there were 0 completed successful connections. Traffic Relayed ↓ 0 KB (0.00 KB/s), ↑ 0 KB (0.00 KB/s).

Of course the upgrade may coincide with more general network issues and it has nothing to do with the code update, anyway I just wanted to mention this.

2

This has nothing to do with the update. I updated to 2.13.1 as soon as they suggested it.

As a matter of fact traffic jumped on May 26 2026 when Iran opened their internet again. See thread: Big increase in Snowflake proxy traffic recently - #3 by gus

My traffic is as it was at the end of 2025 and early 2026.

Yesterday 15,214,998 KB with at most 14 connections.

Edited later:
But mine says snowflake-proxy 2.13.1 (ff32ce45)
So you may be onto something.

3

Version 2.13.1 (0d925e7f*) is effectively v2.14.0 since the latest update only has updates to the Changelog and the version.go file.

I was using parameter -poll-interval 5s but the Changelog mentions changes to this:

Broker: Represent pollInterval in ms as time.Duration
Issue 25598: Proxy: Adjust poll interval to honour NextPoll field from broker

So I removed the -poll-interval parameter (trusting on defaults being good enough) and will see what happens.

4

That didn’t help, also removed the parameter that pointed to my own stun server without result. There’s typically a little traffic in the first hour, then traffic for subsequent hours drops to 0.

5

Do you keep logs?

I see many of these in the logs: Timed out waiting for client to open data channel
Thousands in the beginning of 2026 but down to hundreds now.

What I also see is many connections lasting less than 1 minute so that will not add much to the bandwidth that you see.

Here is a way, in real time, to tell how many connections there are:
netstat -anp | grep -i 'proxy' | grep -i -E -c '141.212.118.18|193.187.88.42'

The last line is the count. Maybe some smart Linux guy can find a way to pretty print it.

This is why I never rush to update stuff just to be at the latest whatever. I like the expression “if it ain’t broke, don’t fix it”. When I did the update to 2.13.1 as soon as it was suggested, it was because I thought it would help with ongoing blocking in RU. It made no difference I could measure.
You could go back to the version you had before.

6

I moved from the native go build to docker and now I have the

NAT type: unrestricted

again, there’s something fishy with the go source / install. I kept getting error 400 from the broker and NAT type strict.

7

NAT type strict is the wording used in version 2.14.1
Unrestricted is the wording previous to 2.14.1
See: Snowflake Standalone Server issue - multiple servers