Troubleshooting guide

Login issues

Owing to the distributed nature of OAuth on AT Protocol, you may run into issues with logging in. If you run a self-hosted PDS:

• You may need to ensure that your PDS is timesynced using NTP:
  • Enable the ntpd service
  • Run ntpd -qg to synchronize your clock
• You may need to increase the default request timeout: NODE_OPTIONS="--network-family-autoselection-attempt-timeout=500"

Empty punchcard

For Tangled to register commits that you make across the network, you need to setup one of following:

• The committer email should be a verified email associated to your account. You can add and verify emails on the settings page.
• Or, the committer email should be set to your account’s DID: git config user.email "did:plc:foobar". You can find your account’s DID on the settings page

Commit is not marked as verified

Tangled only supports SSH commit signatures. Ensure the SSH public key you use for signing is uploaded to Tangled.

To sign commits using an SSH key with git:

git config --global gpg.format ssh
git config --global user.signingkey ~/.ssh/tangled-key

To sign commits using an SSH key with jj, add this to your config:

[signing]
behavior = "own"
backend = "ssh"
key = "~/.ssh/tangled-key"

Self-hosted knot issues

If you need help troubleshooting a self-hosted knot, check out the knot troubleshooting guide.