- 1 Compiling ZNC
- 1.1 General
- 1.1.1 The compiler dies saying it has not enough memory! / g++: internal compiler error: Killed (program cc1plus)
- 1.1.2 configure: error: pkg-config could not find znc (znc.pc)
- 1.1.3 Upgrade your compiler. GCC 4.7+ and Clang 3.2+ are known to work.
- 1.1.4 Upgrading / updating from a previous release, to a new version
- 1.1.5 Do I have to shut down and restart ZNC during an upgrade to a new version?
- 1.2 BSD
- 1.3 Debian
- 1.1 General
- 2 Starting ZNC
- 3 Using ZNC
- 3.1 ZNC dies when I power off the device it's running on!
- 3.2 How do I tell ZNC which network/server a channel belongs to?
- 3.3 How to use multiple networks like with psybnc?
- 3.4 I added several different servers, but ZNC connects only to one of them!
- 3.5 How do I choose which IP to use for connecting to IRC?
- 3.6 How do I add a new user?
- 3.7 Connecting with mIRC
- 3.8 Connecting with Eggdrop
- 3.9 I got banned from #channel and ZNC keeps trying to rejoin
- 3.10 How to use the loaded modules?
- 3.11 I keep getting kicked for flood when I ...
- 3.12 Every time I connect to my BNC, I see the channel buffers from the last time I connected!
- 3.13 What are BINDHOSTS and why can't I make mine work?
- 3.14 I get 'Could not find znc-config. Please (re)install' when using znc-buildmod
- 3.15 I keep getting a lot of stuff like /who replies when connected with multiple clients to one znc-user
- 3.16 How can I access webadmin with my browser?
- 3.17 My IRC-Client doesn't allow multiple connections to one server/host
- 3.18 How to reload ZNC config without restart?
- 3.19  Software caused connection abort
- 3.20 How to store private messages even when user is attached, so other clients can see them?
- 3.21 Networks
- 3.22 How much memory does ZNC need to run?
- 3.23 My NickServ password is stored in plaintext!
- 3.24 Why does ZNC connect with my altnick?
- 3.25 How can I make ZNC disconnect when I'm not using it?
- 3.26 I forgot my password! How do I reset my ZNC password?
- 3.27 How do I reload znc.pem?
- 4 Troubleshooting
The compiler dies saying it has not enough memory! / g++: internal compiler error: Killed (program cc1plus)
Starting from ZNC 0.062, you can use the
--disable-optimization to configure. This will disable
-O2 and instead use
-O0". GCC should need less memory now.
If you still can't compile ZNC, try
./configure --disable-optimization CXXFLAGS="--param ggc-min-expand=2 --param ggc-min-heapsize=20000" but be prepared for looong wait.
1GB swap has usually been enough with 512MB RAM, to create a swap file of 1 GB, e.g.
sudo fallocate -l 1G /swap sudo chmod 600 /swap mkswap /swap
Now you can either
swapon /swap or edit /etc/fstab and add:
/swap none swap sw 0 0
swapon -a. This enables the swap now and on boot.
configure: error: pkg-config could not find znc (znc.pc)
PKG_CONFIG_PATH=~/znc/lib/pkgconfig ./configure and replace
~/znc with the path you installed ZNC to.
Upgrade your compiler. GCC 4.7+ and Clang 3.2+ are known to work.
As the error says, your compiler is too old. We cannot help you with it, because it's issue with your operating system and not ZNC.
You have two options for getting help:
- Using your favourite search engine.
- Asking on IRC support channel of your distribution, NOT #znc.
Upgrading / updating from a previous release, to a new version
This is really simple. You can just follow the instructions on the Installation page again, but DON'T RUN
--makeconf. Your configuration won't be deleted. If you'd like to make a backup before, however, you can backup ZNC's config folder. It is usually located at ~/.znc. You can use tar to make a backup, like this:
tar cfvj znc-backup.tar.gz ~/.znc.
Your existing configuration will be upgraded to new version when you start it. If new ZNC will complain about few missing modules, you may need to remove them from znc.conf. That can happen if some modules which were loaded to your ZNC are removed in new version. See ChangeLog for details.
Why should I keep my ZNC up-to-date?
ZNC is like any other software, it has bugs and security issues that are fixed in new versions and also gets improvements. By not upgrading you risk all kinds of security issues, don't trust your distribution to patch old releases as ZNC's code has changed so much that it's often impossible to apply patch from newer version to older version.
For reasons to upgrade, take a look at ChangeLogs starting from the next version to what you are currently running to the newest version.
Starting from ZNC 1.6.0 there have been two branches, e.g. 1.6.x gets only bug/security fixes and later becomes 1.6.1 which distributions can package as bugfix release.
Why should I upgrade from ZNC 0.206?
ZNC 0.206 was released on 2012-04-05 and while being ancient, it's sadly still widely used (mainly, because of distributions shipping it).
- IPv6 isn't attempted when it's not available.
- Doesn't crash when admin unloads *admin (now controlpanel) module.
- Doesn't crash when user with attached client is removed.
- CVE-2014-9403 - Denial of Service attack by adding channel that already exists without the "#", the reason why 1.4 was released.
- Disable SSLv3, because of POODLE and follow Mozilla's server-side TLS recommendations.
- Validate SSL certificates.
- Fix memory leak in webadmin if gzip compression is enabled (accessing webadmin is enough, no login required).
- Fix round-robins.
- e.g. don't only resolve chat.freenode.net as rajaniemi.freenode.net even if rajaniemi.freenode.net is down.
- Fix use-after-delete (similar to why 1.4 was released, but more difficult to trigger)
- Build with ancient OpenSSL & OpenSSL with SSLv3 disabled
CAP :ENDparsing which caused some clients to timeout.
- Fix memory leak with invalid config
- Fix modpython memory leak
- Avoid infinite loops with stickychan
These are only the main points and might not be up-to-date when new versions are released. It's also entirely possible that there are security issues that haven't been found yet, but are fixed in newer versions.
Look at ChangeLog for more details and more bug-fixes.
- Someone more technical should check this list and remove this comment, I don't understand e.g. the CSocket changes and do they fix issues. Mikaela Suomalainen (talk) 13:34, 16 September 2015 (CEST)
Do I have to shut down and restart ZNC during an upgrade to a new version?
Yes. You have to. There's no way to avoid it and also no feasible technical way to do it in a future version, sorry.
I get a "Need an operator" error when running make in bsd
Try using gmake instead.
ZNC crashes at making a config file or adding a user via webadmin on FreeBSD 7.x 64bit
Try to compile znc from source with g++42/gcc42 from the ports instead of the default gcc (
./configure CXX=g++42) and check your compile output for g++42.
I'm getting the error: configure: error: C++ compiler cannot create executables
There are missing some compiler packages, you need to install them via:
sudo apt-get update sudo apt-get install build-essential make bin86
If you aren't on Debian, Ubuntu, or related distro, you need to install
make and possibly other things using your package manager.
I'm compiling under debian and I don't have an openssl/include directory available
sudo apt-get install libssl-dev to get the development version of OpenSSL. (Something similar may be the case for other distros with package managers.)
I've installed znc, but when i try to compile modules it says that there is no command znc-buildmod
You need to add the development files to your debian/ubuntu:
sudo apt-get install znc-dev
Why do I get an "Incorrect Password" every time I connect even though my pass is correct?
There're few ways to supply password:
- If you have decent IRC client, you can just use "username" (or "ident") field for username, optional client identifier and network (for example
User@phone/freenode) and "server password" field for password.
- You can supply all four in the password field like "user@phone/network:pass" (without quotes)
- Just do "/quote pass PA$$WORD" manually every time you connect to ZNC
Avoid using special character
: in your password, as this can cause errors when trying to parse the password field to look for username, client, network, and password (user@client/network:pass). If the password has
: in it, everything before first
: is considered to be username (also network and client), and the username sent in the normal way is ignored.
How can I restart ZNC automatically (in case of a machine reboot, crash, etc.)?
Add a cron entry to execute ZNC regularly. If there is already one copy of ZNC running on a particular config file, new copies won't be spawned. Example cron entry:
*/10 * * * * /usr/local/bin/znc >/dev/null 2>&1
This will check if ZNC is running every 10 minutes. If you load a module (like awaystore) that needs user input to run, you can add the input to the LoadModule line in your config file (ie.
LoadModule = awaystore yourpassword).
If you're using Vixie's cron, you can start it on start-up like this.
@reboot /usr/local/bin/znc >/dev/null 2>&1
ZNC dies when I power off the device it's running on!
Of course, ZNC isn't magic. Like any other software, it doesn't run when you turn off or sleep your PC.
If you want to stay connected while your own device is off/sleeping, ZNC must be running on some other machine somewhere. That could be an always-on PC/server in your home, a remote server that you control, or a ZNC server run by someone else. If you were going to run it on your home PC—which you often power-off or sleep—consider getting a VPS or using a ZNC provider instead. That way you can stay connected even when your device is off or sleeping.
How do I tell ZNC which network/server a channel belongs to?
You have separate connection for all network. Please also read the next question.
How to use multiple networks like with psybnc?
ZNC works a bit differently since version 1.0. Each user can have multiple networks, but you need to connect ZNC multiple times; once per network. See Why do I get an incorrect password every time I connect though my password is correct?
I added several different servers, but ZNC connects only to one of them!
You need to have separate user per IRC network (see previous question). (Note: since 0.207 it has been changed, user can have several networks now, see Networks) Additional servers for the same user are for fallback. If one server doesn't work, ZNC tries to connect to another server. So you can add several servers of one network to server list of one user.
How do I choose which IP to use for connecting to IRC?
By default user can choose any bindhost which means the host to use for connecting to IRC:
/znc setuserbindhost 18.104.22.168 /znc jump
If you want to limit users to only one bindhost, go to webadmin and set the user bindhost as whatever you want and check the "deny setbindhost" checkbox.
How can I force IPv4/IPv6 when connecting to the IRC
To force IPv4:
/znc setuserbindhost 0.0.0.0
To force IPv6 bindhost:
/znc setuserbindhost ::
How can I have separate bindhost for IPv4 and IPv6?
IMPORTANT: ZNC cannot connect from IP address that is not available on your system.
If you have root access
hosts file of your operating system and add:
0.0.0.0 my.awesome.vhost.example.com 2001:4860:4860::8888 my.awesome.vhost.example.com
and tell ZNC to use it as bindhost:
/znc setuserbindhost my.awesome.vhost.example.com
With this configuration when IPv6 was used the bindhost would be 2001:4860:4860::8888 and when IPv4 was used, any available IPv4 address was used.
If you don't have root access
You must own a domain and set the A and AAAA records however you want into it or preferably subdomain. Then tell ZNC to bind on it with
/znc setuserbindhost my.awesome.vhost.example.com
How do I add a new user?
There are (at least) two ways to add a new user.
The easiest way is to load and use the webadmin module.
If you want to do it from IRC, load the controlpanel module and check out
/msg *controlpanel help.
Connecting with mIRC
See MIRC for a detailed explanation on how to connect with mIRC.
Connecting with Eggdrop
See Eggdrop for a detailed explanation on how to connect Eggdrop.
I got banned from #channel and ZNC keeps trying to rejoin
/part #channel and ZNC will remove the channel.
How to use the loaded modules?
/msg *modulename command
/znc *modulename command
"*" is the StatusPrefix, which you can change in config file. You could start trying the help command which should work on all modules.
I keep getting kicked for flood when I ...
.. reattach bnc!
This happens if you use "many" channels, due to IRC clients flooding the server with commands upon reattach. A workaround is decreasing size of buffer for each channel. (You should experiment how many is enough.)
... start bnc!
There is a per-User setting to control this:
- MaxJoins - How many channels should ZNC join at once. Lower this if you get disconnected for 'Excess flood.
Enable Flood settings and/or set them to be less generous (by increasing their values). Disabling Flood settings may lead to some cases where you are simply sending too much information to the server. This can be done via the Web Panel
Every time I connect to my BNC, I see the channel buffers from the last time I connected!
If you have a large channel buffer, it may be annoying to see the channel buffer every time you reconnect. To have ZNC erase the channel buffer every time you connect, set AutoClear Chan Buffer and AutoClear Query Buffer to true using either the webadmin or controlpanel module.
/msg *controlpanel set AutoClearChanBuffer $me True /msg *controlpanel set AutoClearQueryBuffer $me True
This will result in only the missed messages being played back to you upon reconnecting. Be careful if you use more than one client as znc will still see you as connected when one drops off and messages will not be buffered. Also, if your connection to znc dies unnaturally, znc might take a little bit to realize you're gone and thus not buffer a few of the messages that you haven't yet seen. The external playback module can help with this if your client supports it.
I don't see buffer playback when attaching to ZNC!
See also the previous question.
If AutoClear Chan Buffer and AutoClear Query Buffer (commonly referred as AutoClear*Buffer) are true, ZNC clears the buffers after they have been sent to client. This has some drawbacks such as sometimes the messages getting lost when client has lost network connection or another client not receiving messages, because one was already running and clearing buffers.
/msg *controlpanel set AutoClearChanBuffer $me False /msg *controlpanel set AutoClearQueryBuffer $me False
In case you wish to only clear buffers automatically for specific clients, take a look at the external clientbuffer module which is basically AutoClear*Buffer for clients added to it.
Check also that your ChanBufferSize and QueryBufferSize are higher than 0 (disabled). They default to 50 meaning you get 50 lines of what was said before you attached to ZNC.
What are BINDHOSTS and why can't I make mine work?
̈́VHOSTS were renamed into BINDHOSTs very long time ago, if you still see it in your ZNC, upgrade immediately!
ZNC bindhost option controls the IP address ZNC will attempt to make connections to the IRC servers from. For this to be successful the computer you're running ZNC on must have this IP address configured and usable for your user. For it to show up as a host name on IRC there must be matching forward and reverse DNS in place. You can check this with:
% host demo.znc.in demo.znc.in has address 22.214.171.124 % host 126.96.36.199 188.8.131.52.in-addr.arpa domain name pointer demo.znc.in.
As long as the response looks similar then you should be able to
/msg *status SetUserBindHost 184.108.40.206
connect to IRC and check that it's working.
If you find you are unable to connect to IRC after attempting to set bindhost options then it is likely you have set an IP address or host name that is not available on your computer. The easiest way to resolve this and get connected to IRC is to
/msg *status ClearUserBindhost
and try to connect again.
To get rid of several misunderstandings vhost was renamed to bindhost since version 0.096.
I get 'Could not find znc-config. Please (re)install' when using znc-buildmod
Your ZNC is too old, upgrade.
I keep getting a lot of stuff like /who replies when connected with multiple clients to one znc-user
see user-module Route_replies
How can I access webadmin with my browser?
By default webadmin runs on the same PORT as your ZNC is accessible. So if you connect your IRC client to ZNC with server example.com and port 6667, then you would access webadmin by opening your web browser and going to the address http://example.com:6667.
If ZNC listens using SSL, use the HTTPS protocol (https://) instead of just HTTP (http://). If your web interface won't come up, please ensure that you are using the correct protocol for connecting.
If you are using Google Chrome and keep getting an Error 312 (net::ERR_UNSAFE_PORT), then try calling Chrome with the parameter
- Plaintext port on IPv4 localhost:
- SSL port on IPv6 localhost:
- Plaintext port on IPv4 localhost:
My IRC-Client doesn't allow multiple connections to one server/host
Try to use different local aliases for the bnc-host.
How to reload ZNC config without restart?
If you really need to do something in znc.conf, stop ZNC, make your changes and start it again.
If you really need to rehash config from file without restart, there're 2 ways to do that: from IRC (
/msg *status rehash)
and from shell (
pkill -SIGHUP znc). But don't complain if something is broken (because it will be broken for sure)
 Software caused connection abort
Socket error 10053 can be caused by attempting to connect without SSL to a znc bouncer with SSL enabled (or vice versa). Refer to your IRC-client's documentation on how to establish a SSL-secured connection to a server.
How to store private messages even when user is attached, so other clients can see them?
What is this new network support?
It means you can add multiple IRC networks such as EFnet and freenode onto a single user. Instead of creating multiple users for each network like you did in versions before 1.0.
How do I connect to my networks?
When you supply your username to ZNC in your client, you can include the network as `username/network`. If you send your username in the server password field you can use `username/network:password`.
There needs to be one connection between the client and the ZNC if you wish to connect to multiple networks at the same time.
As every IRC client is slightly different, please consult the documentation for your IRC client on where to put the server password, or if you wish to configure autoconnect when the IRC client starts.
Examples for mIRC, irssi, and HexChat:
Note: Where 220.127.116.11 is an IP your ZNC instance is listening on, 7777 and 7778 are the port numbers the listeners are using, ZNCUser is the name of the ZNC user account, and PassWord is the password. In these examples, the second line uses SSL whereas the first one does not.
Note: The network name is arbitrarily defined when setting it up in ZNC, though many users will use the name of the actual network for clarity.
/server 18.104.22.168 7778 ZNCUser/EFnet:PassWord /server -ssl 22.214.171.124 7777 ZNCUser/freenode:PassWord
/server 126.96.36.199 7778 ZNCUser/EFnet:PassWord /server -SSL 188.8.131.52 7777 ZNCUser/freenode:PassWord
/server -m 184.108.40.206 7778 ZNCUser/EFnet:PassWord /server -m 220.127.116.11 +7777 ZNCUser/freenode:PassWord
Is it the same as in psybnc?
No, ZNC doesn't use stupid tags for networks, which mix up different channels and nick together to one big network with prefixes.
Instead, you should connect to ZNC multiple times, once for each network, see previous question on how to do that.
Also you may switch between networks on the fly via
/msg *status JumpNetwork command.
If ZNC ever supports connecting to all networks together, it will be done properly, without those prefixes, but via an IRC protocol extension instead. Also that extension should be standardized at IRCv3, to allow client developers to support it easier.
How much memory does ZNC need to run?
This question is very difficult to answer because it depends highly on how much you use it. However, personal ZNC instances, where you are the only user, are unlikely to require a great deal of memory to run.
In an effort to give a better idea of how much memory ZNC may use in different situations, a page with anecdotal reports from users has been added. It may be found here: ZNC Memory Usage
Please update the page with your reports.
My NickServ password is stored in plaintext!
Of course, how could ZNC identify you to services otherwise?
Your ZNC password is hashed in the config file as ZNC doesn't have to know your password, because when you login your password is hashed and compared to the hash in the config file. ZNC cannot do hashing or anything else to other passwords without losing ability to use them.
In theory storing passwords encrypted some way would be possible, but that would require password inputting during ZNC startup preventing starting ZNC automatically and your passwords would still be readable from memory.
If you are using a provider and do not trust them with your credentials, seek a different provider or host ZNC yourself.
Note also that cert isn't any more secure then password if you don't trust the provider. Malicious provider can use it to identify as you and do everything as you including changing your password.
Why does ZNC connect with my altnick?
The exact answer is impossible, other than check
znc -D for what happens. Most likely there was connection issue between ZNC and the server.
Keepnick should always take your primary nick when it becomes free. Alternatively if you want to get your primary nick on connect you can configure SASL and set perform to regain your nick (with Atheme IRC services)
/msg *perform add NICKSERV REGAIN %defnick%.
How can I make ZNC disconnect when I'm not using it?
The primary reason ZNC exists is to keep you connected to IRC while your client is disconnected. However, some people have found other uses for ZNC and want it to disconnect or even shut down when their IRC client isn't connected.
Disconnect ZNC from IRC when the client quits
You can use the external module simple_disconnect to cause ZNC to disconnect from the IRC server when your client quits. If, for whatever reason, ZNC doesn't connect to the IRC network the next time you connect your IRC client to ZNC, simply issue the command
/znc connect to manually initiate the connection between ZNC and the IRC network.
Quit ZNC when the client quits
You probably just want to disconnect ZNC rather than shut it down (see previous section). You can make ZNC quit when you disconnect, but you will then need to access the host machine (via physical access or SSH) and restart ZNC to connect your IRC client to ZNC again; obviously you can't connect your client to ZNC if ZNC is not running.
You can use the external module antiperform to issue commands at the time your IRC client disconnects from ZNC. Add the antiperform command
PRIVMSG *status :shutdown to quit ZNC upon disconnecting your IRC client from ZNC. To reconnect, you must first re-launch ZNC on the host machine (for example,
ssh firstname.lastname@example.org 'znc') before connecting your IRC client to ZNC again.
I forgot my password! How do I reset my ZNC password?
On the host running ZNC, open a terminal and issue the command:
You will then be able to create a new password:
[ ** ] Type your new password. [ ?? ] Enter password: [ ?? ] Confirm password:
Once the new password is entered, you will be instructed on how to update your config file to use the new password:
[ ** ] Kill ZNC process, if it's running. [ ** ] Then replace password in the <User> section of your config with this: <Pass password> Method = sha256 Hash = 846696ed153511170264b41b51008d2c0ccc96929f9e268926857677b50d98dd Salt = +zHiaj0~Ci:d6]/`nPizT:+e </Pass> [ ** ] After that start ZNC again, and you should be able to login with the new password.
How do I reload znc.pem?
znc.pem is currently (1.6.2) reloaded every time client connects to ZNC. It'll be fixed in future (https://github.com/znc/znc/issues/1215)
My SSL certificate has expired
If your ZNC SSL certificate has expired, you can delete the old one (the filename is znc.pem) and generate a new one with the following command:
My client supports server-time and all timestamps are wrong
Your clock is in wrong time either on your PC or the server you run ZNC on. Consider using NTP (Network Time Protocol) to keep your clocks on the right time.
- If you use systemd:
sudo timedatectl set-ntp true
- Windows/Linux/OS using ntp: using pool.ntp.org
- Windows (10): Start → Settings → Time and language → Add clocks for different timezones → Internet-time → Change settings, type
pool.ntp.organd click OK.
- Windows (10): Start → Settings → Time and language → Add clocks for different timezones → Internet-time → Change settings, type
- OS X: System Preferences → Date and Time → (click the lock and) check "Set date and time automatically:" and enter
My question isn't answered here
Hop on #email@example.com and ask! Usually someone's around, but if no one replies, just wait for a while.
Where do I report bugs?
Create a new issue on GitHub.