Cannot configure proxy on Windows

Support
1

I’m running syncthing v0.14.44 on Windows 10.

λ syncthing -version

syncthing v0.14.44 “Dysprosium Dragonfly” (go1.9.2 windows-amd64) teamcity@build.syncthing.net 2018-01-19 06:21:05 UTC

I’ve all_proxy to my SOCKS proxy as follows:

λ set all_proxy

all_proxy=myproxy

When I start syncthing I do not see any log message indicating that my proxy settings have been detected.

Here is my verbose log (with links removed):

[monitor] 13:23:48 INFO: Log output saved to file “C:\Users\nnnnnn\AppData\Local\Syncthing\syncthing.log” [monitor] 13:23:48 INFO: Starting syncthing [GLAVD] 13:23:48 INFO: syncthing v0.14.44 “Dysprosium Dragonfly” (go1.9.2 windows-amd64) 2018-01-19 06:21:05 UTC [GLAVD] 13:23:48 INFO: My ID: NNNNNNN [GLAVD] 13:23:49 INFO: Single thread SHA256 performance is 366 MB/s using minio/sha256-simd (312 MB/s using crypto/sha256). [GLAVD] 13:23:49 VERBOSE: Starting up (C:\Users\nnnnnn\AppData\Local\Syncthing) [GLAVD] 13:23:50 INFO: Hashing performance with weak hash is 299.91 MB/s [GLAVD] 13:23:50 INFO: Hashing performance without weak hash is 356.72 MB/s [GLAVD] 13:23:50 INFO: Weak hash enabled, as it has an acceptable performance impact. [GLAVD] 13:23:50 INFO: Ready to synchronize “Default Folder” (default) (readwrite) [GLAVD] 13:23:50 INFO: Send rate is unlimited, receive rate is unlimited [GLAVD] 13:23:50 INFO: Rate limits do not apply to LAN connections [GLAVD] 13:23:50 INFO: Using discovery server
[GLAVD] 13:23:50 INFO: Relay listener (dynamic+ ) starting [GLAVD] 13:23:50 INFO: Using discovery server
[GLAVD] 13:23:50 INFO: Using discovery server
[GLAVD] 13:23:50 VERBOSE: Folder “default” is now scanning [GLAVD] 13:23:50 INFO: TCP listener ([::]:22000) starting [GLAVD] 13:23:50 INFO: KCP listener ([::]:22020) starting [GLAVD] 13:23:50 INFO: Completed initial scan of readwrite folder “Default Folder” (default) [GLAVD] 13:23:50 VERBOSE: Folder “default” is now idle [GLAVD] 13:23:50 VERBOSE: Folder “default” is now syncing [GLAVD] 13:23:50 VERBOSE: Folder “default” is now idle [GLAVD] 13:23:50 INFO: Relay listener (dynamic+ ) shutting down [GLAVD] 13:23:50 INFO: Relay listener (dynamic+ ) starting [GLAVD] 13:23:50 INFO: c.S.listenerSupervisor: Failed service 'dynamic+ ’ (1.000000 failures of 2.000000), restarting: true, error: “{dynamic+ dynamic+ } returned unexpectedly”, stacktrace: [unknown stack trace] [GLAVD] 13:23:50 INFO: GUI and API listening on 127.0.0.1:8384 [GLAVD] 13:23:50 INFO: Access the GUI via the following URL: [GLAVD] 13:23:50 INFO: Device NNNNNNN is “Work” at [dynamic] [GLAVD] 13:23:50 INFO: Device MMMMMM is “Home” at [dynamic] [GLAVD] 13:23:50 VERBOSE: Startup complete [GLAVD] 13:23:50 INFO: Relay listener (dynamic+ ) shutting down [GLAVD] 13:23:50 INFO: c.S.listenerSupervisor: Failed service 'dynamic+ ’ (1.997582 failures of 2.000000), restarting: true, error: “{dynamic+ dynamic+ } returned unexpectedly”, stacktrace: [unknown stack trace] [GLAVD] 13:23:50 INFO: Relay listener (dynamic+ ) starting [GLAVD] 13:23:50 INFO: Couldn’t fetch release information: Get : remote error: tls: access denied [GLAVD] 13:23:50 INFO: Automatic upgrade: no version to select [GLAVD] 13:23:51 INFO: Relay listener (dynamic+ ) shutting down [GLAVD] 13:23:51 INFO: Entering the backoff state. [GLAVD] 13:23:51 INFO: c.S.listenerSupervisor: Failed service 'dynamic+ ’ (2.992798 failures of 2.000000), restarting: false, error: “{dynamic+ dynamic+ } returned unexpectedly”, stacktrace: [unknown stack trace] [GLAVD] 13:23:51 INFO: Couldn’t fetch release information: Get : remote error: tls: access denied [GLAVD] 13:23:51 INFO: Couldn’t fetch release information: Get : remote error: tls: access denied [GLAVD] 13:23:52 INFO: Couldn’t fetch release information: Get : remote error: tls: access denied [GLAVD] 13:24:01 INFO: Detected 0 NAT services [GLAVD] 13:24:02 INFO: Couldn’t fetch release information: Get : remote error: tls: access denied [monitor] 13:24:25 INFO: Signal 2 received; exiting [GLAVD] 13:24:25 INFO: Exiting

Am I doing something wrong?

2

Yeah, you’re leaving out the scheme and the port, so it doesn’t work and gets bypassed - assuming myproxy is a name that resolves to something, otherwise that is also a problem and you should use an IP.

https://docs.syncthing.net/users/proxying.html

3

When I tried to post my support request, I got an alert stating I could only include one link in my post so I edited my real proxy address to “myproxy”.

My windows environment var was something like this:

all_proxy=myproxy.example.com:1080

I’ve reset it to

all_proxy=socks://myproxy.example.com:1080

and the proxy settings are being detected now.

Thanks :slight_smile:

4

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.