DWShells
Customer Panel
← All guides

IRC apps / 7 min READ

Set up and connect to ZNC

Create a managed bouncer, connect your IRC client and understand the two network connections.

Reviewed 6 October 2026 · DarkWorld Network · Applies to the selected shell’s effective permissions

Detailed wiki guide ↗
ZNC has two separate connections Workflow illustration
  1. 01Your IRC client

    Connects inbound using ZNC login and assigned listener port.

  2. 02Your ZNC

    Runs on the shell and keeps its network session.

  3. 03IRC network

    Receives the outbound connection on its server port.

Check permissions and ports

Create a managed instance

  1. Open the ZNC manager

    In Packages, choose ZNC. If an existing instance is already configured, inspect its details instead of running setup again.

  2. Enter the ZNC identity

    Choose the ZNC username, IRC nickname and a separate ZNC password of at least 14 characters. Confirm the password.

  3. Choose the IRC network

    Enter a network name and a permitted IRC server. DarkWorld community connections use irc.darkworld.chat with TLS on 6697. Keep Use TLS to IRC server enabled for that connection. Other networks must meet shell network policy.

  4. Set up and start

    Use Set up and start ZNC. The portal chooses an available assigned listener port. Wait for the result, then check status and View logs.

Connect your IRC client

Use the Client connection details shown by the manager: hostname/address, listener port, TLS setting and login. The displayed login can include the network, such as ZNC_USERNAME/NETWORK_NAME. Use the ZNC password, not the shell or dashboard password.

What you seeWhat to do
Client → ZNCYour assigned application listener port, shown in Packages. Use the displayed SSL/TLS setting.
ZNC → IRC networkThe network server’s port, for example TLS 6697. This is not your allocated listener port.
IPv4 inboundUse only a connection marked IPv4 forwarding confirmed. Otherwise follow the IPv6 details or contact staff.
Free outboundIRC connections use assigned IPv6. IPv4 access from your client does not change that policy.
Other plans outboundManaged configuration prefers assigned IPv6 with permitted IPv4 fallback.

TLS and the web interface

Match the displayed hostname to the certificate. Verify a fingerprint when the portal supplies one; do not disable certificate verification to hide a warning. Use Open ZNC web only when the manager shows it. “Web Access is not enabled” means the web interface is not available, not necessarily that the IRC listener is down.

Manage or replace ZNC

Use Start, Stop, Restart and View logs. Install fresh and Delete ZNC are destructive: stop first and make an independent copy of needed settings. The confirmation removes configuration, credentials, logs and scripts. Install fresh reopens setup; it is not a repair that preserves your existing account.

Troubleshooting

What you seeWhat to do
Client cannot connectCheck assigned listener port, TLS and forwarding status, then the running state and logs.
Client connects, network is offlineCheck IRC server, server port, TLS, permitted destinations and IPv6 support on Free.
Login rejectedUse the displayed ZNC login and ZNC password. Network names matter.
No available portReview existing app reservations and your allocation; ask staff before changing ports.

Read this topic in the wiki ↗ · Documentation hub ↗

Reference and help

Checked against the current customer-panel implementation and DWShells signup and rules. For assigned values and eligibility, use your dashboard. Need help? Join #DWShells on DarkWorld IRC or contact staff. Do not send credentials.

CONTINUE LEARNINGCreate and manage an Eggdrop bot →