DSM 7.1 Drive client fails to use socks5 proxy

Currently reading
DSM 7.1 Drive client fails to use socks5 proxy

1
0
NAS
DS223J
Operating system
  1. Linux
  2. macOS
Mobile operating system
  1. iOS
I have Synology Drive 3.4.0 installed on a ds223j, and the 3.4.0 client on my MacBook Pro, running Sonoma 14.1.1. I work in a hospital that blocks all outbound traffic except http(s), so I need to be able to connect over socks5. I have socks5 tunneled through ssh tunneled through https, and it works for other services (smtp, imap, http, https) but not for Synology Drive. I'm investigating now on my home network, and see in daemon.log:

Bash:
$ grep -b2 proxy daemon.log
2175618-2023-12-01T11:38:13 (27728:56384) [INFO] init-handler.cpp(44): Initialize session 1 with sync_id: 13630
2175722-2023-12-01T11:38:13 (27728:56384) [INFO] protocol-client.cpp(135): Failed to establish a new channel (-2), trying to find a new connection.
2175862:2023-12-01T11:38:13 (27728:56384) [INFO] connection.cpp(619): Going to find connection for connection: '{server_name:ds223j.example.com, server_ip:192.168.1.5, server_port:6690, mode:3, username:jeffemandel, password:***hidden***, key_pem:, key_fingerprint, ds_id:1d01fe70e7d6f3883e229e32f5516f98, restore_id:1d01fe70e7d6f3883e229e32f5516f98, host_name: ds223j, session:75bc45a3a5172d39b9a21a1fbaa7085b, protocol_ver:70, conn_id:1, computer_name:JeffMandelMBP, use_ssl:1, linked:0, ssl_allow_untrust:0, ssl_signature:xxx, version_info: {major: 3, minor: 4, build_number: 15724}, status:0, enable_shared_with_me:0, conn_type:1, cloud extension clsid:, server_fingerprint:, domain_name: ds223j.example.com, is_index_home: 1, user_is_admin: 1, error:0}' with proxy '{use_proxy: 1, use_sys_proxy: 0, proxy_ip: 127.0.0.1, proxy_port: 1080, auth_type: 0, user_name: , password: ********, domain: , host: JeffMandelMBP.example.com}', use_quick_connect_server = Yes.
2177594:2023-12-01T11:38:13 (27728:17344) [ERROR] proxy_channel.cpp(84): ProxyChannel: cannot connect to proxy
2177697:2023-12-01T11:38:13 (27728:70464) [ERROR] proxy_channel.cpp(84): ProxyChannel: cannot connect to proxy
2177800-2023-12-01T11:38:13 (27728:70464) [ERROR] proto-ui.cpp(674): failed to connect to server at 192.168.1.5:6690
2177909:2023-12-01T11:38:13 (27728:43904) [ERROR] proxy_channel.cpp(84): ProxyChannel: cannot connect to proxy
2178012-2023-12-01T11:38:13 (27728:17344) [ERROR] proto-ui.cpp(674): failed to connect to server at 192.168.1.5:6690
2178121-2023-12-01T11:38:13 (27728:43904) [ERROR] proto-ui.cpp(674): failed to connect to server at 192.168.1.5:6690
--
2178382-2023-12-01T11:38:13 (27728:17344) [ERROR] conn-finder.cpp(298): TestConnect: error code -200, error message: 'channel error while connecting to server'
2178534-2023-12-01T11:38:13 (27728:43904) [ERROR] conn-finder.cpp(298): TestConnect: error code -200, error message: 'channel error while connecting to server'
2178686:2023-12-01T11:38:13 (27728:97024) [ERROR] proxy_channel.cpp(84): ProxyChannel: cannot connect to proxy
2178789-2023-12-01T11:38:13 (27728:97024) [ERROR] proto-ui.cpp(674): failed to connect to server at 192.168.1.5:6690
2178898-2023-12-01T11:38:13 (27728:97024) [ERROR] conn-finder.cpp(298): TestConnect: error code -200, error message: 'channel error while connecting to server'
It fails with the proxy 3 times, then tries without the proxy and succeeds on the internal network, but not in the hospital. Here is my ssh.config:
Bash:
Host *.example.com
    IdentityFile /Users/jeffemandel/.ssh/id_ecdsa
    Compression yes
    DynamicForward *:1080
    SessionType none
    StdinNull yes
    passwordauthentication no
    ControlMaster no
    LogLevel VERBOSE

I don't have any errors in the ssh log. If I try to connect with curl using the proxy, I get:
Bash:
curl -vv --socks5 127.0.0.1:1080 ds223j.example.com:6690
* processing: ds223j.example.com:6690
*   Trying 127.0.0.1:1080...
* Connected to 127.0.0.1 (127.0.0.1) port 1080
* SOCKS5 connect to 192.168.1.5:6690 (locally resolved)
* SOCKS5 request granted.
* Connected to 127.0.0.1 (127.0.0.1) port 1080
> GET / HTTP/1.1
> Host: ds223j.example.com:6690
> User-Agent: curl/8.2.1
> Accept: */*
>
* Empty reply from server
* Closing connection
curl: (52) Empty reply from server
Of course, telnet to port 6690 doesn't get a response either.
 

Create an account or login to comment

You must be a member in order to leave a comment

Create account

Create an account on our community. It's easy!

Log in

Already have an account? Log in here.

Similar threads

Using Drive Client 3.4.0 on Win 10. By default, it seems like the client is copying my entire home profile...
Replies
0
Views
428
  • Question
Thanks for your replies. fredbert's suggestion would work I guess, but the folders wouldn't be in my home...
Replies
3
Views
711
  • Solved
Finally found some info on this thread. So, to my understanding, it is impossible to use win/mac Drive...
Replies
1
Views
1,105
Thank you, that will help, but its almost there. Not all places I support use AD or even LDAP. I would...
Replies
2
Views
862
My Drive client was working fine for months. Then one day out of the blue it stopped syncing. I get this...
Replies
0
Views
881
  • Solved
You're right! Thinking twice about it, I don't understand my thoughts of yesterday. My bad - I will...
Replies
12
Views
6,317
  • Question
I was able to find and purge the log in Windows. C:\ > Users > [user] > AppData > Local > SynologyDrive >...
Replies
7
Views
7,807

Welcome to SynoForum.com!

SynoForum.com is an unofficial Synology forum for NAS owners and enthusiasts.

Registration is free, easy and fast!

Trending threads

Back
Top