Learn how to connect your IRC client to Eggy BNC using /server -m, what the command does, and how to troubleshoot common connection and SSL certificate issues.
Eggy BNC is designed to make connecting to your IRC bouncer as simple as possible. Once your account is created, your dashboard gives you the connection details you need to attach your IRC client to your BNC.
One of the quickest ways to connect from many IRC clients is by using the /server -m command.
What /server -m does
The /server command tells your IRC client to connect to a server.
The -m option usually means “open this as a new server connection” instead of replacing your current IRC connection.
That is useful if you are already connected to another IRC network and want to connect to Eggy BNC at the same time.
In simple terms:
/server connects to a server.
-m opens it as an additional connection.
+6697 means use SSL/TLS on port 6697.
Your BNC username and password tell Eggy BNC which account to attach.
Basic Eggy BNC connection example
Your dashboard should show your exact connection command. Always use the command shown there if it is available.
A typical command looks like this:
/server -m bnc.eggy.net +6697 your-username
Replace:
your-username with your Eggy BNC username
your-password with your Eggy BNC password
If your dashboard gives you a slightly different command, use the dashboard version. Some clients handle usernames and passwords differently, so the dashboard command is the safest source.
Why the plus sign matters
The plus sign before the port is important:
+6697
This tells many IRC clients to use SSL/TLS.
Without the plus sign, your client may try to connect without SSL. That can fail, or it can connect in a way you did not intend.
Use:
/server -m bnc.eggy.net +6697 username
Not:
/server -m bnc.eggy.net 6697 username
The second version may not enable SSL in some clients.
Use the hostname, not the IP address
For SSL to work cleanly, connect using:
bnc.eggy.net
Do not connect using the raw server IP unless you know exactly what you are doing.
SSL certificates are issued for hostnames, not random client-side labels. If you connect to an IP address, your IRC client may complain that the SSL certificate name does not match.
Correct:
/server -m bnc.eggy.net +6697 username
Avoid:
/server -m 77.68.125.117 +6697 username
If you use the IP address, an SSL certificate warning is expected because the certificate is for the hostname.
What happens after connecting
When the command works, your IRC client connects to Eggy BNC.
Your BNC account then attaches to your configured IRC network.
Depending on your account and network settings, you may see:
Your BNC status messages
Your IRC network connecting
Channels joining automatically
Messages from NickServ or network services
Existing channel activity if your BNC has remained connected
If nothing appears immediately, give it a few seconds. Some IRC networks take longer to connect than others.
Troubleshooting
Connection refused
If your client says connection refused, check:
You are using the correct hostname: bnc.eggy.net
You are using the correct port: +6697
You included the plus sign for SSL
Your internet connection is working
You did not mistype the server name
Correct example:
/server -m bnc.eggy.net +6697 username
SSL certificate warning
If your IRC client shows an SSL certificate warning, check that you are connecting to:
bnc.eggy.net
Do not use an IP address.
Do not use an old hostname.
Do not use a misspelled hostname.
A certificate warning can also happen if your computer has an incorrect date or time. SSL certificates depend on your system clock, so check your device time if the warning looks strange.
If the hostname is correct and your clock is correct, try reconnecting. If the warning continues, open a support ticket and include the exact warning text.
Unable to verify certificate
Some older IRC clients may not have an up-to-date certificate store. If your client is very old, it may fail to verify modern SSL certificates properly.
Try:
Updating your IRC client
Using a newer client
Checking your client’s SSL settings
Connecting with the exact dashboard command
You should not normally need to disable SSL verification. If you are unsure, ask for support first.
Invalid password
If the client says your password is wrong, check:
You copied the full password
There are no extra spaces before or after it
Your username is correct
Your password has not recently been changed
You are using the correct format shown in the dashboard
If you changed your dashboard password recently, remember that your BNC password may also have changed. Use the newest connection details from the dashboard.
Wrong username
If your username is wrong, the BNC will not know which account you are trying to attach to.
Use the username shown in your Eggy BNC dashboard.
Do not guess the username.
Do not use your IRC network nickname unless it is the same as your BNC username.
Connected to BNC but not the IRC network
If your client connects to Eggy BNC but your IRC network does not connect, the BNC connection itself is working. The issue is likely your network settings.
Check your dashboard network settings:
IRC server address
Port
SSL setting
Nickname
Network enabled/connected state
If you edited the network recently, reconnect it from the dashboard.
Channels do not auto-join
If your BNC connects but your channels do not appear, check whether auto-join is configured.
You can also try joining manually:
/join #channelname
If manual join works, the BNC connection is fine and the issue is only your channel auto-join setup.
The command opens a new connection but disconnects another one
The -m option is meant to open a new server connection in many IRC clients. If your client behaves differently, check that your client supports /server -m.
Some clients use different command formats.
If /server -m does not work in your client, use the connection form/settings screen instead and enter:
Server: bnc.eggy.net
Port: 6697
SSL/TLS: enabled
Username/password: from your Eggy BNC dashboard
Using Web Chat instead
If you do not want to configure an IRC client yet, you can use Web Chat from the Eggy BNC dashboard.
Web Chat opens your BNC session in the browser. It is useful for quick access, testing, or connecting from a device where you do not want to install an IRC client.
A normal IRC client is still recommended if you want a permanent desktop setup, scripts, local logs or advanced customisation.
Quick checklist
Use bnc.eggy.net
Use +6697
Use the exact username and password from your dashboard
Use the plus sign to enable SSL
Avoid connecting by IP address
Check your network settings if the BNC connects but IRC does not
Use Web Chat if you want quick browser access
Need help?
If you still cannot connect, open a support ticket from the Eggy BNC dashboard.
Include:
Your BNC username
The IRC client you are using
The command format you tried, without showing your password
The exact error message
Whether Web Chat works
This makes it much easier to diagnose the issue without exposing your password.