Unable to access API with self-hosted

[eharb04]

Repeatedly get Failed to get API server version: Invalid response payload: expected value at line 1 column 1 error for every bencher run command. Versions of CLI, API, and console are all v0.6.6. Input my host location for the API server but nothing has gotten me passed this. When I curl the same host it will return some data.

What needs to be done to get around this issue?

[eharb04]

Was able to curl a benchmark to the API and see them on the console. Still can't use builtin bencher run command to post data.

[epompeii]

@eharb04 thank you for using Bencher, and I'm sorry you're running into trouble.

How are you running Bencher Self-Hosted? Are you using bencher up or some other deployment method?

Can you give me an example of the bencher run comman you're trying to run?
If you can also provide the curl command that works that may help too.

[eharb04]

curl -X POST http://localhost:61016/v0/run -H "Authorization: Bearer <USER_TOKEN>" -H "Content-Type: application/json" -d @path/to/json.json
Any and all bencher run commands to the API did not work. bencher up did not work either, make a docker-compose file with same setup from the API and console images.

[epompeii]

Any and all bencher run commands to the API did not work.

Can you please share some examples of what you tried. It would really help with troubleshooting.

bencher up did not work either

What operating system and version are you trying to run on? Any additional details about your environment would really help with troubleshooting.

What's the exact command you're running?
What errors are you seeing when you run those commands?

Trying to debug your own Docker Compose setup will be much more difficult, so I'd say we start with getting bencher up working for you first.

[eharb04]

Used x86_64 GNU/Linux.
Tried the example bencher run bencher mock command that is provided at login. That is one example.
bencher up Pulling ghcr.io/bencherdev/bencher-console:v0.6.8` image...

Failed to pull Docker image (ghcr.io/bencherdev/bencher-console:v0.6.8): Docker responded with status code 500: no such file or directory`

[eharb04]

I have downloaded the images.
ghcr.io/bencherdev/bencher-api v0.6.6 f2575dc275df 5 weeks ago 207 MB ghcr.io/bencherdev/bencher v0.6.6 2502731fdfaa 5 weeks ago 51.5 MB ghcr.io/bencherdev/bencher-console v0.6.6 647b89d3ea4a 5 weeks ago 514 MB

However, when running bencher up I get:
bencher up
Stopping existing bencher_console container...
Removing existing bencher_console container...

Stopping existing bencher_api container...
Removing existing bencher_api container...

Pulling ghcr.io/bencherdev/bencher-console:v0.6.6 image...

Failed to pull Docker image (ghcr.io/bencherdev/bencher-console:v0.6.6): Docker responded with status code 500: no such file or directory

[eharb04]

I am using Podman instead of Docker too

[epompeii]

Thanks for the extra details, that helps a lot. There look to be two separate things going on.

1. The original bencher run error

Failed to get API server version: Invalid response payload: expected value at line 1 column 1 means the CLI reached your host but got back something that is not JSON (typically HTML). The CLI calls GET <host>/v0/server/version and expects {"version":"..."}.

The usual cause is --host (or BENCHER_HOST) not pointing at the API server's base URL. A couple of things to check:

• Heads up on a recent change: in v0.6.8 we switched the default self-hosted API port from 61016 to the IANA-registered 6610 (see the v0.6.8 entry in the changelog). Your working curl hits http://localhost:61016/v0/run, which is the old default, but a newer CLI defaults to 6610. If your CLI and API are on different ports, the CLI ends up talking to the wrong place. Make the port you pass to --host match the port your API server is actually bound to (server.bind_address).
• Make sure --host is the API base URL only, with no path and not the Console UI port (the Console defaults to 3000). Pointing at the Console returns HTML, which produces exactly this error.

So, given your setup, try:

bencher run --host http://localhost:61016 --token <USER_TOKEN> ...

If you are going through a reverse proxy, confirm that route returns the API's JSON and not an HTML page.

2. bencher up with Podman

Since you already have the v0.6.6 images pulled locally, the failure is the pull step, not the run step. bencher up defaults to --pull always, which always asks the daemon to pull from ghcr.io, and Podman's Docker-compatible pull endpoint is what is returning status code 500: no such file or directory.

Because the images are already local, skip the pull:

bencher up --pull never

(--pull missing also works.) That should let it start the API and console containers from your local images.

Let me know how those go and we can dig in further if needed.