Level up your Box knowledge with brand new learning paths on Box University. Visit training.box.com to get started

Box Status

Box ftp captcha

Follow
New post
releaseagent_runner

Hello,

We use automation script that uploads files to box daily (oauth makes issues for automation).

We connect to box using FTP.

After testing I got:

  • 530 Box: CAPTCHA is required. You have triggered Captcha on your account. To clear Captcha, use your Web browser and Box credentials (or External Password, if you're using SSO) to log in to app.box.com.

Is there anyway to disable this message? (from admin settings?)

If not, what is the trigger? is there any number of connections before block?

Thanks

2

Comments

4 comments

Date Votes
  • France

    Hi there, 

    Welcome to the Box Community!

    There is no way to disable this message and to clear the Captcha requirement, you need to follow as instructed and that is to go your account in Box.com  via your Web browser and login with your Box credentials.

    If you are still having problem connecting to Box via FTP, please go ahead and submit a support ticket with our Product Support team to get direct assistance.

    Thanks for your participation in the Community!

    Best,

    0
    Comment actions Permalink
  • Felipe Fischmann

    Getting the same error, doesn't seem to go away by signing in on a browser.

    0
    Comment actions Permalink
  • Revonda Mehovic

    I'm having the same issue in spite of logging in and out of the browser multiple times. Do you have a workaround?

    0
    Comment actions Permalink
  • Felipe Fischmann
    • Edited

    In our case it turned out that, in short:
    - We have several servers with the same IP
    - One of the servers was running a process with wrong Box credentials
    - This caused Box to "block" the IP and require a captcha in all servers, even the ones with valid credentials
    - In theory the captcha goes away if one waits for 90 minutes and then goes through the process once (as described by support). But because the process with wrong credentials kept trying to log in, these 90 minutes never elapsed

    So once we fixed the credentials in the process the issue was gone.

    0
    Comment actions Permalink

Post is closed for comments.