How I got rclone to get a token for Box

I'm trying to migrate users to Box. FTP is horribly slow (especially since parallel requests seem to confuse Box). I'm hoping that rclone is faster.

Unfortunately, rclone requires token authentication. And it fails. Running "rclone authorize box" gets me an error from Box about an insecure_redirect_uri (redirect_uri=http://127.0.0.1:53682/state=...).

This forum doesn't allow new users to post more than two URLs, so go here for the rest of what I would have posted: http://uploads.lairds.com/kyler/rclone_token.txt

1 Like

Just bumped into this myself (timely). I sit next to the Box admin, between the two of us we seem to have enabled the rclone box app and given all the permissions... It's still working on my linux box afaik, so I guess this is a new remote issue (at least for me). Box I was on is OSX High Sierra, should that matter.

I've run into a similar issue. My company uses rclone to mount box. We have Okta as our SSO. As of a couple days ago the mount worked flawlessly but now we get the error:
---------------
Don't worry, your files are perfectly safe. Get in touch with Box support to get assistance with this app. We're here to help.

Error: insecure_redirect_uri

Show Error Details

  • response_type=code
  • redirect_uri=http://127.0.0.1:53682/

Any help would be appreciated!

The box team have unlisted rclone from the app gallery.

This should mean that

  • the 127.0.0.1 redirect works OK
  • the old config works OK.

I had no idea getting rclone listed in the app gallery would cause so much disruption - I'll try to work with box for a smoother transition next time.

1 Like

Closing to consolidate duplicate recent topics. Keeping this one open in favor.