Skip to content
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

Error: "Command failed because error occurred: invalid character 'p' after top-level value" on running hydra client create #1244

Closed
sum2000 opened this issue Dec 19, 2018 · 3 comments

Comments

@sum2000
Copy link

sum2000 commented Dec 19, 2018

Describe the bug
When running
hydra clients create
i get an error
Command failed because error occurred: invalid character 'p' after top-level value

To Reproduce
Steps to reproduce the behavior:

  1. Download hydra binary for darwin-amd64 and version:1.0.0-rc.5+oryOS.10
  2. Set environment variable 'HYDRA_ADMIN_URL' to http://localhost:4444/
  3. Run hydra client create after making the binary executable
  4. See error described above

Expected behavior
Should receive information about necessary flags required to run the command instead of the error.

Screenshots
screen shot 2018-12-19 at 6 29 02 pm

Version:

  • Environment: macOS High Sierra
  • Version: 10.13.6

Additional context
Surprisingly, hydra clients delete and hydra clients get work as expected.

@aeneasr
Copy link
Member

aeneasr commented Dec 20, 2018 via email

@sum2000
Copy link
Author

sum2000 commented Dec 20, 2018

Yes, I figured that part. But when we provide public hydra URL, this error is due to JSON parsing. I guess the method looks for JSON in the response body but gets 404 code instead. A more helpful error message can be something like "You are providing public URL for an Admin Command"

aeneasr added a commit that referenced this issue Apr 2, 2019
This patch significantly refactors internal configuration and service management with the goal of making configuration changes possible without service restarts. This patch prepares the possibility to configure ORY Hydra from a remote source (etcd, consul) and watch for changes. This patch also introduces the possibility to configure ORY Hydra from a configuration file on top of environment variables.

The following issues have been fixed as well:

- Key rotation of the system secret is now much simpler (closes #1316)
- Database connectivity parameters such as max_conns no longer cause issues with older postgres versions (closes #1327)
- Non-existing routes now return a JSON error instead of `text/plain` when `application/json` was requested (clsoes #1244)
- We now push tags latest, X, X.Y, X.Y.Z to docker hub (closes #1289)
- The quickstart guide no longer builds the source code but instead pulls latest tag (closes #1309)
- We moved to goreleaser and godownloader for release management (closes #1107)
- The quickstart Docker Compose files are now reusable (closes #1196)

The following issues are also resolved:

- Closes #1121 

Signed-off-by: aeneasr <[email protected]>
@aeneasr
Copy link
Member

aeneasr commented Apr 11, 2019

The router now returns a JSON response when application/json was requested!

@aeneasr aeneasr closed this as completed Apr 11, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants