RexSystem1 voteMerged from #640originally by @timjrobinson on GitHub
I set claude on the diagnosis and it found that an earlier setup in the process marked the setup as configured when the admin account was bootstrapped but then the server refused to enable policy.single_community_enabled because the server was configured (I've only been going through the main setup flow once, I haven't restarted it or tried to do a new setup).
Claude notes:
Confirmed the root cause. Here's your current stored state:
- app_public_config → setup.configured: **true**
- admin_bootstrapped → true
- instance_policy_config → does not exist (single-community mode was never successfully enabled)
So what happened: an earlier step already marked setup as configured and bootstrapped your admin account. Now the final "Finish
Setup" click sends policy.single_community_enabled: true, but the server refuses to enable single-community ("one server") mode once
setup.configured is already true — hence the 400 on every retry. You're in a stuck loop.
Thread
Comment by @timjrobinson