Getting help
Last updated
Support is a ticket you open here, an email address, and a public issue tracker for the relay. Nobody at Weald can read a workspace, list its members, or recover a lost recovery phrase, so the fastest route depends on what you need.
Open a support ticket
A ticket lives in your account. It needs a sign-in, because the thread is attached to your workspace and your billing rather than to an address anyone could type. Every reply lands on the same page, so nothing gets lost in a mailbox.
Where to write
- General help and account questions: hunter@getweald.com.
- Anything with a security dimension: hunter@getweald.com. Do not open a public issue for a vulnerability.
- Relay bugs and protocol questions: the public repository at Weald-Protocol/wealdrelay.
Larry, the chat box in the corner of this site, answers from these documentation pages and is the fastest way to find the page that already covers your question. He is not a person and does not open a ticket: he holds no session, knows nothing about your account or workspace, and cannot act on anything. Anything he cannot answer belongs in a ticket or an email.
What support cannot do
| Request | Answer |
|---|---|
| Read a message or a ticket to help debug it | Not possible. No key exists that would allow it |
| List who is in a workspace | Not possible. Member lists are inside the encrypted half |
| Recover a lost recovery phrase | Not possible. There is no escrow and no operator reset |
| Restore a workspace nobody has a device for | Not possible. Every copy lives on member devices |
| Tell you what your relay is doing | Yes. Versions, connection state, errors, storage |
| Fix a provisioning, billing or DNS problem | Yes. That half is ours and is not encrypted |
Every "not possible" above is a consequence of the design rather than a policy, which is why the docs set the expectation before the first ticket.
Reporting a security issue
Write to the security address above. A security contact and its expiry are also published at /.well-known/security.txt in the form RFC 9116 defines, so a researcher can find it without reading this page.
Before you write
Four things resolve most of what arrives:
- Larry, the chat box in the corner, searches these pages and answers in a sentence or two. If he says he is not sure, that is worth knowing too: it usually means the page does not exist yet, which is a useful thing to say in the ticket.
- Troubleshooting covers the failures a self-hosted relay actually produces and what each looks like from the app.
- The encryption panel in the Mac app names the relay hostname, the running digest, whether the access set is enforced, and the safety number for a channel.
- The relay's readiness endpoint says which dependency is unhealthy in words.
Status and releases
Every release is recorded on the changelog with its image digest, source tag and compatible protocol version. For an installed relay, the running digest is the thing to trust rather than the tag it was fetched under.
Create a support ticket Requires a sign-in.