-
Notifications
You must be signed in to change notification settings - Fork 634
Unable to set credentials, 'No such file or directory' #204
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
@arnoud999 , are you on a personal computer? The credentials file tries to get created in
You've probably got a permissions problem, but I'm sure we can figure out a way to get you up and running. The simplest thing to get going straight-away is to just sign in.
In general, this isn't a great solution as you'll be hard-coding your credentials and you'd have to do it for every script. |
Thanks for your quick response!
It indeed seems to be a permission problem, I'm on a work computer and my user folder is some kind of network drive. Is it possible to change the location of |
@arnoud999 , specifying the location of the Until then, yes, you'll need to sort out the permission block. I had thought that our R library handled this though, @mkcor , thoughts? |
@theengineear You are right, I remember troubleshooting Windows users in the past... But this may be yet another thing... It could be a thing to let users specify/overwrite environment variable I think Windows does not understand Can you try and run, say: py <- plotly("rAPI", "yu680v5eii") Please? |
Unfortunately, I get the same error:
|
@arnoud999 It's not the same error! The py <- plotly(username="rAPI", key="yu680v5eii", base_url="https://plot.ly") Let me know how it goes! |
That works, thanks a lot! 👍 |
When I try to set my credentials/API key, I get the following error message:
I've tried creating the .plotly folder and the .credentials file myself, and I tried running R through a command window as administrator, but in both cases I still saw the same error message.
The text was updated successfully, but these errors were encountered: