Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

is there a way to tell it to generate new circuit (new IP)? #49

Open
airdogvan opened this issue Jun 16, 2020 · 5 comments
Open

is there a way to tell it to generate new circuit (new IP)? #49

airdogvan opened this issue Jun 16, 2020 · 5 comments

Comments

@airdogvan
Copy link

I'm running with the simple docker run -it -p 8118:8118 -p 9050:9050 -d dperson/torproxy command and using it at port 9050 for browser proxy.
But I noticed each time I start it it seems to run the same circuit resulting in the same IP (exit node).

Is there a way to tell it to generate new one?

Thanks

@ProjectDarkTiger
Copy link

I want to know too!

@XSPGMike
Copy link

I have the same question

@nguyenhn1299
Copy link

You can check the Dockerfile that the controlport is 9051. So just map it outside to use.

sudo docker run -it -p 8118:8118 -p 9050:9050 -p 9051:9051 -e PASSWORD=yourpass dperson/torproxy

from stem import Signal
from stem.control import Controller

with Controller.from_port(port=9051) as controller:
	controller.authenticate(password="yourpass")
	controller.signal(Signal.NEWNYM)

@des1redState
Copy link

Yes. See comment in thread: #80

@henriqueutsch
Copy link

Hy guys
My question is 9051 port is not open when I run nmap command
image: dperson/torproxy ports: - 8181:8181 - 9050:9050 - 9051:9051 environment:

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

6 participants