We have installed a snowflake proxy on a standalone server using docker-compose as per the instructions on the tor website (Tor Project | Standalone Snowflake proxy).
Our docker-compose.yl looks like the attached screenshot. We have added command:[“-capacity”, “300”] to limit clients to 300
Two questions:
1- Is it normal for PORTS to be empty under the output of the docker-compose ps command
2- We can’t seem to read the logs at all. we have tried both the following commands:
docker-compose logs snowflake-proxy
docker logs snowflake-proxy
Both commands do not return anything.
When we check the server traffic graphs, nothing seems to be happening.
3- What is the right way to include two custom options in the yml file , like limiting clients to 300 and specifying desired filename for the logs. would it be
command: [“-capacity” , “300” , “-log” , “snowflake-proxy.log”]
Using two separate command lines in the yml file, seems to force docker to only use the last line and discard the first one.
Followup: We have rebuilt the docker container (after removing it) , and now docker-compose logs snowflake-proxy spits out the following error:
ortc ERROR: 2022/09/26 18:07:42 Failed to accept data channel: failed to send ChannelOpen ACK: sending payload data in non-established state: state=Closed
We would appreciate any feedback on this error as well.
Two questions:
1- Is it normal for PORTS to be empty under the output of the docker-compose ps command
Yes this is normal, the PORTS field in this table is referring to the ports published by the container to the host operating system. By default, the snowflake proxy container uses the host network directly and so doesn’t need this feature at all. But even more relevant, Snowflake proxies are designed to work behind NATs so there is no need to specifically expose ports to the outside at all.
2- We can’t seem to read the logs at all. we have tried both the following commands:
ortc ERROR: 2022/09/26 18:07:42 Failed to accept data channel: failed to send ChannelOpen ACK: sending payload data in non-established state: state=Closed
This error is safe to ignore: I’m not sure of the direct cause, but it only corresponds to one proxy connection and does not indicate a problem with the proxy as a whole. Not all proxies are compatible with all clients, this could be a side effect of that.
