Cuff-Link Auth Server Settings


Port: 7797
Authentication Method: SASL [Your client may say "PLAIN" or "/CAP"]
Requirements: Registered Nickname and a client that supports SASL authentication.

For clients that don’t specify a SASL Username, the regular Username/Ident and sometimes the entered nick are used as SASL Username. SSLFP/SASL External is supported as well, see this post for more info about creating a client cert and see notes on the specific clients that are known.  Note that SSLFP can be supported without being used as SASL External as well, so keep that in mind – still allows for passwordless identification but is only post-connect as opposed to during so it won’t work on the auth servers.

IMPORTANT: If you have just received one of these messages when trying to connect: Z:line, SSL handshake timeout, or dns pool — wait at least 60 minutes before trying to reconnect after altering your settings according to the instructions for your your client below.

ALSO IMPORTANT: If you receive the error “[Access denied by configuration]”, you have not properly configured SASL, you have used the wrong AccountName/UserName, you have used the wrong password, or some combination of all three.

Desktop Clients

  • Hexchat [win/*nix/BSD/mac]
  • AdiIRC [win/wine]
  • IceChat9 [win]
  • irssi [BSD/*nix/win/mac]
  • weechat [BSD/*nix/source + interfaces]
  • Quassel [*nix/mac/win + interfaces]
  • Konversation [KDE *nix]
  • BitchX [*nix/source]
  • ZNC [*nix/source]
  • mIRC [win – note this is only here to provide instructions on how to use the auth system. We do not support mIRC for troubleshooting.

Web Clients

  • IRCCloud [ios/Android/Desktop (browser & apps)]
  • KiwiIRC [ios/Android/Desktop (browser)]

Note: Both IRCCloud and KiwiIRC will work in any modern web browser on any operating system on pretty much any device – desktop machine, laptop, tablet, or phone.

Android Clients

iOS/OSX Clients

Unsupported Clients

Desktop Clients


Required fields:

server/port: or [hit <TAB> after editing to save]
Check "Use SSL for all the servers on this network"
User Name: Your registered NickServ account username. This may be your primary nickname.
Login Method: SASL (username + password)
Password: Your NickServ account password.

SSLFP/SASL External is available and detailed in this howto.


Required Fields:

Username: Your registered NickServ account username. This may be your primary nickname.
Login Method: SASL (username + password)
Password: Your NickServ account password in the Password field beneath Login Method

Ports: 6697 and/or 7797
We recommend adding 2 entries, 1 for each port.

SSLFP/SASL External is supported under the SSL tab for loading the cert and change the Login Method accordingly.


Required Fields: ‘Server port‘ updates to 6697 or 7797, verify that the “Connect with SSL” box is checked [Note: Do not check “Accept invalid SSL Certificates” – Our certificates are no longer self-signed!]; uncheck ipv6 since it seems to be acting weird.  If necessary, update the server to to force it to ipv4.

Required Fields: ‘Connect with SASL‘ checkbox will allow the next two boxes, ‘SASL user‘ is your registered nick, ‘SASL password‘ is your nickserv password.

See the howto for information on the other boxes or initial basic setup.  Note that IceChat7 does not support SASL and even IceChat9 has to be one of the latest versions, 9.13+.


Versions 0.8.18 and later have SASL built in.

/network add -sasl_username <registerednick> -sasl_password <password> -sasl_mechanism PLAIN Cuff-Link
/server add -auto -net Cuff-Link -ssl 7797

See Arch’s howto here for info on SSLFP; the mechanism will then change to EXTERNAL.


See their startup guide here and adjust as necessary per the above.  Also see the FAQ here for info on SSL server certificates.

NOTE: The server is and SSL port is 6697 or 7797.  All else is the same.


Specific server
SASL settings – Note SSLFP/SASL External is available under the identities properties


Specific server
SASL settings – Note SSLFP/SASL External is available under “Type”


Amazingly a revived project, and seems to include SASL.  Check the current wiki here.

NOTE – The server is and SSL port is 6697 or 7797.  All else is the same.


See their wiki here; there is also a link there for the SSLFP aka certfp option.  By default available on our ZNC service as well, see here.

NOTE – The server is and SSL port is 6697 or 7797.  All else is the same.


mIRC does not implement SASL as well as some other clients, and this will only work on versions 7.52 and later. To properly set this up, you must have a server entry in your server list for Cuff-Link.

  1. Open Options
  2. Click on Servers
  3. Click on your Cuff-Link entry
  4. Click on the server under Cuff-Link you want to edit
  5. Click Edit
  6. Enter server info:
    Port: +6697 or +7797
    Note: The + symbol must be entered before the number to indicate you want to use SSL.
  7. Choose SASL (/CAP) as Login Method
  8. In the SECOND password field below Login Method enter your username and password in this format:

Note: username is your NickServ account name, typically also your primary nickname.

mirc auth settings

Web Clients


IRCCloud is available via browser, iOS app, and Android app — we are putting all of the screenshots for the different versions here instead of doubling up in the iOS/Android client sections.

iOS Settings

Browser Settings

Required Fields: Tap the cog in the lower right hand corner to get to the menu and either add or edit network depending on stage.  Once in the network screen, tap ‘Network‘ and scroll down to Cuff-Link which should automatically populate the hostname, port, and SSL as shown.  Then just fill in ‘Nickname‘ as your registered nick, and ‘Nickserv‘ is your nickserv password; it will automatically default to SASL to connect.  It is highly suggested to group your automatic alternate nick which for example if your primary nick is yournick, do /nick yournick_ and use /ns group to attach it.  Reason being is irccloud doesn’t have a way to have secondary nicks, it automatically uses this method.  Just remember to use it within 90 days so it doesn’t expire.

NOTE Due to the way irccloud exists, it is not necessary to change the port from 6697 [SSL] unless wanting to specifically be on the auth servers.  Also note that the free version has a 2 hour idle timer whereas the paid version allows unlimited connectivity to the server (Connection closed for inactivity).


If the above link isn’t working:

All you have to do is enter your registered nick account user name or any nickname grouped in that account, check the “I have a password” box, type your password in and put any channels you want in the Channel box (it’ll be prefilled with #cuff-link). If you want multiple channels, do:


You can also write a link specifically for your channel joins and point it at the auth server, then all you’ll have to do is bookmark it and enter your nickname/user account in each time:,#channel,#channel

Android Clients

Most of these are a matter of editing the red sections, those are the mandatory parts that make a difference, there may be other info needed [noted below] and other settings that make your chatting experience more useful.


This is the only client that supports SSLFP that I know of, however not as SASL External.  See the howto here for some other useful details in the settings if this is your first usage.  Ad supported for free version but is only a footer banner on the startup screen.

NOTE – The difference from the howto is the port is 6697 or 7797.  All else is the same.

IRC for Android

See SimpleIrc, this is probably the closest in style.



Scroll down to click on “Authentication”.

iOS/OSX Clients

Screenshots are a bit harder to come by in this category, so most will be references.  Same information will apply:

  • Server:
  • Port: 6697 or 7797 [SSL]
  • SASL Username or Username: your registered nick
  • SASL Password: your nickserv password

Both mobile and desktop are included here since quite a few cross over, with the exception of HexChat since it is listed above.


Simply update your server to and change the port to 6697 or 7797 and verify SSL is checked.  Username must be registered nick; it will automatically use SASL.


Mobline only; Direct from Palaver’s site, their getting started how-to; it does have ZNC integration as well.


Textual will default to attempting SASL, so for many its updating a couple fields:

Required Fields:  In the general information for the server: ‘Server Address’ is or if using ipv6 [if you get odd errors, try this].  ‘Port’ is 6697 or 7797 and check ‘Connect Securely’.  Choose reconnect options if desired.  Next move down to Identity: ‘Nickname’ is your nick, ‘Username’ MUST be your registered nick, ‘Personal Password’ is your nickserv password.


See the wikihow here; most of the settings necessary will be in the advanced section.

Unsupported Clients

  • mIRC prior to version 7.52. Beyond providing the instructions on how to implement SASL authentication here, and this other post for using certificate (no password) authentication we are not supporting it for troubleshooting.
  • KVIrc – has options for using SASL, but has not had an update in over 5 years. No longer supported.
  • TurboIRC – doesn’t even handle basic authentication
  • nettalk – not in development
  • hydrairc –  not in development
  • xchat – upgrade to hexchat for the maintained fork, old confs and scripts will port
  • ByrdIRC – has a box for SASL, but does not have a way to specify port or SSL
  • Chatzilla – doesn’t have SASL at all
  • Pidgin – technically has SASL, but you’re on your own
  • Adium – same category as pidgin, doesn’t appear to be anywhere in the works
  • CIRC – shows promise for chrome, but SASL not officially listed
  • IceChat7 – not included at all
  • IceChat9* – says it has SASL, but versions prior to 9.13 don’t appear to work
  • PsyBNC – not in development, see ZNC
  • Snak – doesn’t appear to be in development
  • pirch – no. Just. No.
  • vortex – pirch fork, see above.
  • ircII – well they did add SSL in 2014, but no SASL.  There may be forks
  • LeafChat – not in development
  • KiwiIRC – cannot use the port needed for authorisation settings.
  • rooms – website says in development, feature list doesn’t include SASL
  • AndChat – no longer in active development.
  • Mutter – no longer in active development – as it stands now, it can do SASL and authenticate properly, but it’s now unsupported as the project is now shut down.
  • Hermes – no longer available.
  • Atomic – no longer available.
  • SimpleIRC – no longer available.
  • Mibbit – does not implement SASL correctly — On November 15, 2019, Mibbit will no longer be able to connect to Cuff-Link.

Leave a comment

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.

3 thoughts on “Cuff-Link Auth Server Settings”