Understanding your connect command

A typical Eggy BNC command looks like this:

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

Every part has a purpose.

`/server -m`

Many IRC clients use /server to open a server connection. The -m option often means “open a new server connection” instead of replacing your current one. Some clients use a different interface, but the server, port, SSL setting, and password are still the important parts.

`bnc.eggy.net`

This is the Eggy BNC hostname. Your IRC client connects here first. Eggy BNC then connects to the IRC networks configured in your account.

`+5000`

This is the secure Eggy BNC listener port. The plus sign means SSL/TLS. If your client uses a checkbox instead of a plus sign, enable SSL/TLS and use port 5000.

`username/Network:password`

This is the server password format. It contains:

username
Network
password

The network label selects which ZNC network context to attach to. If you have more than one user-managed network, the /Network part matters.

For example:

dan/Libera:my-password
dan/DALnet:my-password

Both use the same Eggy BNC account but attach to different network contexts.

Common mistakes

Do not put your NickServ password here unless your Eggy BNC password is intentionally the same. The BNC server password logs you into Eggy BNC.

Do not leave out the network label if your account has multiple networks. Without it, the client may attach to the wrong context or fail.

Do not replace bnc.eggy.net with the remote IRC network hostname. The remote IRC network is configured inside the dashboard.

Source of truth

The dashboard and signup success screen are the safest places to copy the exact command. If you are unsure, copy the generated command again instead of rebuilding it from memory.