Ozone labeling service live today is visible but cannot report to it

[SteveTownsend]

Selected both Bsky _did:plc:uac6er53o2pvr5y2qmvaf7hw#atprotolabeler and my reporting service _did:plc:ar7c4by46qjdydhdevvrndac#atprotolabeler to moderate a single post.

Bsky report works, mine gets Bad Gateway HTTP error. Is there latency in plumbing this together?

Only diff in HTTP headers is the did:plc field.

My service handle is nafo-moderation@bsky.social. [Do I have to change that to use my own domain?]

I have verified the service is live as follows. To me, this looks like an issue routing reports that target my DID to the right place. The URL in each case lands at https://amanita.us-east.host.bsky.network/xrpc/com.atproto.moderation.createReport

Have I missed a step, or misconfigued something?

[SteveTownsend]

tagging @bnewbold as this seems to be in scope for them, if they have time to take a look I'd appreciate it