Can't retrieve token from new Dropbox remote setup

Help and Support
1

What is the problem you are having with rclone?

When trying to set up a new remote at Dropbox (with blank client ID and secret and no advanced config), I get the following. I was able to create a remote with no problem a month or so ago, but then it stopped working. All attempts since to create a new one have had this same problem. The browser opens and shows Success!, but on returning to terminal, I see the following. Note that (additionally) I'm confused by what is meant by setting the Redirect URL in my custom config. Where would I see that?

Thanks for any help.

2026/09/20 15:59:43 NOTICE: Make sure your Redirect URL is set to "http://localhost:53682/" in your custom config.
2026/09/20 15:59:43 NOTICE: If your browser doesn't open automatically go to the following link: http://127.0.0.1:53682/auth?state=vsL5v_GWjoV1jko-oBolTw
2026/09/20 15:59:43 NOTICE: Log in and authorize rclone for access
2026/09/20 15:59:43 NOTICE: Waiting for code...
2026/09/20 15:59:52 NOTICE: Got code
Error: failed to get token: Post "https://api.dropboxapi.com/oauth2/token": dial tcp 162.125.4.19:443: connect: bad file descriptor
```

Run the command 'rclone version' and share the full output of the command.

```
rclone v1.75.1
- os/version: darwin 26.7 (64 bit)
- os/kernel: 25.6.0 (arm64)
- os/type: darwin
- os/arch: arm64 (ARMv8 compatible)
- go/version: go1.26.8
- go/linking: dynamic
- go/tags: cmount

```

Which cloud storage system are you using? (eg Google Drive)

Dropbox

The command you were trying to run (eg rclone copy /tmp remote:tmp)

```
rclone config
```

Please run 'rclone config redacted' and share the full output. If you get command not found, please make sure to update rclone.

See next.

A log from the command that you were trying to run with the -vv flag

```
2026/09/20 16:26:17 DEBUG : rclone: Version "v1.75.1" starting with parameters ["rclone" "config" "redacted" "-vv"]
2026/09/20 16:26:17 DEBUG : Using config file from "/Users/bg/.config/rclone/rclone.conf"
[bgchlaenius]
type = local

[bgdam]
type = sftp
host = XXX
user = XXX
key_pem = XXX
shell_type = unix
md5sum_command = md5sum
sha1sum_command = sha1sum

[bgdream1]
type = s3
provider = Dreamhost
access_key_id = XXX
secret_access_key = XXX
endpoint = s3.us-east-005.dream.io
acl = private
region = us-east-005

[bggd]
type = drive
scope = drive
token = XXX
team_drive = 

[bgicloud]
type = iclouddrive
apple_id = XXX
password = XXX

[pribox]
type = box
token = XXX

[prigd]
type = drive
client_id = XXX
client_secret = XXX
scope = drive
token = XXX
team_drive = 

[prigd2]
type = drive
client_id = XXX
client_secret = XXX
scope = drive
token = XXX
team_drive = 

[prispec]
type = s3
provider = AWS
access_key_id = XXX
secret_access_key = XXX
region = us-east-1
acl = private
### Double check the config for sensitive info before posting publicly
2026/09/20 16:26:17 DEBUG : rclone: Version "v1.75.1" finishing with parameters ["rclone" "config" "redacted" "-vv"]
```
2

hi,
as a quick test, as per your example, i created a new dropbox remote using rclone's default config.
it works, no problems

i think this is the hint.
perhaps issue with your machine? dns, vpn, proxy server, etc..
can you test on another machine, physical or virtual?

that does not apply to your example, as you are using rclone's default configuration
if you were using a client id+secret, that would be a custom config

3

Thanks, @jojothehumanmonkey. I had tried different browsers, but it didn’t occur to me to try a different machine. I had no trouble making a new remote on a different computer (both Macs). However, when I copied the relevant code from the config file over to the original machine, it still didn’t work and even running a simple command (rclone size) works on the second, but not the first. I think you’re right about the hint, but will have to dig into it more, as I don’t know what would have changed.

Thanks for your help!

4

Hi,

Any chance you can create a new user account on your Mac that has a clean profile and then try and create the rclone connection from there?

It seems that something in your login environment on the first Mac has something wrong with it.

If it works then you know the problem is with your login account.

From that point I don't know enough about Mac to help.

5

Leo --

I found the penultimate solution, but not the ultimate one. I use Little Snitch (a Mac and Linux firewall/network monitor). Even though I had it set to allow everything through, I had to actually disable it in my Mac’s network settings to retrieve the token. With it disabled, all is working as it should. The confusing thing is that my second Mac was set up the same way but with Little Snitch enabled, and it was working fine. There’s a slight mismatch in OS version (26.7 on the first Mac and 27.0 on the second), so it’s possible that accounts for this. I’ll pursue this further so that I can again use Little Snitch, but at least my scripts will run again for now.

I’m considering this closed now as far as rclone and the forum is concerned. Thanks for your reply!

Brian

6

I see. Thanks for the update.

So you needed to turn off your firewall in order to get the token. After you got to token can you use rclone to connect to the drive with the firewall enabled?

7

Nope, throws an error until I disable it again. But the other Mac works fine with it enabled. I’m missing something…

Am waiting until OS 27.1 comes out to upgrade the first Mac (my production one). After that, I’ll research it further to see if that fixes the discrepancy.

8

With my VPN software I can do what is called split tunneling that selects a specific app and says don't go through the VPN for this app.

Is there a feature in your firewall that says leave this app alone?

9

Little Snitch has a slew of adjustments that can be made, but I’ve never dug into them. I’m pretty sure I can eventually get it configured so it works, but will have to RTFM. :slight_smile: