Skip to content

Networks and connections

Use Connect or Add network to configure an IRC connection. Enter the server hostname, port, TLS preference, nickname, and any required authentication. A signed-in Relay account keeps its IRC connections alive when the browser is closed.

Administrators can lock a deployment to a preconfigured network. When lockNetwork: true is set, users cannot change that network's connection or proxy settings. Public mode applies the same boundary and hides transport credentials.

Relay supports common IRCv3 capabilities; consult the IRCv3 reference and compatibility notes when a network or bouncer behaves differently.

Connection safety

  • Prefer TLS and verify the server name.
  • Store IRC service passwords only on a Relay instance you trust.
  • Use a dedicated Relay account and revoke unfamiliar sessions under Settings > Security & sessions.
  • Ask the instance administrator before changing proxy or gateway values.

IRC account authentication

The connection form separates Basics, Authentication, and Advanced in its guided flow. The server Password is for IRC server access. Under Authentication, choose Username + password (SASL PLAIN) and enter the IRC Account and Password supplied by your network; these are separate from the Relay login. Prefer TLS with Only allow trusted certificates enabled.

For Client certificate (SASL EXTERNAL), Relay generates and manages a client certificate. Register the displayed fingerprint with your network's services using that network's instructions before expecting certificate login to work. In 0.11.2, the optional Account field can select the IRC account for EXTERNAL authentication; leave it empty for the server's default certificate mapping. EXTERNAL is offered only with TLS and is not available in public mode. Advanced Commands run after connection; enter one /command per line and avoid redundant service identification if SASL already authenticates successfully.

Reconnect and diagnose

Current master adds Feature availability to Network diagnostics…, with plain-language reasons why each feature is available or unavailable on this connection. Channel permissions and server policy still apply.

A browser reconnect restores access to the persistent private account; it is separate from reconnecting the IRC transport. Unexpected IRC disconnections are retried. After an intentional Disconnect, use Connect in the network context menu (or /connect) to resume it. Use Edit this network… to correct saved settings.

Open Network diagnostics… from the network context menu and inspect Negotiated and Rejected / unavailable capabilities. This shows what this connection actually supports, rather than everything Relay knows how to request. Check the lobby for TLS, SASL and nickname errors. If the browser itself repeatedly reconnects, follow WebSocket troubleshooting.