mirror of
https://github.com/probberechts/soccerdata.git
synced 2026-04-25 10:05:53 +03:00
[GH-ISSUE #83] [General] Tor port is not up to date #18
Labels
No labels
ESPN
FBref
FotMob
MatchHistory
SoFIFA
Sofascore
WhoScored
WhoScored
bug
build
common
dependencies
discussion
documentation
duplicate
enhancement
good first issue
invalid
performance
pull-request
question
question
removal
understat
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/soccerdata#18
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @david-leconte on GitHub (Sep 25, 2022).
Original GitHub issue: https://github.com/probberechts/soccerdata/issues/83
(seen on Windows 11)
The Tor port specified in the code for when initializing a scraper with the
proxy="tor"option is 9050, whereas the new Tor versions seem to use port 9150.Something should be done to check whether port 9050 works in the first place and if it doesn't check with 9150.
For other people it doesn't work for right now, you can always do this :
@probberechts commented on GitHub (Sep 27, 2022):
I've just updated Tor and it still defaults to port 9050. Did you perhaps install the Tor Browser Bundle? That distribution indeed defaults to listening on port 9150.
@probberechts commented on GitHub (Sep 27, 2022):
Anyway, thanks for raising the issue. I think it would be good to add this to the docs.
@david-leconte commented on GitHub (Sep 27, 2022):
The only difference from a regular installation was that I downloaded the
Tor files and executable from a German mirror due to DNS blocking, maybe
that's what it is.
No problem, thanks for adressing the issue!
Le mar. 27 sept. 2022 à 19:32, Pieter Robberechts @.***>
a écrit :