Local Hosted Trying to Phone Home

[eharb04]

Running a local hosted version. Over the last few days it has stopped working. It seems to be trying to phone home.
`Jun 23 16:40:11.261 INFO Server stats endpoint: https://api.bencher.dev/v0/server/stats/b70f0731-5556-433a-ba08-98a827d29f7c

bencher_console | 16:40:11 [@astrojs/node] Server listening on
bencher_console | local: http://localhost:3000
bencher_console | network: http://10.43.32.141:3000
bencher_console |
bencher_api | Jun 23 16:40:41.815 WARN Failed to register startup: error sending request for url (https://api.bencher.dev/v0/server/stats/b70f0731-5556-433a-ba08-98a827d29f7c?startup=true)`

Also the console seems to want to run on port 3002 or 3004 instead of 3000 like it was and like I specified. When I pull up the console and try to do anything, I get Reconnecting to the Bencher API... pop up in a banner. Then it says Unable to reach the Bencher API..
I don't know why this all worked a few days ago just fine. I have downloaded 0.6.6 images to run locally and haven't changed anything in the configuration files, so I don't know why this isn't working all of a sudden. Unless it isn't truly locally hosted and pulling changes from somewhere.

[epompeii]

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

There are two separate things going on here, and the "phone home" one is not actually what broke your setup.

1. The server/stats request to api.bencher.dev is expected, and harmless.

Self-hosted Bencher registers on startup and sends a small daily usage stat to api.bencher.dev. This is part of the Bencher Plus license/usage model, not a sign that your instance isn't local. The WARN Failed to register startup line just means your server couldn't reach api.bencher.dev (offline or firewalled); it does not block anything locally.

The reason you only started noticing it "a few days ago" is that the visible startup-registration ping was added in v0.6.6, which is the version you pulled. Earlier versions sent only the silent daily stat, so there was nothing in the logs on boot.

If the outbound request bothers you, you can block egress to api.bencher.dev at your firewall.

2. "Unable to reach the Bencher API" is a separate, local issue.

That banner comes from the Console failing to reach your API, not api.bencher.dev. The clue is the Console drifting off port 3000 to 3002/3004: that happens when port 3000 is already taken (e.g. a stale container) or when the host port auto-increments. When the Console is served from an unexpected origin/port, the API rejects it because the allowed origin is derived from your console.url setting.

To fix it:

• Make sure only one Console is running and it is actually on the port you expect (docker compose down to clear stale containers, then bring it back up).
• Confirm BENCHER_API_URL (and INTERNAL_API_URL for Docker-to-Docker) point at your API, and that the API server's console.url matches the URL/port you load the Console from.
• Heads up for when you upgrade further: in v0.6.8 the default self-hosted API port changes from 61016 to 6610, so keep the API port and the Console's BENCHER_API_URL in sync. See the v0.6.8 changelog.

Can you share your docker-compose.yml (or bencher up command) and your API server config (with secrets redacted)? That'll let us pin down the port/origin mismatch.