How to connect using bnc.eggy.net +5000

Your IRC client connects to Eggy BNC using the secure listener:

bnc.eggy.net +5000

The plus sign matters. In IRC client and ZNC-style port fields, a plus sign before the port means SSL/TLS should be used. Eggy BNC expects a secure client connection on port 5000.

A normal connection command looks like this:

/server -m bnc.eggy.net +5000 username/Network:password

Replace username with your Eggy BNC username, Network with the network label shown in your dashboard, and password with your Eggy BNC password.

Do not use plain 5000

This is wrong for Eggy BNC:

/server -m bnc.eggy.net 5000 username/Network:password

Plain 5000 can cause connection aborts or TLS errors because the listener expects SSL/TLS.

Client examples

For mIRC, the command format is usually:

/server -m bnc.eggy.net +5000 username/Network:password

If your client has a separate server password field, use:

username/Network:password

For HexChat, enable SSL/TLS for the server entry and use bnc.eggy.net on port 5000. For WeeChat, a typical setup is:

/server add eggybnc bnc.eggy.net/5000 -ssl
/set irc.server.eggybnc.password username/Network:password
/connect eggybnc

Two different ports

Your client-to-BNC connection is always the Eggy BNC connection. The BNC-to-network connection is configured separately. For example:

Eggy BNC listener: bnc.eggy.net +5000
Remote IRC network: irc.example.net +6697
Remote IRC network: irc.example.net 6667

Do not replace bnc.eggy.net +5000 with the remote IRC network address in your client unless you intentionally want to bypass the BNC.

If it fails

Check the plus sign before 5000, the username/network/password format, your SSL/TLS client setting, and the exact network label. If it still fails, open a support ticket with the exact error text.