question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

dask-distributed client socks proxies

See original GitHub issue

My scheduler is not reachable by the public web, I actually use a SOCKS5 proxy to reach it. The reason is, i’m limited by the number of public IPs I can have at one time. To perform my task, I’m using dask.distributed.Client.

  • I used to use ngrok to poke more holes but now I’ve reached the limit of how many ngrok tunnels I can have at the same time too.
  • Using socks4 or socks5 with dask.distributed.Client context manager did not work, or maybe i’m doing something wrong?

Perhaps this is a dumb question, but I did not find information about this in the documentation. https://distributed.dask.org/en/latest/local-cluster.html and https://distributed.dask.org/en/latest/client.html

Is there a way to add a socks proxy?

Issue Analytics

  • State:open
  • Created 4 years ago
  • Comments:14 (7 by maintainers)

github_iconTop GitHub Comments

1reaction
mrocklincommented, Dec 31, 2019

Hi @deepio , my apologies for the delay in response here.

cc’ing @jacobtomlinson , when you’re back from the holidays could you weigh in here?

0reactions
deepiocommented, Jan 14, 2020

What a great service (serveo), thank you for bringing this one to my attention. It’s too bad that it is currently disabled. Hopefully will see it in action in a few days though.

Dask has implemented many things I would need to program myself, I’m quite thankful that this exists! I’m not quite sure where to begin looking at the codebase but if I can help with implementing socks i’d be glad to help.

Read more comments on GitHub >

github_iconTop Results From Across the Web

API — Dask.distributed 2022.12.1 documentation
The client connects to and submits computation to a Dask cluster (such as a ... A Future is a local proxy to a...
Read more >
Client — Dask.distributed 2022.12.1 documentation
The Client is the primary entry point for users of dask.distributed . After we setup a cluster, we initialize a Client by pointing...
Read more >
Source code for distributed.client
[docs]class Future(WrappedKey): """A remotely running computation A Future is a local proxy to a result running on a remote worker.
Read more >
How to run parallelized python jobs on yarn using Dask?
1 ) How do I connect Dask to Hadoop/YARN and parallelize a job? When I try using: from dask.distributed import Client client ......
Read more >
SOCKS vs HTTP Proxy: What Is the Difference? - Oxylabs
When using SOCKS proxies, the internet traffic is routed through a proxy server via TCP connection on behalf of a client. Just like...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found