Repository navigation
tor-snowflake #1570
Description
Activity
github-actions commented
on May 20, 2026 on May 20, 2026 – with GitHub ActionsContributorMore actionsThe tor-snowflake script is ready for testing:
bash -c "$(curl -fsSL https://github.com/community-scripts/ProxmoxVED/raw/main/ct/tor-snowflake.sh)"
Note: This is not in the official repo yet—it's just a dev version! After merging into ProxmoxVE, it will need to be recreated.No clue how this one works so i have done very little testing but install and update functions complete as expected.
Reacted by TobiasInstalled without issue (although I did get a warning that nesting may be required). Is there a way to verify that it is connected/available to be connected to as a snowflake proxy? I don't see a port bound for a web UI or anything on those lines.
Hi @CrazyWolf13 for pushing this topic also thanks for testing by @CerberusStyle and @TheDeliver8or
To generally see if the Service has connected succesfully run:root@tor-snowflake:~# systemctl status snowflake-proxy.service ● snowflake-proxy.service - Snowflake Proxy Service Loaded: loaded (/etc/systemd/system/snowflake-proxy.service; enabled; preset: enabled) Active: active (running) since Tue 2026-06-30 18:32:51 CEST; 35s ago <--some Stuff left out --> Jun 30 18:33:16 tor-snowflake snowflake-proxy[8355]: 2026/06/30 16:33:16 Connected to relay: wss://snowflake.torproject.net/ Jun 30 18:33:26 tor-snowflake snowflake-proxy[8355]: 2026/06/30 16:33:26 Poll interval set to 30s root@tor-snowflake:~#
if you let snowflake run long enough you should see the outbound connections here:
root@tor-snowflake:~# ss -tpn | grep snowflake ESTAB 0 0 172.16.10.66:50182 <redacted---ipv4>:443 users:(("snowflake-proxy",pid=462,fd=22)) ESTAB 0 0 [2001:<redacted---ipv6>]:43274 [2a00:<redacted---ipv6>]:443 users:(("snowflake-proxy",pid=462,fd=3)) ESTAB 0 0 [2001:<redacted---ipv6>]:38764 [2a0c:<redacted---ipv6>]:443 users:(("snowflake-proxy",pid=462,fd=19)) ESTAB 0 0 [2001:<redacted---ipv6>]:51872 [2a0c:<redacted---ipv6>]:443 users:(("snowflake-proxy",pid=462,fd=16)) ESTAB 0 0 [2001:<redacted---ipv6>]:53014 [2a0c:<redacted---ipv6>]:443 users:(("snowflake-proxy",pid=462,fd=10)) ESTAB 0 0 [2001:<redacted---ipv6>]:54658 [2a0c:<redacted---ipv6>]:443 users:(("snowflake-proxy",pid=462,fd=12)) ESTAB 0 0 [2001:<redacted---ipv6>]:55446 [2a0c:<redacted---ipv6>]:443 users:(("snowflake-proxy",pid=462,fd=13)) ESTAB 0 0 [2001:<redacted---ipv6>]:58910 [2a0c:<redacted---ipv6>]:443 users:(("snowflake-proxy",pid=462,fd=8)) root@tor-snowflake:~#
Log Messages (which should appear I think at least every 30 seconds you should be able to see with:
journalctl -u snowflake-proxy -f
I appended you some example logs for that one
Reacted by CerberusStyle, Tobias and Lucas DrewesReacted by TheDeliver8orInstallation completed as expected, got the same warning about nesting maybe being required as @TheDeliver8or though. Service seems to run fine, circuits are being openend and closed as expected. No errors in the log so far. Update function appears to be working, though no actual update was available at the time of testing.
Installation completed as expected, got the same warning about nesting maybe being required as @TheDeliver8or though. Service seems to run fine, circuits are being openend and closed as expected. No errors in the log so far. Update function appears to be working, though no actual update was available at the time of testing.
You can test update with. (From the lxc)
cd.. ls -Xal rm .<app name> updateReacted by Tobias and Lucas Drewesgithub-actions commented
on Jul 10, 2026 on Jul 10, 2026 – with GitHub ActionsContributorMore actionsA PR has been created for tor-snowflake: community-scripts/ProxmoxVE#15684
Merged with #15684 in ProxmoxVE
github-actions commented
on Aug 10, 2026 on Aug 10, 2026 – with GitHub ActionsContributorMore actionsFiles deleted with PR #2163
Name of the Script
tor-snowflake
Script Type
CT (LXC Container)
📋 Script Details
tor-snowflake