Partytracks/sessions/new 403 Forbidden Error
- Dominant language
- TypeScript
- Stars
- 2.3k
- Forks
- 348
- PR merge metrics
- No merged PRs in 30d
Description
When build from localhost & try to join room, got error message, it keeps report error on the URL:
```
[wrangler:inf] POST /partytracks/sessions/new 403 Forbidden (476ms)
{
eventName: 'alarm',
meetingId: '4db66d72-83bd-4111-994b-c5b349a42f57'
}
{
eventName: 'clientNegotiationRecord',
connectionId: '95f0c480-3961-4a90-8c7d-43e3f2544afd',
meetingId: '4db66d72-83bd-4111-994b-c5b349a42f57',
entry: {
endpoint: '/partytracks/sessions/new?correlationId=4db66d72-83bd-4111-994b-c5b349a42f57',
method: 'POST',
type: 'request'
},
sessionId: undefined
}
```

Contributor guide
Research direction
Start by reproducing the localhost room-join flow and inspect the Wrangler log for POST /partytracks/sessions/new returning 403. Trace the request associated with the meetingId and correlationId shown in the report to identify where the rejection occurs. Done means joining a room from localhost no longer produces the 403 response.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- api, backend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100