You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The 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.
Installed 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:
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.
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.
Activity
github-actions commentedon May 20, 2026
The 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.
CerberusStyle commentedon Jun 1, 2026
No clue how this one works so i have done very little testing but install and update functions complete as expected.
TheDeliver8or commentedon Jun 25, 2026
Installed 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.
CrazyWolf13 commentedon Jun 26, 2026
@KernelSailor
KernelSailor commentedon Jun 30, 2026
Hi @CrazyWolf13 for pushing this topic also thanks for testing by @CerberusStyle and @TheDeliver8or
To generally see if the Service has connected succesfully run:
if you let snowflake run long enough you should see the outbound connections here:
Log Messages (which should appear I think at least every 30 seconds you should be able to see with:
I appended you some example logs for that one
snowflake-log-journalctl.txt
ludrewes commentedon Jul 6, 2026
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.
CerberusStyle commentedon Jul 6, 2026
You can test update with. (From the lxc)
github-actions commentedon Jul 10, 2026
A PR has been created for tor-snowflake: community-scripts/ProxmoxVE#15684
michelroegl-brunner commentedon Aug 10, 2026
Merged with #15684 in ProxmoxVE
github-actions commentedon Aug 10, 2026
Files deleted with PR #2163