Keyboard shortcuts

Press ← or → to navigate between chapters

Press S or / to search in the book

Press ? to show this help

Press Esc to hide this help

Authentication

  1. Open a private chat with the bridge bot. Usually @signalbot:your.server

Linking as secondary device

  1. Go to "Linked Devices" in the Signal app settings and add a new device.
  2. Send login to the bridge bot.
  3. Scan the QR code the bridge sends you.
  4. If backfill is enabled in the bridge config, Signal will ask whether you want to transfer message history. You can choose whichever option you want.
  5. Finally, the bot should inform you of a successful login.
    • If you chose to transfer history, recent chats should be created and backfilled automatically. If not, chats will be bridged when you receive new messages

Registering as the primary device

Registering as the primary device is no longer supported directly in the bridge. Using an official mobile app is recommended. However, if you don't want to use those, signal-cli works quite well too.

signal-cli instructions
  1. Download the latest release of signal-cli.
  2. Run signal-cli -u +123456789 register
  3. Go to https://signalcaptchas.org/registration/generate.html to generate a captcha code.
    • The page will redirect you to a signalcaptcha:// URI after solving the captcha. At least on Firefox, you need to have the devtools console open to be able to see and copy the URI.
    • Alternatively, you can wait for a few seconds for the "Open Signal" button to appear, then right click on it and copy the link.
  4. Run signal-cli -u +123456789 register --captcha 'signalcaptcha://signal-hcaptcha...' with the generated captcha code.
  5. Run signal-cli -u +123456789 verify 123456 (123456 being the code sent over SMS).
  6. Send login to the bridge bot.
  7. Run signal-cli -u +123456789 addDevice --uri 'sgnl://...' with the URI returned by the bridge bot.
  8. The bot should inform you of a successful login.
  9. Run signal-cli -u +123456789 receive occasionally to make sure the registration remains active.
    • Optionally use the -t -1 flag to make it run in the background. However, it needs occasional updating and it might also crash randomly, so you shouldn't leave it completely unattended.