Option to be able to change oauth webserver port
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 59.9k
- Forks
- 5.4k
- Avg merge
- 2d 14h
- Merged PRs (30d)
- 48
Description
What is your current rclone version (output from rclone version)?
1.72.1
What problem are you are trying to solve?
I try to authorize Rclone (create an authorization JSON/token) for a headless server on Windows. I run (or formerly ran) something on the auth webserver port (53682) which gives the error message:
Error: config failed to refresh token: failed to start auth webserver: listen tcp 127.0.0.1:53682: bind: An attempt was made to access a socket in a way forbidden by its access permissions.
Actually nothing runs on that port. Maybe WSL2 or Docker Desktop or many of my browser windows did something, but I cannot get this working.
(I tried to run authorize onedrive with alpine/rclone:1.72.1 docker container, but couldn't map port, because somehow that port is opened later, so docker runner cannot pick that up; the container is started, but port is not reachable).
Only way to get this work locally is to have a restart (or logout-login), without WSL2 and Docker Desktop. I know about the remote possibilities, but it's hard to find an SSH-able machine and have the port tunneling and everything well.
How do you think rclone should be changed to solve that?
If it's possible, it would be great to have a command line parameter which can set the port of the auth webserver.
How to use GitHub
- Please use the 👍 reaction to show that you are affected by the same issue.
- Please don't comment if you have no relevant information to add. It's just extra noise for everyone subscribed to this issue.
- Subscribe to receive notifications on status change and new comments.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by tracing the auth webserver used when running the authorize command, focusing on how its current port 53682 is selected and how the webserver starts. Add a command-line option for selecting that port and verify that authorization works when the default port is unavailable, including the Docker use case described in the issue.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- authentication
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 62/100