PostHog / PostHog/wizard

New setup with the wizard fails with 405

Open
#1,193 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
TypeScript
Stars
197
Forks
51
Avg merge
1d 23h
Merged PRs (30d)
94

Description

Hi there, trying to onboard a project in a new tenant, completely greenfield.
I created a Posthog tenant in the EU region, then ran the self-driving wizard, I get to the authorisation screen, confirm it, then the wizard reports that it cancelled the process.

I checked the logs and I can see it fails with a 405 on the OAuth endpoint.

[2026-09-02T09:20:38.651Z] [oauth] attempting callback server on port 8239
[2026-09-02T09:20:38.664Z] [oauth] callback server ready, showing login URL
[2026-09-02T09:20:45.132Z] [oauth] callback received with authorization code
[2026-09-02T09:20:45.164Z] [oauth] exchanging code for token at https://oauth.posthog.com/oauth/token
[2026-09-02T09:20:45.256Z] [oauth] token exchange failed (HTTP 405): Request failed with status code 405
[2026-09-02T09:20:45.258Z] [oauth] flow failed: AxiosError: Request failed with status code 405

Not sure whether there is a workaround or whether I should just wait and try in a few days?
Thanks,
Max

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the self-driving wizard's authorization flow and trace the callback server from the authorization screen to the token exchange at https://oauth.posthog.com/oauth/token. Reproduce the 405 and identify why the OAuth token request is rejected; done means a new EU tenant can complete setup without the wizard cancelling.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript
Domain
api, authentication
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Active
Clarity
Needs clarification
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.