Bug Report: The managed reverse proxy consent screen reappears unintentionally
Open
Nobody has claimed this yet.
bug
team/platform-features
- Dominant language
- Python
- Stars
- 39.9k
- Forks
- 3.4k
- Avg merge
- 6h 51m
- Merged PRs (30d)
- 232
Description
Bug Description
Users can create a managed reverse proxy to route their events through. However, sometimes the consent screen will reappear on users who have already accepted this. This may show up even if users already have a proxy running.
How to reproduce
- Looking into how to reproduce this. As it is quite inconsistent.
Additional context
- From https://posthoghelp.zendesk.com/agent/tickets/58662 (moved to PostHog: https://us.posthog.com/project/2/support/tickets/59969)
- This is purely a cosmetic issue, as the proxy itself still works fine. It just causes confusion as if the proxy is not yet set up.
Debug info
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue names no files or tests. Start by locating the managed reverse proxy consent screen and the condition that controls whether it appears, then investigate the inconsistent reappearance after consent when a proxy is already running. Done means the screen stays dismissed in that situation and the behavior is covered by a regression check.
Written by the indexing model from the issue text.
Assessment
- Domain
- frontend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100