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
api-access issue #331
Comments
i reproduced the exact same error with no api-access.json created so the problem is the node can't find the file. solved it by creating file exactly as: http://docs.bitshares.eu/api/access.html and placing at the same folder as config.ini. please make sure your api-access.json is located in the same directory as config.ini or you can use i think full path. i am pretty sure the problem is around file location. hope it helps. |
The issue is that the api-access.json file are not assumed to be in the same folder as the config.ini file. The code assumes to find this in the same space as the executable file. So when I specified api-access = "api-access.json" and placed it in the same folder (witness_node_data_dir) I got this error. Placing it in the root folder does not throw this error, but nothing specifies that the access json has been read and understood. On a side note, it seems that it doesn't matter if the filename is inside quotes or not. |
I can confirm that using a full path will work, because I am using this feature this way. I'm not sure where the file is designed to be, or how others are using it, so don't know whether changing the behavior or "fix" it will break any existed 3rd-party applications. |
i added a log to the startup when api-access is present in the config.ini or the command line: |
patch was merged, please check #332 |
When trying to follow the guide for adding API Access to restricted APIs I end up having an EOF Error.
The documentation I followed was: http://docs.bitshares.eu/api/access.html
The API Access JSON File contains:
config.ini
The Resulting Error
The text was updated successfully, but these errors were encountered: