Describe the bug
This is not a bug report but a feature request. Thanks for the work in creating desktop clients (https://tutanota.com/blog/posts/desktop-clients), but as far as I could tell there's no simple way to make the client use a SOCKS5 proxy to connect to the Internet, e.g to the default address of 127.0.0.1:9150 when using Tor. Ideally the desktop client would notice that there is such a proxy available and prompt the user whether to use it by default.
To Reproduce
Steps to reproduce the behavior:
./tutanota-desktop-linux.AppImage version 3.47.4 when routing all traffic via TorCould not reach server, looks like you are offline. Please try again later.Expected behavior
Client can reach servers and log in, either with zero configuration for the user running SOCKS5 proxy on 127.0.0.1:9150, or after specifying a command line argument to explicitly state that SOCKS5 should be used and the address to use to reach the proxy.
Desktop (please complete the following information):
Hey
We ask users to not leave feature requests here
We will revisit it when we have more time, for now I close it to be consistent with the rules.
you can start with that:
/opt/tutanota-desktop-linux/tutanota-desktop-linux.AppImage --proxy-server="socks://localhost:9050"
but it would be easier with a function implemented on the application.
I have found this guide useful.
TL;DR the option --proxy-server="socks5://127.0.0.1:port" has worked for me for Privoxy+Tor solution on Windows. While localhost:port won't work without the extra --host-resolver-rules option.