Communication Applications

IRC (Internet Relay Chat) remains a critical communication protocol for open-source communities, private tracker announce channels, developer teams, and technical support. QuickBox Pro provides three powerful IRC solutions—each designed for different use cases and preferences.

Available Applications

The Lounge

Modern, self-hosted web IRC client with responsive design and always-online experience. Access IRC from any device through your browser with persistent connections and message history.

View documentation →

Quassel

Distributed IRC client with separate core and client components. Persistent IRC connections with multi-platform desktop clients and synchronized message history.

View documentation →

ZNC

Advanced IRC bouncer (BNC) that maintains persistent connections. Connect multiple clients simultaneously with message buffering and web-based administration.

View documentation →

Choosing the Right Solution

Each IRC solution serves different needs and preferences. Understanding the differences helps you select the best option for your workflow.

Quick Comparison

Feature	The Lounge	Quassel	ZNC
Interface	Web Browser	Desktop Client	Any IRC Client
Installation	None (browser only)	Client app required	Client app required
Access Method	Any device with browser	Desktop/mobile apps	Traditional IRC clients
Best For	Convenience, mobile	Power users, features	Existing IRC workflows
Complexity	Low	Medium	Medium-High
Setup Time	< 5 minutes	10-15 minutes	15-20 minutes

Detailed Recommendations

The Lounge

Choose if: You want instant access from any device without installing software. Perfect for users who value convenience and modern web interfaces.

Quassel

Choose if: You prefer native desktop applications with advanced features. Ideal for power users who want synchronized multi-device access.

ZNC

Choose if: You already use an IRC client and want persistent connections. Perfect for users with existing IRC workflows and tools.

Not Sure Which to Choose?

Start with The Lounge if you’re new to IRC—it’s the easiest to set up and use. You can always install additional solutions later as your needs evolve. All three can run simultaneously on QuickBox.

Installation

Install any IRC solution from the App Dashboard → Package Management panel (/dashboard?mode=packages): browse the Communication category or search for the app, then click Install. The dashboard streams the install log live and the app appears in your Application Control panel when it finishes. Reinstall, Update, and Remove live on the same panel. QuickBox configures SSL certificates, nginx reverse proxies, and systemd services automatically.

The install dialog inputs differ per app: The Lounge offers a Stable / Beta channel selector; ZNC prompts for its port, SSL, identity, and an optional starter IRC network; Quassel has no options to pick. 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, and each app’s page for its install-dialog inputs.

The CLI runs the same install scripts and suits automation:


qb install thelounge -u username          # web-based
qb install thelounge -u username --beta   # web-based, beta channel
qb install quassel -u username            # distributed core
qb install znc -u username                # IRC bouncer

Manage any installed IRC app the same way — replace <application> with thelounge, quassel, or znc:


qb update <application> -u username       # update to latest version
qb reinstall <application> -u username    # reinstall (preserves configuration)
qb remove <application> -u username       # remove the application
qb help <application>                     # view help

Full flag reference: CLI Reference.

Private Tracker Integration

IRC announce channels are the most common QuickBox use case for these apps. Pair a persistent IRC solution with an automation tool to download from tracker announces:

Symptoms

Need to monitor IRC announce channels 24/7
Want automated downloading from tracker announces
Must respond quickly to new uploads
Require reliable announce monitoring without gaps

Resolution

Install The Lounge or Quassel for persistent IRC connections
Configure announce channels with proper authentication
Integrate with autobrr or autodl-irssi for automated downloads
Set up highlights and notifications for important announces

Recommended Setup:

IRC Client: The Lounge or Quassel for 24/7 monitoring
Automation: Autobrr for intelligent announce parsing
Configuration: SASL authentication and SSL/TLS connections

Integration & Automation

IRC applications integrate seamlessly with QuickBox automation tools:

Autobrr Integration

Autobrr monitors IRC announce channels and automatically downloads matching content:

Install IRC solution for persistent monitoring
Configure announce channels with proper authentication
Install and configure Autobrr with IRC credentials
Define filters for automated content matching
Sit back as new releases download automatically

Autodl-irssi Integration

Autodl-irssi provides similar automation for traditional workflows:

Legacy tool still maintained for compatibility
Supports extensive tracker announce formats
Integrates with torrent clients for automatic downloading
Alternative to Autobrr for users preferring irssi

Best Practices

Do

Use SASL authentication when supported by IRC networks
Enable SSL/TLS connections (port 6697) for secure communication
Configure auto-join for important channels to reconnect automatically
Set up highlights for your nickname and important keywords
Back up configuration files regularly (especially for ZNC)
Use strong, unique passwords for IRC services and bouncers
Configure proper away messages for when you're unavailable
Test notifications to ensure you receive important alerts

Don't

Don't use plain text connections when SSL/TLS is available
Don't share IRC credentials or bouncer login details
Don't flood channels with automated messages—use rate limiting
Don't ignore channel rules and etiquette guidelines
Don't use the same password across multiple IRC networks
Don't leave debug logging enabled in production environments
Don't expose bouncer admin interfaces without authentication
Don't install untrusted ZNC modules from unknown sources

Security Considerations

Connection Security

Always Use Encryption

Enable SSL/TLS for all IRC connections. Modern IRC networks support encrypted connections on port 6697. Unencrypted connections expose your messages and credentials to network monitoring.

Security Checklist:

✅ Use SSL/TLS connections to IRC networks (port 6697)
✅ Enable SASL authentication when supported
✅ Use strong, unique passwords for each service
✅ Keep IRC client software updated
✅ Configure firewall rules appropriately
✅ Use certificate authentication where possible (ZNC)
✅ Review and audit installed modules/plugins
✅ Monitor access logs for suspicious activity

Authentication Methods

SASL (Simple Authentication and Security Layer):

Authenticates before joining channels
Prevents nickname hijacking
Supported by major networks (Libera.Chat, OFTC)
Configured in client network settings

NickServ Authentication:

Traditional username/password authentication
Requires identifying after connection
Fallback when SASL is unavailable

Certificate Authentication (ZNC):

SSL client certificates for enhanced security
No password transmission over network
Recommended for advanced users

Troubleshooting

Common Issues

Verify network address and port are correct
Ensure SSL/TLS is enabled for secure ports (6697)
Check firewall allows outbound IRC connections
Confirm authentication credentials are valid

Review logs with:

journalctl -u servicename@username -n 50

Check service status:

systemctl status servicename@username

Verify permissions on config directories
Review error logs for specific issues

Try reinstalling:

qb reinstall servicename -u username

Check database permissions and disk space
Verify backup directories exist
Review log rotation settings
Reinstalling typically preserves config where possible

Service Management

Each IRC service runs under systemd. Replace <service> with thelounge, znc, or quasselcore:


systemctl status <service>@username     # check status
journalctl -u <service>@username -f     # view logs
systemctl restart <service>@username    # restart service