-
Notifications
You must be signed in to change notification settings - Fork 233
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
Scrapoxy doesn't work with DigitalOcean Firewall #203
Labels
connectors
all issue about connectors
Comments
By default it runs on port 3128 instead of 3125. Did you changed? |
Yes I know, I changed the port
…On Tue, Jan 19, 2021 at 9:07 AM André Duarte ***@***.***> wrote:
By default it runs on port 3128 instead of 3125.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#203 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAUBKE4BUKR5DAZQT6WFAQTS2WG2LANCNFSM4VVNZTQQ>
.
--
Will Perone
|
Worked for me only with private ip. |
to test |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Create a DigitalOcean firewall. Set to allow port 3125 traffic from (public and private ips running scrapoxy). Scrapoxy can't tell if proxies are alive anymore.
I've also tried accepting all TCP traffic on port 3125 from any IPV4 and IPV6 and scrapoxy still thinks the proxies are up but not alive.
The text was updated successfully, but these errors were encountered: