-
-
Notifications
You must be signed in to change notification settings - Fork 116
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
How do I properly use this? #132
Comments
also even on docker I get these messy errors on the output: |
BTW I want to add some additional info on my process. At first I was just trying to load pages in my browser with the proxy set to the server but after searching through all the issues I saw someone using curl with the proxy flag so I used that for testing afterwords. |
Did some more testing, went ahead and made a dev container using vscode using a python3 template with python 3.8 installed. I still get the same depreciation warnings as before and I still can't get serve to show any connections at all and when I run a curl I still get my own ip nearly every time. I also went ahead and tried to make a script in order to grab and CHECK proxies and put them into a file so I could try to use proxy.py in order to host a proxy server since this isn't working no matter what I do but I am getting errors saying:
|
I've done some more testing and experimenting, so far I've gotten proxy.py working-ish using the following start script:
Basically the script uses ProxyBroker to find and check proxies then scrape the output IP:PORT Combos to a file called ips.txt which is then read and ran through a curl check to make sure the proxies are indeed working. Then adds each working proxy into a proxy pool for proxy.py. Unfortunately with this setup my ip is always returned even after disabling the headers Via, X-Forwarded-For, Remote_Addr, and X-Real-IP. This is kinda odd since when using proxybroker serve I had at least a 5% chance of a different IP being returned but when using proxy.py I get a 100% return rate of my own IP. I also "tried" to make a plugin for proxy.py that would instead modify the X-Forwarded-For header to replace the ip of the client with a random upstream proxy ip but failed to get proxy.py to load the plugin cause I'm not that smart... I wouldn't mind switching back to just ProxyBroker if anyone can help me get it working properly but all my testing leads me to believe that proxybroker is just broken atm since it doesn't even show incoming connections whereas proxy.py at the very least does that. Please help.... |
I've been trying to get this working for a good 2 hours now and I can't seem to get serve to work. At first I couldn't run proxybroker at all on windows due to aiodns being depreciated among other issues so I pulled the docker container. After about 45 minutes I was able to get it running and working with the find command but when I launch a serve instance with
docker run --rm -p 8888:8888 bluet/proxybroker2 --log CRITICAL serve --host 127.0.0.1 --port 8888 --types HTTP HTTPS --lvl High --min-queue 5
I at least got it running but then when I tried to see if it was working by going to localhost:8888 i got a 400 error after changing the host to 0.0.0.0 so I figured it was working but when I add it to my proxy settings and check my ip I got a different ip ONCE and then it went back to my normal ip but the console shows no connections so idek if it's getting anything.What do I need to do to get this working properly?
The text was updated successfully, but these errors were encountered: