Welcome to the new Box Support website. Check out all the details here on what’s changed.

Box Status

boxcli error "Could not read environments config file"

Completed
Follow
New post
Naima Personal

Hi,

Mention: I have seen a similar post but that didn't help.

I've been having an error while trying to run this commands. I have run these same commands successfully before(about an month ago). However, all of a sudden it's giving this error. I'm not sure where it went wrong or I have done anything by mistake. 

[###@#### ~]$ box users:get
Could not read environments config file

[####@#### ~]$ box users:get --json --save
Could not read environments config file

Help from anyone will be highly appreciated. Thank you!

0

Comments

5 comments

Date Votes
  • Official comment
    Mike Grytsai

    Hi,

    The error states that Box CLI can't find the valid configuration file.

    The easiest way to fix that is to download new config file from the developer console, and provide the path to the downloaded file in the CLI using the following command: 

    box configure:environments:update --name=<enviroment_name> --config-file-path=/path/to/downloaded/config_file.json

     

    Another alternative would be to authenticate in CLI using OAuth following the guide 

    Comment actions Permalink
  • Naima Personal
    • Edited

    Hi Mr. Mike,

    Thank you so much for your response. Appreciate it.

    when I run "box configure:environments:get", its information "Client ID" "Enterprise ID" , "Box config File Path" everything match with the previous config.json file but still it didn't work.

    I'm following the first way to fix it. When I try this it gives the following error though the file is present to the path: 400 is the new config.json file's permission.

    box configure:environments:update --name=def --config-file-path=/file/path/config.json
    Could not read environment config file /file/paht/config.json.

    What could be the reason of this problem am I not following the instruction in right way? If you could help with that would be appreciable. Thank you!

    0
    Comment actions Permalink
  • Mike Grytsai

    Reasons for the below error could be that path provided to the config file is wrong. 

    Are you sure you provided the right file path? you can test it by executing `cat /file/path/config.json`, this will print out the content inside your configuration file.

     

     

    0
    Comment actions Permalink
  • Naima Personal
    • Edited

    Thank you Mr. Mike. 

    Appreciate your response. 

    Yes, I have done that for both, that gives the content of the both files which most likely mean given path is accurate; for previous config file, content like "enterpriseID", "clientID", are exact match of the output of the command "$ box configure:environments:get or box configure:environments:get -c"

    0
    Comment actions Permalink
  • Naima Personal

    Fixed! Path was accurate. Previously I copied the content of the config file to the server's config file. When I directly transferred the config file to the server, it worked though there weren't any difference in the content; I have done this same way before as well without any errors. Don't know why it happened this time. 

    Thank you so much for your help. Sincerely appreciate it.

    1
    Comment actions Permalink

Post is closed for comments.