Skip to Content
Quassel

Quassel IRC

Modern distributed IRC client with persistent connections

Quassel IRC

Quassel IRC is a modern, cross-platform, distributed IRC client based on the Qt framework. Unlike traditional IRC clients, Quassel uses a unique client-server architecture where the core (server) stays connected to IRC networks 24/7, while multiple clients can connect and disconnect at will without losing your IRC connection.


What is Quassel IRC?

Quassel IRC is a distributed IRC client that separates the core functionality from the user interface. The Quassel Core runs continuously on your QuickBox server, maintaining persistent IRC connections, while Quassel Client applications can connect from any device to access your IRC sessions.

Distributed Architecture

Core stays connected 24/7 while clients connect/disconnect freely from any device

Persistent Backlog

Never miss messages—complete conversation history stored while you're disconnected

SSL/TLS Security

Automatic SSL certificate generation for secure client-to-core communication

Multi-Client Support

Connect from desktop, laptop, mobile—all clients share the same session state

Modern Interface

Beautiful Qt-based UI with customizable themes and advanced features

IPv4/IPv6 Support

Dual-stack network support for modern IRC connectivity

How Quassel Works
Info

Quassel operates as two components: Quassel Core (server) runs on your QuickBox installation and maintains IRC connections, while Quassel Client (desktop/mobile app) connects to the core to access your IRC sessions from anywhere.


Installation

Install from the Dashboard

Open App Dashboard → Package Management (/dashboard?mode=packages), find Quassel in the Communication category (or search), and click Install. Quassel has no options to pick — the install dialog runs straight through, generating SSL certificates and starting the core. The dashboard streams the install log live. Reinstall and Remove are in the same Package Management panel. To update, use the amber Update badge on the Quassel row in the App Dashboard.

What you see is gated by your account: admins manage any user’s apps, regular users manage their own. See App Management for the full flow. After the core is running, install the Quassel client on your devices to connect (covered below).

Install from the CLI (automation)

The CLI runs the same script and suits automation:

bash
qb install quassel -u username
qb reinstall quassel -u username
qb update quassel -u username
qb remove quassel -u username
qb help quassel

Full flag reference: CLI Reference.


Configuration

Default Settings

Quassel Core is configured with the following defaults:

Configuration Files
Path
Description
/home/username
.config/Quassel/
quasselcore.conf
Core configuration file
logs/
core.log
Main core log file
quassel-storage.sqlite
Message and configuration database
.ssl/
quasselCert.pem
SSL certificate for secure connections
cacert.pem
Certificate authority bundle
System Configuration
Path
Description
/etc/default
quasselcore
Environment configuration file

Environment Configuration

Quassel Core uses environment variables defined in /etc/default/quasselcore:

bash
# Log Level: Debug|Info|Warning|Error
LOGLEVEL="Info"
 
# Log file location
LOGFILE="/home/username/.config/Quassel/logs/core.log"
 
# Port for client connections (default: 4242)
PORT="4242"
 
# Network addresses to listen on (IPv6 and IPv4)
LISTEN="::,0.0.0.0"
 
# Data directory
DATADIR="/var/lib/quassel"

Port Configuration

By default, Quassel Core listens on port 4242. QuickBox automatically handles:

  • Port availability checking
  • Automatic port assignment if default is in use
  • Firewall rule configuration
  • Database port registration
Firewall Configuration
Warning

Ensure port 4242 (or your custom port) is accessible through your firewall if connecting from external networks. QuickBox configures local access automatically.

Check your assigned port:

bash
cat /etc/default/quasselcore | grep PORT

Allow port through UFW firewall:

bash
# Allow from specific IP
ufw allow from 203.0.113.50 to any port 4242
 
# Allow from anywhere (not recommended)
ufw allow 4242/tcp

Advanced Configuration

Customize log level:

bash
# Edit environment file
nano /etc/default/quasselcore
 
# Change LOGLEVEL (Debug|Info|Warning|Error)
LOGLEVEL="Debug"
 
# Restart service
systemctl restart quasselcore

Change listening addresses:

bash
# Edit environment file
nano /etc/default/quasselcore
 
# Listen only on IPv4
LISTEN="0.0.0.0"
 
# Listen only on IPv6
LISTEN="::"
 
# Listen on both (default)
LISTEN="::,0.0.0.0"
 
# Restart service
systemctl restart quasselcore

Connecting to Quassel Core

Accessing Your Quassel Core

After installation, you’ll need the Quassel Client application to connect to your core. Unlike web-based IRC clients, Quassel requires a desktop or mobile application.

Download Quassel Client

Choose Your Platform
Tip

Quassel Client is available for all major platforms. Download the appropriate version for your operating system.

Desktop Clients:

PlatformInstallation Method
Linux (Debian/Ubuntu)apt install quassel-client
Linux (Fedora/RHEL)dnf install quassel-client
WindowsDownload from quassel-irc.org 
macOSbrew install quassel-client or download from website

Mobile Clients:

PlatformApplicationStore Link
AndroidQuasseldroidGoogle Play Store 
iOSQuassel for iOSApp Store 

First-Time Connection Setup

Step 1: Launch Quassel Client

Open the Quassel Client application on your device.

Step 2: Add Core Account

  1. Click “Add Core Account” or navigate to connection settings
  2. Enter your connection details:
plaintext
Core Account Name: My QuickBox Server
Hostname:          your-server.com (or IP address)
Port:              4242
  1. Enable “Use Secure Connection (SSL)” ✓

Step 3: Accept SSL Certificate

Certificate Verification
Important

On first connection, you’ll be prompted to accept the SSL certificate. This is normal for self-signed certificates. Verify the certificate fingerprint if security is critical.

To verify certificate fingerprint on your server:

bash
openssl x509 -in ~/.ssl/quasselCert.pem -noout -fingerprint -sha256

Step 4: Create User Account

Since this is your first connection, you’ll create the initial admin account:

  1. Click “Add User”
  2. Enter username and strong password
  3. This becomes your Quassel Core account (separate from IRC networks)

Step 5: Add IRC Networks

Configure IRC networks you want to connect to:

  1. Right-click on your identity → “Configure Networks”

  2. Click “Add” to create a new network

  3. Common IRC networks:

    Libera.Chat
    irc.libera.chat:6697 (SSL)
    OFTC
    irc.oftc.net:6697 (SSL)
    IRCnet
    irc.ircnet.com:6667
  4. Configure authentication (if required by network)

  5. Set auto-join channels

Connected!
Success

Once configured, your Quassel Core maintains persistent IRC connections 24/7. You can now close the client and reconnect anytime without losing your IRC session!

Connection Settings Reference

Required Connection Parameters:

ParameterValueNotes
HostnameYour server IP or domainExample: server.example.com
Port4242 (default)Check /etc/default/quasselcore if custom
SSL/TLSEnabled (required)Always use SSL for security
AccountCreated on first connectionSeparate from IRC network accounts

Find your assigned port:

bash
cat /etc/default/quasselcore | grep "^PORT="

Multiple Client Connections

One of Quassel’s key features is multi-client support:

  • Connect from desktop, laptop, tablet, and phone simultaneously
  • All clients share the same conversation state
  • Read/unread status syncs across all devices
  • Disconnect any client without losing IRC connection

Example use case:

  1. Connect from desktop at work
  2. Disconnect and connect from phone during commute
  3. Resume from laptop at home
  4. All conversations and history available everywhere

Service Management

Quassel Core runs as a systemd service for reliable operation:

Basic Service Commands

Check service status:

bash
systemctl status quasselcore

Start service:

bash
systemctl start quasselcore

Stop service:

bash
systemctl stop quasselcore

Restart service:

bash
systemctl restart quasselcore

Enable service (start on boot):

bash
systemctl enable quasselcore

Disable service:

bash
systemctl disable quasselcore

Viewing Logs

View service logs:

bash
journalctl -u quasselcore -f

View core log file:

bash
tail -f /home/username/.config/Quassel/logs/core.log

Check last 100 log entries:

bash
journalctl -u quasselcore -n 100

Features

Core Features

Message Backlog

Complete conversation history stored in SQLite database with efficient retrieval

Multi-User Support

Create multiple user accounts for different team members or use cases

Network Management

Connect to multiple IRC networks simultaneously with independent configurations

Channel Buffers

Organized channel and query buffers with unread message tracking

Smart Notifications

Customizable highlight rules and notification settings per channel

Secure Authentication

PostgreSQL or SQLite backend with encrypted password storage

Client Features

When connected via Quassel Client:

  • Cross-Platform: Windows, macOS, Linux, and mobile clients
  • Synchronized State: All clients share the same read/unread status
  • Rich Interface: Context menus, keyboard shortcuts, and customizable layouts
  • Advanced Search: Full-text search across conversation history
  • Identity Management: Multiple nicknames and authentication methods
  • File Transfers: DCC send/receive with resume support

Directory Structure

Quassel stores configuration and data in user-specific directories:

User Configuration
Path
Description
/home/username
.config/Quassel/
quasselcore.conf
Main configuration
quassel-storage.sqlite
Message database
logs/
core.log
Runtime logs
.ssl/
quasselCert.pem
SSL certificate
cacert.pem
CA bundle
System Files
Path
Description
/
var/lib/quassel/
Additional data storage
etc/default/quasselcore
Service environment

Back up and restore

QuickBox backs Quassel up for you from the dashboard or the CLI, and Quassel keeps running while it does. Every backup is saved to /home/username/.QuickBox/software/quassel/backup/, named with the version and the date.

BackupWhat it saves
Config Onlyquasselcore.conf, the core’s configuration file. It does not hold your message history
Full BackupOne archive, quassel-<version>-config_<date>.tar.gz, of /home/username/.config/Quassel/ without its logs folder. That folder holds links to the files the core keeps in /var/lib/quassel/, not copies of them, so the archive does not hold the message database quassel-storage.sqlite

From the dashboard: open the App Dashboard, stay on Application Control, expand the Quassel row (click the row, or the arrow beside the app name, to open its options), open Operations and click Backup, then choose Full backup or Config Only. You can also open Content → Asset Management Center (AMC in the sidebar), choose the Application Backups tab, expand the Quassel row and click Back up now; that row lists every saved file with download and delete buttons. See App Management → Application Backups for who can see the tab.

To roll back from the dashboard: open the App Dashboard, stay on Application Control, expand the Quassel row, open Operations, click Restore, pick the backup, then click Rollback and confirm. Restore appears only when your account is allowed to restore backups. A Config Only or Nginx Only backup shows Restore instead of Rollback and puts back just that file.

From the CLI:

bash
# Config Only: quasselcore.conf
qb manage software -o backup -u username -s quassel
 
# Full Backup: the config folder (not the message database)
qb manage software -o backup -o app -u username -s quassel
 
# Roll back to a Full Backup: pick the version from a menu, then confirm
qb manage software -o rollback -o app -u username -s quassel

Every option is described in the qb manage reference.

Quassel Core runs from a system-wide package shared by every account, so there is no install tree of yours to save and the Full Backup is a single config archive. The dashboard still lists it with Rollback, and a rollback stops Quassel for your account, puts the config folder back and starts Quassel again.

Copy the message database yourself. Because the Full Backup does not hold /var/lib/quassel/quassel-storage.sqlite, copy that file before major updates or system changes. Stop the core first so the copy is consistent, then start it again:

bash
sudo systemctl stop quasselcore
sudo cp /var/lib/quassel/quassel-storage.sqlite ~/quassel-saved.sqlite
sudo systemctl start quasselcore

To put the copy back, follow the steps under Database Corruption in Troubleshooting.

Remove and reinstall delete your backups
Caution

qb remove quassel and qb reinstall quassel both delete /home/username/.config/Quassel/, /var/lib/quassel/ (where the core keeps its message database), your certificate /home/username/.ssl/quasselCert.pem, and the backup folder /home/username/.QuickBox/software/quassel/ with every backup in it, and clear the rollback list. Copy the message database first, as described above. Before either one, download the Full Backup from the Application Backups tab of the Asset Management Center.


Troubleshooting

Common Issues & Solutions

Check Logs First
Warning

Most Quassel issues can be diagnosed by checking systemd logs with journalctl -u quasselcore -n 100. Always review logs before making configuration changes.

Service Won’t Start

Symptoms

  • systemctl start quasselcore fails or service immediately stops

Solutions

  • Check service status: systemctl status quasselcore
  • Review logs: journalctl -u quasselcore -n 50
  • Verify permissions: ls -la /home/username/.config/Quassel/
  • Check port availability: ss -tlnp | grep 4242
  • Reinstall if corrupted: qb reinstall quassel -u username

Client Connection Refused

Symptoms

  • Quassel client cannot connect to core, timeout errors

Solutions

  • Verify service is running: systemctl is-active quasselcore
  • Check port is listening: netstat -tlnp | grep 4242
  • Test local connection: telnet localhost 4242
  • Verify firewall rules: ufw status or iptables -L
  • Check client SSL settings match server configuration

SSL Certificate Errors

Symptoms

  • Certificate verification failed, untrusted certificate warnings

Solutions

  • Verify certificate exists: ls -la ~/.ssl/quasselCert.pem
  • Check certificate validity: openssl x509 -in ~/.ssl/quasselCert.pem -noout -dates
  • Regenerate certificate: qb reinstall quassel -u username
  • Accept certificate in client (verify fingerprint first)

Database Corruption

Symptoms

  • Core crashes on startup, SQLite errors in logs

Solutions

  • Stop service: systemctl stop quasselcore
  • Keep a copy of the damaged database: sudo cp /var/lib/quassel/quassel-storage.sqlite ~/quassel-damaged.sqlite
  • Restore your own saved copy over it: sudo cp ~/quassel-saved.sqlite /var/lib/quassel/quassel-storage.sqlite
  • Fix ownership: sudo chown quasselcore: /var/lib/quassel/quassel-storage.sqlite
  • Start service: systemctl start quasselcore

Service Health Checks

Verify core is running:

bash
systemctl is-active quasselcore

Check port listening:

bash
ss -tlnp | grep 4242

Test local connection:

bash
telnet localhost 4242

Verify SSL certificate:

bash
openssl x509 -in ~/.ssl/quasselCert.pem -text -noout

Best Practices

Do

  • Use strong, unique passwords for each Quassel user account
  • Enable SSL/TLS for all client-to-core connections
  • Regularly copy the database from /var/lib/quassel/ (QuickBox Full Backup archives ~/.config/Quassel, which holds links to the core data and does not hold a copy of the database)
  • Monitor logs periodically with journalctl -u quasselcore
  • Keep Quassel Core updated via qb update quassel command
  • Restrict port 4242 access via firewall to known IP addresses
  • Use dedicated IRC networks for different purposes (work, personal, etc.)
  • Configure proper certificate verification in client settings

Don't

  • Don't use default or weak passwords for user accounts
  • Don't expose Quassel Core port directly to the internet without firewall rules
  • Don't disable SSL/TLS for client connections—always encrypt traffic
  • Don't ignore systemd service failures—investigate with journalctl
  • Don't manually edit the SQLite database—corruption risk
  • Don't share user credentials across multiple people
  • Don't run Quassel Core as root user—let QuickBox manage permissions
  • Don't forget to copy /var/lib/quassel/quassel-storage.sqlite before major updates or system changes

Security Recommendations

  • Use strong passwords for Quassel user accounts
  • Enable SSL/TLS for all client connections
  • Restrict port access via firewall to known IPs
  • Regular updates to address security vulnerabilities
  • Monitor connections via logs and systemd status

When to Use Quassel

Symptoms

  • Need 24/7 IRC presence without keeping computer on
  • Want to access IRC from multiple devices (desktop, laptop, mobile, tablet)
  • Missing messages when disconnected from IRC networks
  • Managing multiple IRC networks and channels becomes cumbersome
  • Team needs centralized IRC communication platform
  • Require complete conversation history and backlog
  • Need advanced features like highlights, notifications, and rich formatting

Resolution

  • Install Quassel Core on QuickBox server for persistent connections
  • Connect multiple Quassel clients simultaneously from any device
  • Complete message backlog automatically stored in SQLite database
  • Single core manages all networks, channels, and identities
  • Distributed architecture enables team collaboration with shared core
  • Full conversation history with efficient search and retrieval
  • Modern Qt-based UI with customizable themes and advanced IRC features
Not Ideal For
Warning

Quassel may not be the best choice if you need web-only access (requires desktop/mobile client installation), single-user occasional IRC usage (consider The Lounge for simpler web-based access), or public IRC servers without authentication.


Additional Resources


Quassel IRC works well alongside these QuickBox Pro communication tools:

Security Tools

1

Monitoring

1

Join the Community

Media server operators sharing configs, getting support, and shaping the future of QuickBox Pro.

  • Dedicated Support
  • Feature Previews
  • Community Configs
  • Active Discussions
Join Discord Server
Last updated on